-
Notifications
You must be signed in to change notification settings - Fork 7
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
Independance from Linux (MacOS) #11
Comments
Do you know what would be required to make that happen, or what is stopping it from working on windows? I wasn't aware it was a problem running on windows. |
I can't run .sh files on windows, there is whole library that does let's encrypt. It is called greenlock |
@Akxe Ahh! OK. Yes that makes a lot of sense. Honestly I stopped using windows for server functionality about 10 years ago and every now and then I get a gotcha like this when I assume a platform :) |
Sure, most users use Linux as server platform, but for example my home server, or many localhosts playgrounds are on windows. |
@Akxe agreed. Do you have a suggestion on the best way to handle this? Do you think we should just auto-detect windows and use a different tool to do letsencrypt or should we make it part of the config file? Do you have any preference, suggestions? Also, because I don't use windows, any change that makes this possible will need testing by someone who uses windows :) |
I wouldn't separate codebase into two based on OS. I rather use one of the let's encrypt libraries. The greenlock seemed to me as best bet, but I will sure look into it a bit more once I get home. I can for sure set up a test server on Windows to test my part and you can do the Linux one.
|
I think that this one should do exactly what we need, however we should look it it will express version also support httpproxy or not. |
Doesn't letsencrypt have an official Node.js module? |
No, I don't think so, I thing that most vanilla experience is this: https://git.daplie.com/Daplie/node-greenlock |
It would be great if it would not be defendant on Linux, therefor would be usable on Windows too.
The text was updated successfully, but these errors were encountered: