48c0cd5b2a
Why this change? Before this change, running `d/boot_dev` does not run `bundle install` and `yarn install` unless the `--init` option is specified. However, this does not make sense because the user will end up having to run `d/bundle install` and `d/yarn install` manually after if the `--init` option is not used. We can simplify this by just always running `bundle install` and `yarn install` whenever `d/boot_dev` is used. What does this change do? This change changes the `d/boot_dev` script to always run `bundle install` and `yarn install`. |
||
|---|---|---|
| .. | ||
| README.md | ||
| boot_dev | ||
| bundle | ||
| cleanup | ||
| discourse | ||
| ember-cli | ||
| exec | ||
| mailhog | ||
| migrate | ||
| psql | ||
| rails | ||
| rake | ||
| reset_db | ||
| rspec | ||
| shell | ||
| shell_root | ||
| shutdown_dev | ||
| 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.