Skip to content

Conversation

@cfarvidson
Copy link

Why

To simplify local development and ensure consistency across different environments by using Docker. Additionally, switching to Solid Queue for background jobs provides a database-backed queuing system that is easier to manage in a local development environment without requiring Redis.

What’s included

  • A docker-compose.yml file to orchestrate the application, MySQL database, and a worker process.
  • Updates to Dockerfile.dev and .dockerignore for efficient container builds.
  • Configuration for multiple databases (primary, cable, queue, cache) in config/database.mysql.yml.
  • Configuration of ActiveJob to use Solid Queue in the development environment.
  • Necessary migration directories for the secondary databases.

Usage

  1. Ensure Docker is installed and running.
  2. Run docker-compose up to start the application, database, and worker.
  3. Access the application at http://fizzy.localhost:3006.

Configuration

  • The docker-compose.yml uses environment variables for database connection details.
  • config/environments/development.rb now specifies solid_queue as the queue adapter.

Notes

  • The GITHUB_TOKEN secret is required for the build process if private gems are used.
  • The db/*_migrate directories were added to support Rails' multi-database migrations.

- Updated .dockerignore and Dockerfile.dev for better containerization
- Added docker-compose.yml for local development
- Configured Solid Queue in development environment
- Added dedicated databases for queue and cache in MySQL config
- Included necessary migration directories for multi-database setup
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