#82 Deployment Tool/Environment

Open
opened 2 weeks ago by hz · 0 comments
hz commented 2 weeks ago

The idea is to have a web site that people go to which hosts a little web app that people can use to deploy Dockerized catsoop instances automatically (including automaticaly setting up Git repos for course content, access control, etc; and maybe including help queues as well). It would be great if those new instances could be subdomains, but it’s probably easiest if they are just hosted on subpaths of the host that is controlling things.

Ike’s great work on catsoop-stack this past term can serve as an outline, but a web site stuck on front to make it completely automated would be nice. The selfish part of that goal is that managing the infrastructure for so many different subjects takes a lot of time, and it’s not good to have myself as a single point of failure (🚌).

Of course, this would really only work for subjects that don’t have timing-sensitive problems, so 6.009 and 6.006 (and maybe 6.036?) will want to stay on their own self-hosted instances, probably.

I’ve been poking away at this a little bit over the last couple of days, and I’m hoping to be able to have a prototype by the end of the weekend week...I’ll post a link to that repo here when it is a little bit closer to actually existing.

The idea is to have a web site that people go to which hosts a little web app that people can use to deploy Dockerized catsoop instances automatically (including automaticaly setting up Git repos for course content, access control, etc; and maybe including help queues as well). It would be great if those new instances could be subdomains, but it's probably easiest if they are just hosted on subpaths of the host that is controlling things. Ike's great work on catsoop-stack this past term can serve as an outline, but a web site stuck on front to make it completely automated would be nice. The selfish part of that goal is that managing the infrastructure for so many different subjects takes a lot of time, and it's not good to have myself as a single point of failure (:bus:). Of course, this would really only work for subjects that don't have timing-sensitive problems, so 6.009 and 6.006 (and maybe 6.036?) will want to stay on their own self-hosted instances, probably. I've been poking away at this a little bit over the last couple of days, and I'm hoping to be able to have a prototype by the end of the ~~weekend~~ week...I'll post a link to that repo here when it is a little bit closer to actually existing.
hz added the
enhancement
label 2 weeks ago
hz added the
devops
label 2 weeks ago
hz self-assigned this 2 weeks ago
hz added the
infrastructure
label 2 weeks ago
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.