-
-
Notifications
You must be signed in to change notification settings - Fork 308
Clean up, add error checking, remove ambiguity around term "port" #1228
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
very good to have these changes @ericfitz , and very good to see the annotation to the example.env file
I am working on the documentation that may help as well
we have just released version 2.4.0, with version 2.5.0 scheduled 6 months away, but this is well worth putting into a version 2.4.1 which can potentially be released this month (March 2025) or mid next month
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome stuff, thanks @ericfitz 🎉
@ericfitz we may have to revert this change for the now - we get Heroku errors:
and the site no longer runs |
Summary:
Cleans up vue.config.js to make clear what different "port" values are used for
Adds error checking for reading TLS certificate/key files
Fixes up references to renamed "PORT" variable in server app & tests
Reorganizes and heavily comments example.env
Description for the changelog:
Make configuration of custom ports easier and more understandable