ylqjgm
/
canvas-lms
mirror of https://github.com/instructure/canvas-lms.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
canvas-lms/docker-compose.yml

24 lines
454 B
YAML
Raw Normal View History

docker-compose.yml v2 If you have a docker-compose.override file you'll want to move it somewhere else. mv docker-compose.override.yml docker-compose.`whoami`.yml Once you've updated your override file to the version 2 syntax, you should add it to the COMPOSE_FILE environment variable. Probably in a .env file in the project root. Test plan: You'll need to remove your existing canvas containers and volumes to fully test this. to do so run this **BEFORE** you checkout this patchset ``` docker-compose down docker-compose ps -q | docker rm docker volume ls -q | grep canvaslms | xargs docker volume rm ``` then you should be able to get up and running using the following ``` cp docker-compose/config/* config/ dc build dcr web bundle exec rake db:create db:initial_setup dc up ``` You should be able to access canvas like normal Change-Id: Ia7ff76cfdd4f46278fc1cb2a03969fdadaa4a434 Reviewed-on: https://gerrit.instructure.com/91008 Reviewed-by: Zach Wily <zach@instructure.com> Tested-by: Jenkins QA-Review: August Thornton <august@instructure.com> Product-Review: Brad Horrocks <bhorrocks@instructure.com>
2016-09-23 02:42:34 +08:00
# See doc/docker/README.md or https://github.com/instructure/canvas-lms/tree/master/doc/docker
build ruby image in docker_dev_setup docker_dev_setup.sh broke with a recent change to how we build our docker image. Adding the ruby docker build into the script, then passing that image as an arg to the main Dockerfile. Removed the default of the arg to pull from starlord since it's not available to public. fixes: DE-153 Test Plan - Run docker_dev_setup.sh in a clean environment - script will build canvas-lms-ruby image - script will build alpine image using ruby image Change-Id: Ia607f72717580bc808616f5483bb5c26342241ad Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/243614 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Aaron Ogata <aogata@instructure.com> Product-Review: James Butters <jbutters@instructure.com> QA-Review: James Butters <jbutters@instructure.com>
2020-07-29 00:58:02 +08:00
version: '2.3'
docker-compose.yml v2 If you have a docker-compose.override file you'll want to move it somewhere else. mv docker-compose.override.yml docker-compose.`whoami`.yml Once you've updated your override file to the version 2 syntax, you should add it to the COMPOSE_FILE environment variable. Probably in a .env file in the project root. Test plan: You'll need to remove your existing canvas containers and volumes to fully test this. to do so run this **BEFORE** you checkout this patchset ``` docker-compose down docker-compose ps -q | docker rm docker volume ls -q | grep canvaslms | xargs docker volume rm ``` then you should be able to get up and running using the following ``` cp docker-compose/config/* config/ dc build dcr web bundle exec rake db:create db:initial_setup dc up ``` You should be able to access canvas like normal Change-Id: Ia7ff76cfdd4f46278fc1cb2a03969fdadaa4a434 Reviewed-on: https://gerrit.instructure.com/91008 Reviewed-by: Zach Wily <zach@instructure.com> Tested-by: Jenkins QA-Review: August Thornton <august@instructure.com> Product-Review: Brad Horrocks <bhorrocks@instructure.com>
2016-09-23 02:42:34 +08:00
services:
web: &WEB
build:
context: .
links:
- postgres
- redis
Configure databases in a unified manner This patchset removes the much duplicated database.yml and instead defaults to a DATABASE_URL scheme. There is however still present a docker-compose/config/new-jenkins/database.yml file to temporarily allow our internal portal service to still function until such time we can reconfigure it. To set up custom connection options all that is needed is setting DATABASE_URL. See examples of this in docker-compose.yml and docker-compose.new-jenkins.yml. Test Plan ========= Image: - pulling canvas-lms:master image boots without database errors Repo: - given default dev environment where COMPOSE_FILE=docker-compose.yml:docker-compose.override.yml - build the web and postgres images: docker-compose build web postgres (feel free to comment out `yarn install` and `compile_assets` in the Dockerfile since we won't be needing them for this test and this speeds things up) - set a custom DATABASE_URL to change the database name and echo it to see it gets into the image correctly: $ docker run -it -e \ DATABASE_URL=postgres://postgres:sekret@postgres/canvas_custom_env \ $(docker-compose ps -q web) bash -c "echo \$DATABASE_URL" => postgres://postgres:sekret@postgres/canvas_custom_env $ docker-compose run --rm -e \ DATABASE_URL=postgres://postgres:sekret@postgres/canvas_custom_env \ web bash -c "echo \$DATABASE_URL" => postgres://postgres:sekret@postgres/canvas_custom_env - Test that setting a custom database name via DATABASE_URL can create the database $ docker-compose run --rm -e \ DATABASE_URL=postgres://postgres:sekret@postgres/canvas_custom_env \ web bash -c "bin/rails db:create" => Created database 'canvas_custom_env' - This patchset boots on portal Change-Id: Ic6f3819550df94b6c98b17ef05ac2029a578cfe4 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/234213 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Jacob Powell <spowell@instructure.com> Reviewed-by: James Butters <jbutters@instructure.com> QA-Review: Robin Kuss <rkuss@instructure.com> QA-Review: Rex Fleischer <rfleischer@instructure.com> QA-Review: Jacob Powell <spowell@instructure.com> Product-Review: Rex Fleischer <rfleischer@instructure.com>
2020-04-16 02:52:10 +08:00
environment:
Remove DATABASE_URL from docker dev envs Fixes: CCI-347 This will allow connecting to the test environment again. Copy over the updated config/docker-compose.override.yml (or delete the relevant line from your existing docker-compose.override.yml). Also copy over the restored and modified config/database.yml.example. $ cp -iv config/docker-compose.override.yml.example \ docker-compose.override.yml $ cp -iv docker-compose/,}config/database.yml If you have existing databases that don't match the naming scheme of "canvas_<ENV>" then you'll need to do a custom configuration for your database names in config/database.yml or rename your databases in postgres. Test Plan - update your override config and database.yml: $ cp -iv config/docker-compose.override.yml.example \ docker-compose.override.yml $ cp -iv {docker-compose/,}config/database.yml - make sure your postgres image is up to date from earlier patchset (this will remove all your data): $ docker-compose down --volumes $ docker-compose build --no-cache postgres - boot the app, bundle, and wait for postgres to be available (for internal start up scripts to run): $ docker-compose run --rm web bundle \ && docker-compose run --rm web build/new-jenkins/wait-for-it \ postgres:5432 -t 30 - test that connctions to both development and test databases work: - developement: $ docker-compose run --rm web bin/rails runner \ 'puts ActiveRecord::Base.connection.current_database' => 'canvas_development' - test: $ docker-compose run --rm -e RAILS_ENV=test web bin/rails runner \ 'puts ActiveRecord::Base.connection.current_database' => 'canvas_test' - set a custom database name: $ docker-compose run --rm \ -e RAILS_ENV=test \ -e CANVAS_DATABASE_TEST=canvas_rails3_ \ web bin/rails runner \ 'Rails.application.load_tasks; \ Rake::Task["db:create"].invoke; \ puts ActiveRecord::Base.connection.current_database' => 'canvas_rails3_' flag = none Change-Id: Ia19038586508dc91c6a4d4386d812752e00a4ad6 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/235642 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Rex Fleischer <rfleischer@instructure.com> Reviewed-by: James Butters <jbutters@instructure.com> Reviewed-by: Augusto Callejas <acallejas@instructure.com> QA-Review: James Butters <jbutters@instructure.com> Product-Review: Derek Bender <djbender@instructure.com>
2020-04-29 23:04:42 +08:00
POSTGRES_PASSWORD: sekret
docker-compose.yml v2 If you have a docker-compose.override file you'll want to move it somewhere else. mv docker-compose.override.yml docker-compose.`whoami`.yml Once you've updated your override file to the version 2 syntax, you should add it to the COMPOSE_FILE environment variable. Probably in a .env file in the project root. Test plan: You'll need to remove your existing canvas containers and volumes to fully test this. to do so run this **BEFORE** you checkout this patchset ``` docker-compose down docker-compose ps -q | docker rm docker volume ls -q | grep canvaslms | xargs docker volume rm ``` then you should be able to get up and running using the following ``` cp docker-compose/config/* config/ dc build dcr web bundle exec rake db:create db:initial_setup dc up ``` You should be able to access canvas like normal Change-Id: Ia7ff76cfdd4f46278fc1cb2a03969fdadaa4a434 Reviewed-on: https://gerrit.instructure.com/91008 Reviewed-by: Zach Wily <zach@instructure.com> Tested-by: Jenkins QA-Review: August Thornton <august@instructure.com> Product-Review: Brad Horrocks <bhorrocks@instructure.com>
2016-09-23 02:42:34 +08:00
jobs:
<<: *WEB
command: bundle exec script/delayed_job run
postgres:
add i18n sorting dependencies to docker fixes CNVS-35005 Test Plan 1. run: docker-compose build 2. run: docker-compose run --rm web bundle exec rake db:migrate:redo VERSION=20120502190901 3. Visit: /accounts/1/users 4. Create users with the names: Jalapeno, Jalapeoo, Jalapeño, JalapeЖo 5. Refresh the page and verify they are sorted: Jalapeno, Jalapeño, Jalapeoo, JalapeЖo 6. Create an assignment 7. Give each of the students created above a grade 8. Visit: /courses/1/gradebook/history 9. Click on the assignment name to display the hidden table. 10. Verify the table of students / grades is sorted: Jalapeno, Jalapeño, Jalapeoo, JalapeЖo Change-Id: I9743c559a20a3d50600bcbc7e4a310105ec638cf Reviewed-on: https://gerrit.instructure.com/102465 Tested-by: Jenkins Reviewed-by: Neil Gupta <ngupta@instructure.com> QA-Review: Anju Reddy <areddy@instructure.com> Product-Review: Keith T. Garner <kgarner@instructure.com>
2017-02-17 04:26:54 +08:00
build: ./docker-compose/postgres
Configure databases in a unified manner This patchset removes the much duplicated database.yml and instead defaults to a DATABASE_URL scheme. There is however still present a docker-compose/config/new-jenkins/database.yml file to temporarily allow our internal portal service to still function until such time we can reconfigure it. To set up custom connection options all that is needed is setting DATABASE_URL. See examples of this in docker-compose.yml and docker-compose.new-jenkins.yml. Test Plan ========= Image: - pulling canvas-lms:master image boots without database errors Repo: - given default dev environment where COMPOSE_FILE=docker-compose.yml:docker-compose.override.yml - build the web and postgres images: docker-compose build web postgres (feel free to comment out `yarn install` and `compile_assets` in the Dockerfile since we won't be needing them for this test and this speeds things up) - set a custom DATABASE_URL to change the database name and echo it to see it gets into the image correctly: $ docker run -it -e \ DATABASE_URL=postgres://postgres:sekret@postgres/canvas_custom_env \ $(docker-compose ps -q web) bash -c "echo \$DATABASE_URL" => postgres://postgres:sekret@postgres/canvas_custom_env $ docker-compose run --rm -e \ DATABASE_URL=postgres://postgres:sekret@postgres/canvas_custom_env \ web bash -c "echo \$DATABASE_URL" => postgres://postgres:sekret@postgres/canvas_custom_env - Test that setting a custom database name via DATABASE_URL can create the database $ docker-compose run --rm -e \ DATABASE_URL=postgres://postgres:sekret@postgres/canvas_custom_env \ web bash -c "bin/rails db:create" => Created database 'canvas_custom_env' - This patchset boots on portal Change-Id: Ic6f3819550df94b6c98b17ef05ac2029a578cfe4 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/234213 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Jacob Powell <spowell@instructure.com> Reviewed-by: James Butters <jbutters@instructure.com> QA-Review: Robin Kuss <rkuss@instructure.com> QA-Review: Rex Fleischer <rfleischer@instructure.com> QA-Review: Jacob Powell <spowell@instructure.com> Product-Review: Rex Fleischer <rfleischer@instructure.com>
2020-04-16 02:52:10 +08:00
environment:
POSTGRES_PASSWORD: sekret
docker-compose.yml v2 If you have a docker-compose.override file you'll want to move it somewhere else. mv docker-compose.override.yml docker-compose.`whoami`.yml Once you've updated your override file to the version 2 syntax, you should add it to the COMPOSE_FILE environment variable. Probably in a .env file in the project root. Test plan: You'll need to remove your existing canvas containers and volumes to fully test this. to do so run this **BEFORE** you checkout this patchset ``` docker-compose down docker-compose ps -q | docker rm docker volume ls -q | grep canvaslms | xargs docker volume rm ``` then you should be able to get up and running using the following ``` cp docker-compose/config/* config/ dc build dcr web bundle exec rake db:create db:initial_setup dc up ``` You should be able to access canvas like normal Change-Id: Ia7ff76cfdd4f46278fc1cb2a03969fdadaa4a434 Reviewed-on: https://gerrit.instructure.com/91008 Reviewed-by: Zach Wily <zach@instructure.com> Tested-by: Jenkins QA-Review: August Thornton <august@instructure.com> Product-Review: Brad Horrocks <bhorrocks@instructure.com>
2016-09-23 02:42:34 +08:00
redis:
Use redis:alpine Updates docker-compose.yml to use redis:alpine, which is the same version we use to run tests on jenkins. Our lua scripts don't seem to work with redis 2.6. Change-Id: I608d7bbea9e813a5fb31f0c32b8fdf5ba127f16d Reviewed-on: https://gerrit.instructure.com/121058 Tested-by: Jenkins Reviewed-by: Jon Jensen <jon@instructure.com> Product-Review: Jon Jensen <jon@instructure.com> QA-Review: Jon Jensen <jon@instructure.com>
2017-08-01 06:19:51 +08:00
image: redis:alpine