Production deployment #291
Merged
Conversation
This file contains 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
* add template for NPM BIN PATH for tailwindcss support * add template for NPM BIN PATH for tailwindcss support * local settings for tailwindcss
* add template for NPM BIN PATH for tailwindcss support * add template for NPM BIN PATH for tailwindcss support * local settings for tailwindcss * update contact info on README * update package.json for oryx build
* add template for NPM BIN PATH for tailwindcss support * add template for NPM BIN PATH for tailwindcss support * local settings for tailwindcss * update contact info on README * update package.json for oryx build * error with comment
* add template for NPM BIN PATH for tailwindcss support * add template for NPM BIN PATH for tailwindcss support * local settings for tailwindcss * update contact info on README * update package.json for oryx build * error with comment
* upgrade app service build version and node version in gh actions workflows
* add template for NPM BIN PATH for tailwindcss support * add template for NPM BIN PATH for tailwindcss support * local settings for tailwindcss * update contact info on README * update package.json for oryx build * error with comment * upgrade app service build version and node version in gh actions workflows * python version 3.11
This reverts commit e847975.
Sentry should be helping with this, but I'm still running into application errors that don't make their way to Sentry.
This would require us to have the database connection settings in our github repository and that doesn't sit well with me currently. Let's keep looking.
Supervisor would allow us to programatically run background tasks more easily.
Oryx's post build command won't install the dependencies within the image. The next place I know we can install them is from within the startup command.
It was failing to start up causing the whole server to not load.
Installing things via the startup command causing conflicts from the apt lockfile.
* Add factory_boy dependency. * Add factories for tests.
tim-schilling
approved these changes
Feb 18, 2024
| </tr> | ||
| </table> | ||
| </body> | ||
| </html> |
There was a problem hiding this comment.
Missing EOL. Don't forget to install precommit if you haven't already.
There was a problem hiding this comment.
The pre-commit causes me issues as it's setup for python 3.11, this is all for python 3.9 and normally I use 3.12 😅
I think I would prefer the listing in the ci and I would fix anything that comes up and I think we want black too.
Anyways, added the EOL in the followup PR.
There was a problem hiding this comment.
I would prefer the listing in the ci
What do you mean by "listing" here?
I would fix anything that comes up and I think we want black too
Since our repo is public, I think pre-commit ci can auto-apply fixes to PRs if we configure it to.
There was a problem hiding this comment.
Typo/autocorrect sorry "listing" = "linting"
sarahboyce
temporarily deployed
to
staging-djangonaut-space
GitHub Actions
Inactive
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 draft PR is to receive the reviews I have 'skipped' ❤️
Review comments should be addressed here: #292
Main updates
New field
receive_program_updatesadded to theProfilemodelThis field will be used in future when determining who to send notification emails to about new sessions.
As a migration has been added, we should watch that migrations were applied during the deployment.
Sentry setup and logging config updates
These are to better investigate errors. Sentry account details are in bitwarden.
Removal of our Google interest form
This is now replaced by the signup process.
Plan to send an email to all those who filled in the interest form to create an account in djangonaut.space in order to receive email updates going forward.
HTML template for our emails
Fixed and basic restyling to our account pages
On production, our account pages mostly lead to Internal sever errors e.g. https://djangonaut.space/accounts/signup/
This is because they were missing some installed packages. However, the styling didn't match our current site so I have also tried to adjust them a bit.
Registration
Profile
Login
Reset password
etc
Other updates included