This PR is intended to work in concert with the discourse_docker changes
in https://github.com/discourse/discourse_docker/pull/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 via `chpst`
(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.
* ignoring .rvmrc so people can feel to use their own and not
accidentally commit it
* added a .rvmrc.sample file for people to get started
* fixes#608
* [ci skip]
This introduces two configuration management runs into the
Vagrant provisioning phase. The first chef-solo run ensures that
a current version of chef is installed using the omnibus updater.
The second chef-solo run installs vim and phantomjs.
Much more is possible, this is a proof of concept.
Cookbooks are stored in the chef directory, and managed by
librarian-chef, which is like a bundler for cookbooks.
Chef is run when VM is first downloaded and booted, but not on
subsequent halt/up cycles. To force chef to run again, use
`vagrant provision`.
Sam
Jared Reisinger
Guo Xiang Tan
Jeff Atwood
Neil Lalonde
James Kiesel
Régis Hanol
Arpit Jalan
Vikhyat Korrapati
Robin Ward
Alban Diguer
Navin
Pablo Corral
Kuba Brecka
Tobias Pfeiffer
Karan Misra
nverba
Marco Ceppi
Elliot Murphy