Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to create https server? #142

Open
toghrulgasimov opened this issue Dec 15, 2021 · 7 comments
Open

How to create https server? #142

toghrulgasimov opened this issue Dec 15, 2021 · 7 comments
Labels

Comments

@toghrulgasimov
Copy link

Is it possible to create https server?

@ringabout
Copy link
Member

Sorry, It doesn't support HTTPS server. I think you can use nginx reverse proxy enabling HTTPS.

@ringabout
Copy link
Member

see also https://forum.nim-lang.org/t/8849

@kiwids0220
Copy link

Follwoing this. Is it on the list for TO-DO?

@ringabout
Copy link
Member

ringabout commented Apr 1, 2022

I'm working on a frontend framework based on Nim JS backend atm. I will think of implementing a HTTPs server later.

@ringabout ringabout added the todo label Apr 1, 2022
@kiwids0220
Copy link

Awesome stuff! Thanks for putting up this amazing framework haha.

@PhilippMDoerner
Copy link
Contributor

Is the usecase that the server is capable of sending HTTPS requests to other servers?
Or, in contrast to that, to be connected to via HTTPS from clients?

Mostly asking since I'm struggling a bit to envision a usecase for the latter scenario. Normally you'd put nginx or apache between your server and the internet which are capable of such things, thus the confusion on my end.

@PhilippMDoerner
Copy link
Contributor

PhilippMDoerner commented Jul 12, 2022

In case there still is need for using prologue with https, I've written up a deployment guide that leads you through how you can deploy docker with an nginx reverse proxy where nginx handles HTTPS.
https://planety.github.io/prologue/deployment/

Granted, that one assumes you'll deploy both together via the same docker container, but it can be easily enough adjusted to your own way that you want to deploy (e.g. nginx and prologue in separate containers or whatnot).

Since it's a good idea to use a reverse proxy anyway I think that's an alright state to be in regarding this issue ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants