-
Notifications
You must be signed in to change notification settings - Fork 21
Automated deployment forward port #711
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
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
To run webpack on node 18 we need to set --openssl-legacy-provider until we can upgrade webpack.
Automate housekeeping for web2py in a Grunt task
We need an up-do-date pymysql, get it by wrapping a venv around web2py Add a web2py-run helper to use when running standalone scripts, that will get the web2py setup right.
This will impact search performance, by forcing all search queries to go through the unique index before searching. Remove, replace with google analytics later.
Instead of having to tweak is_testing for production use, check the request environment to see what server we're using.
Not that we should be using sessions much, if at all.
Scripts to configure nginx/supervisord
Update shebang at the top of web2py.py so it uses the venv by default.
Remove dependencies that are now part of tree-build, rework instructions to take into account new Grunt rules. Rework based on the
Ideally this would be separated out into instructions for a production instance, but at least not mentioning a temporary branch is good.
An empty installation doesn't have /var/db/acme/live/, only /var/db/acme/.
Nginx falls over if v6 isn't available, which it isn't.
There is no /usr/local/etc/supervisord, it's all in /usr/local/etc.
It's comforting to see what it's doing, and makes error messages more intelligable.
Move the production installation notes into their own section, mention the install scripts to be run as root.
There isn't a separate README_SERVER any more, the installation notes are more choose-your-own-adventure and the gory details are mostly automatic now.
* Link to MSI installer * Suggest SQL workbench
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request forward-ports the work from #703 to main, and completes the to-dos in #672 is now done.
The README still needs more work, but is getting better at least :)
Fixes #672
Fixes #676