History

Sam Saffron d8412f409a DEV: resolve symlinks in docker dev symlinks where not fully resolved leading to docker not booting when you had symlinks in the plugins directory pointing at relative paths.		2020-01-13 10:33:34 +11:00
..
README.md	…
boot_dev	DEV: resolve symlinks in docker dev	2020-01-13 10:33:34 +11:00
bundle	DEV: improve docker dev environment	2018-12-31 10:45:08 +11:00
discourse	DEV: Add missing discourse script to docker dev	2019-01-07 13:10:37 +11:00
mailcatcher	DEV: improve docker dev environment	2018-12-31 10:45:08 +11:00
migrate	DEV: improve docker dev environment	2018-12-31 10:45:08 +11:00
psql	DEV: improve docker dev environment	2018-12-31 10:45:08 +11:00
rails	DEV: improve docker dev environment	2018-12-31 10:45:08 +11:00
rake	DEV: improve docker dev environment	2018-12-31 10:45:08 +11:00
reset_db	Fix docker image name (#8058 )	2019-09-04 16:19:48 +10:00
rspec	DEV: default to test env when running d/rspec (#7962 )	2019-08-02 16:40:46 +10:00
shell	…
shell_root	…
shutdown_dev	…
sidekiq	FEATURE: introduce ultra_low priority queue	2019-01-17 14:53:19 +11:00
unicorn	DEV: improve docker dev environment	2018-12-31 10:45:08 +11:00

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.