Improve the "develop inside Docker" experience #4450
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is intended to work in concert with the discourse_docker changes in discourse/discourse_docker#292. I have used those changes to build a local "discourse_dev" image, and then these changes to easily spin up and work on Discourse and plugin functionality. It's working well for me, but of course YMMV.
Add
--init
and--patch
options to bin/docker/boot_dev to make it easier to spin up a container running Discourse out of a development directory.Add
bin/docker/README.md
to explain how to go about using the docker command-line tools.Tweak the Docker command-line tools to use the
-u
option to specify user rather than changing to the user "inside" the container viachpst
(This way, we don't have to explicitly specify the HOME environment variable, either.)Add
bin/docker/shell
command to make it easy to jump inside the running container.