Elastic Beanstalk Support #1867
Draft
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
The 5.x branch is the only one that's compatible with python 3.11 (which our EB env uses).
In an attempt to get the site to stand up in the Elastic Beanstalk (EB) environment, I'm attempting to remove non-Django services that aren't configured yet. These should be re-enabled as the components of the EB infrastructure are activated.
Our procfile has worker/celery related code, so I removed it because that piece of the infrastructure wasn't ready yet and so the service was crashing. Attempting to apply the same settings (or similar ones recommended in the docs) via a config file in `.ebextensions/`.
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 pull request should not be merged yet. It is unfinished and requires some more work on the Amazon Elastic Beanstalk (EB) environment and configuration before it will, in addition to other potential code changes to this repo.
Some changes so far (see individual commits for more detail):
eb_production.pyfile which mimics our production settings with EB-specific changes. If/when we decide to run the actual site on EB, these settings should probably find their way into the regular production/dev settings files as necessary and theeb_prefixed file removed.I've been attempting to get this branch running on EB using the command line tool and running some commands. These commands often call for an environment name, and the one I'm using is
newamerica-cms-dev.eb console-- opens the web page for the stats and configuration of the environment.eb deploy <environment name>-- deploys the current state of the source tree to the environment. When you make changes to the code, whether or not they're committed in git, this command will send those to EB to try and runeb logs <environment name>-- shows the logs for the environment. Sometimes, this commands fails for me with a 400 error, which is weird since the thing issuing the request is also created by Amazon. In those cases, sometimes the logs are available on theeb consolepage (sometimes they aren't though).eb open <environment name>-- opens URL that the environment is running on. This should be the actual wagtail instance URL. But I haven't gotten it to actually load anything beyond an error page because the configuration isn't correct yet.The current state of the
newamerica-cms-devenvironment is: the console says it's "ok" but the site won't load and I can't add a database (from the left sidebar of the console's Configuration option, then Networking and Databases) without getting these errors:My current theory is that creating the database also creates an RDS security group, but the user I'm running as might not have permission to do so. I can't confirm this though, and I've poked around in the users and permissions areas of AWS and not found anything obviously helpful.