History

Tyler Pickett 099365aec1 Add rake task to populate Consul from dynamic_settings.yml Fixes: CNVS-39293 Since we eliminated the pre-population functionality from our Consul wrapper we needed something to conveniently populate the KV store. Test Plan: - Start a Consul server - Run `bin/rake canvas:seed_consul` - Verify that values were written to the KV store. Change-Id: I340011b7d00ed4e3dd2918e3f101f6377fc72d7e Reviewed-on: https://gerrit.instructure.com/126574 Reviewed-by: Cody Cutrer <cody@instructure.com> Product-Review: Tyler Pickett <tpickett@instructure.com> QA-Review: Cody Cutrer <cody@instructure.com> Tested-by: Jenkins		2017-09-19 18:08:39 +00:00
..
README.md	update README for docker known issues	2017-08-14 18:43:47 +00:00
consul.md	Add rake task to populate Consul from dynamic_settings.yml	2017-09-19 18:08:39 +00:00
developing_with_docker.md	Remove karma container from docker-compose.override.yml	2017-08-18 20:03:30 +00:00
getting_docker.md	remove docker-toolbox for macOS as a viable way to use docker	2017-07-05 19:11:23 +00:00

README.md

Using Docker to run Canvas

Prerequisites

You need Docker. Don't have Docker yet? Go here for details on getting it setup.

Development

These commands should get you going

cp docker-compose/config/* config/
docker-compose run --rm web bash -c "bundle install"
docker-compose run --rm web bash -c "bundle exec rake db:create db:initial_setup"

Now you can do docker-compose up and you should be good to go. If you're using Dinghy or Dory. You should be able to access Canvas by going to: http://web.canvaslms.docker/

On Linux you may want to run this to avoid a few permissions issues:

touch mkmf.log .listen_test
chmod 777 !:2 !:3
sudo chown -R `whoami`:9999 .
chmod 775 gems/canvas_i18nliner
chmod 775 . log tmp gems/selinimum gems/canvas_i18nliner
chmod 664 ./app/stylesheets/_brand_variables.scss

For more information checkout Developing with Docker

Known Issues

Long URL Gateway 502

If a URL is long enough, you may see a Gateway 502 error. This problem has been patched in dinghy-http-proxy#36 however until a new release is cut the follow can be done as a work around:

In ~/.dinghy/proxy.conf add the following:

proxy_buffers 8 1024k;
proxy_buffer_size 1024k;

Restart dinghy afterwards.