ff33899323
Previously we had no control over how internal ports in the containter got published. Following UNICORN_BIND_ALL=true setting this broke docker dev env and exposed this weakness. The new `d/boot_dev` will only export on localhost, if you wish to export network with use `d/boot_dev -p` |
||
|---|---|---|
| .. | ||
| README.md | ||
| boot_dev | ||
| bundle | ||
| discourse | ||
| mailcatcher | ||
| migrate | ||
| psql | ||
| rails | ||
| rake | ||
| reset_db | ||
| rspec | ||
| shell | ||
| shell_root | ||
| shutdown_dev | ||
| sidekiq | ||
| unicorn | ||
README.md
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.