Docker setup

[efstajas]

PR for improved Docker setup.

Changes:

• Adds a single Dockerfile that can be used to deploy a production build on Railway, build a generic production image, and building an image for development that can run the dev server
• Adds a single docker-compose.yml file that (for now) spins up a Redis and dev container of the app
• Most environment variables apart from a few absolutely necessary ones are now optional during development
  • getOptionalEnvVar utils now allow specifying whether the variable is required in production
  • getOptionalEnvVar will now warn about a variable that is required in prod but not def missing, including clear logs about what functionality will be missing / not work properly given the lack of any particular variable
• Changes to building GQL types
  • New npm run gql:generate-schema command will only fetch schema from remote GQL server using GQL_URL and GQL_ACCESS_TOKEN, and create a (gitignored) schema.graphql file in root dir
  • New npm run gql:build-types command will build GQL types based on schema.graphql file.
  • New npm run gql:build command combines the two above commands into one.
  • Building the Dockerfile (by default) now expects schema.graphql file being present in root dir. This allows building a production image including GQL types without leaking GQL_ACCESS_TOKEN into the built image.
  • Still, passing GQL_URL and GQL_ACCESS_TOKEN directly into the image build is possible so that Railway can build properly.

Todo:

• Add GitHub Action that builds app docker image and publishes it to Docker registry
• Dockerize all other parts of the stack by creating Dockerfiles that publish to Docker registry
• Add all other parts of the stack to app's docker-compose for development
• Update .env.template
• Update DEVELOPMENT.md documentation

[railway-app]

🚅 Deployed to the app-pr-1428 environment in Drips App

Service	Status	Web	Updated (UTC)
[Base PR] App	✅ Success (View Logs)	Web	Jan 28, 2025 at 12:36 pm