This PR adds Pitchfork, as we want to move away from Unicorn ultimately. Unicorn still boots by default, so there should be no disruption for anyone. To use Pitchfork instead of Unicorn, the `RUN_PITCHFORK` environment variable must be set. This will make `bin/rails s` and `config/unicorn_launcher` boot Pitchfork. `unicorn_launcher` was patched because that way we can easily switch between Unicorn and Pitchfork without having to change too many things on the infra side. The upgrader from the `docker_manager` plugin doesn’t work yet with Pitchfork. This will be addressed in a future PR. |
||
|---|---|---|
| .. | ||
| boot_dev | ||
| bundle | ||
| cleanup | ||
| discourse | ||
| ember-cli | ||
| exec | ||
| mailhog | ||
| migrate | ||
| pitchfork | ||
| psql | ||
| rails | ||
| rake | ||
| README.md | ||
| reset_db | ||
| rspec | ||
| shell | ||
| shell_root | ||
| shutdown_dev | ||
| unicorn | ||
Developing using Docker
Since Discourse runs in Docker, why not develop there? If you have Docker installed, you should be able to run Discourse directly from your source directory using a Discourse development container.
You can find installation instructions and related discussion in this meta topic: https://meta.discourse.org/t/beginners-guide-to-install-discourse-for-development-using-docker/102009
Where is the container image/Dockerfile defined?
The Dockerfile comes from discourse/discourse_docker on GitHub, in particular image/discourse_dev.