add option to use Docker instead of VM #16

Merged
merenber merged 11 commits from docker into v1 2021-09-17 22:39:28 -04:00
Owner
No description provided.
merenber added 3 commits 2021-09-09 23:38:46 -04:00
merenber requested review from a268wang 2021-09-10 00:02:51 -04:00
merenber requested review from r345liu 2021-09-10 00:02:51 -04:00
merenber added 1 commit 2021-09-10 18:29:40 -04:00
continuous-integration/drone/pr Build is failing Details
f72c6665f9
add nslcd for mail and coffee
merenber added 1 commit 2021-09-10 18:46:01 -04:00
continuous-integration/drone/pr Build is passing Details
2814adcb7c
don't setup auth on coffee in CI
merenber added 1 commit 2021-09-10 18:51:43 -04:00
continuous-integration/drone/pr Build is passing Details
dca957d61a
update OU
Owner

Why not use docker-compose to set up the networks, volumes, etc? Also, why not start ceod automatically in docker, but to use sleep infinity and attach? That seems like bunch of manual steps that can be automated.

Why not use docker-compose to set up the networks, volumes, etc? Also, why not start ceod automatically in docker, but to use sleep infinity and attach? That seems like bunch of manual steps that can be automated.
Author
Owner

We could use docker-compose - I just felt like writing a shell script (feel free to modify).
As for why we sleep infinity, it's because you're going to need to manually restart ceod if you change the source code. If ceod was the foreground process, this would require killing and re-creating the container. I figured it would be easier to just manually start ceod so that we can Ctrl-C and restart it.

We *could* use docker-compose - I just felt like writing a shell script (feel free to modify). As for why we `sleep infinity`, it's because you're going to need to manually restart ceod if you change the source code. If ceod was the foreground process, this would require killing and re-creating the container. I figured it would be easier to just manually start ceod so that we can Ctrl-C and restart it.
merenber added 1 commit 2021-09-10 22:41:15 -04:00
continuous-integration/drone/pr Build is passing Details
ae34b6b7ce
add more UWLDAP users
Author
Owner

I updated the VM so that we can use the same ceod_dev.ini file in both:
2438b1c1d9

I updated the VM so that we can use the same ceod_dev.ini file in both: https://git.uwaterloo.ca/csc/syscom-dev-environment/-/commit/2438b1c1d9d270aedb79b388e912df584853a319
merenber added 1 commit 2021-09-10 22:57:13 -04:00
continuous-integration/drone/pr Build is passing Details
35e577b866
use python image for coffee
Owner

Maybe we can have a simple superviser that restarts ceod on signal? Normally ceod restarts by itself anyways so manual restart would only be needed occasionally (using docker kill -sighup or similiar). Main thing is that I feel having to attach to each individual manually is too much manual work especially when docker can start services by itself.

I can make a pr to this branch with docker-compose and the superviser thing if you want, although I don't want to install docker on my computer right now. Doe any csc machines have docker installed?

Maybe we can have a simple superviser that restarts ceod on signal? Normally ceod restarts by itself anyways so manual restart would only be needed occasionally (using docker kill -sighup or similiar). Main thing is that I feel having to attach to each individual manually is too much manual work especially when docker can start services by itself. I can make a pr to this branch with docker-compose and the superviser thing if you want, although I don't want to install docker on my computer right now. Doe any csc machines have docker installed?
Author
Owner

I can make a pr to this branch with docker-compose and the superviser thing if you want

Sure, that'd be great.

Doe any csc machines have docker installed?

Unfortunately none of the general-use machines have Docker installed - we haven't figured out a way to do that securely.

> I can make a pr to this branch with docker-compose and the superviser thing if you want Sure, that'd be great. > Doe any csc machines have docker installed? Unfortunately none of the general-use machines have Docker installed - we haven't figured out a way to do that securely.
merenber added 1 commit 2021-09-15 17:30:51 -04:00
continuous-integration/drone/pr Build is passing Details
f873d04139
Use docker-compose to manage containers. (#19)
Use docker-compose to manage the containers, and start ceod automatically. The service can be restarted with SIGHUP sent by docker/docker-compose.

Co-authored-by: Rio6 <rio.liu@r26.me>
Reviewed-on: #19
Co-authored-by: Rio <r345liu@localhost>
Co-committed-by: Rio <r345liu@localhost>
merenber added 1 commit 2021-09-17 22:29:44 -04:00
continuous-integration/drone/pr Build is passing Details
d7e9de5f61
install virtualenv on host
merenber added 1 commit 2021-09-17 22:34:13 -04:00
continuous-integration/drone/pr Build is passing Details
0d408e4ed3
Merge branch 'v1' into docker
merenber merged commit de18a9f293 into v1 2021-09-17 22:39:28 -04:00
merenber deleted branch docker 2021-09-17 22:39:58 -04:00
Sign in to join this conversation.
No reviewers
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: public/pyceo#16
No description provided.