Skip to content

Conversation

@Mars190
Copy link

@Mars190 Mars190 commented Mar 19, 2025

Disclaimer

Some important things changed, that could possibly break the deployment process:

  • .env no longer contains a database url, it now contains the individual variables for it to be crafted by the backend
  • The SESSION_SECRET is now required to be atleast 32 characters long, instead of 12
  • Docker Compose now also usese these variables to spin up a database with given values
  • Updated to yarn 4.7 for the backend
  • Changed the name of some commands in package.json

Other changes

  • Updated documentation to setup the backend
  • All backend dependencies are atleast no longer outdated

Mars190 added 25 commits March 18, 2025 16:44
- Added a volume to the Postgres service in docker-compose.yml
- Replaced hardcoded values with environment variables in docker-compose.yml
- Edited Makefile to include the .env file when starting Docker Compose
- Renamed .env.development to .env.example and removed DATABASE_URL;
  now using environment variables to construct the Postgres connection URL
- Updated documentation on how to set up the backend
- Fixed yarn.lock (previous version was incompatible)
- Added a NOTE.md to help with project structure
- Increased SESSION_SECRET_MIN_LENGTH from 12 to 32 characters

Note: The change to SESSION_SECRET_MIN_LENGTH could be considered a breaking change,
depending on how long the production session secret is.
@Mars190
Copy link
Author

Mars190 commented Mar 19, 2025

I checked that login and the challenges themselves still work manually, the two tests still pass.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant