The project service should send updates to the master service. The functionality already exists on the master service.

Send a POST request to the url in the env var FLOCK_COMM_URL with the required param secret_key (in the env var FLOCK_PROJECT_SECRET) and the optional param worker_count.

I can add new fields if we come up with use cases for them.

Deployment is currently done on the main thread, which makes (primarily admin facing) requests really slow when they do deployment work, in the range of ~45s.

From some rudimentary research, flask won't block me from using different threads, but it will block me from referencing the current_app object from the other thread, which also means no database access.

The answer to this problem will be marking some functions as background functions and making others do the foreground work. For instance, call deploy_project on the main thread, which gathers the necessary parameters and database writes, which then calls start_container in the background, who will have no references to current_app or get_db.

https://github.com/priologic/easyrtc/blob/master/LICENSE

We need to host two javascript files:
/easyrtc/easyrtc.js
/socket.io/socket.io.js

We need to figure out how we want to manage this.

1. We could rehost the javascript files not in the repo (I don't know where they are right now?)
2. We could copy the files into our repo (would need to check the license on redistribution)
3. We could link to an existing source of the files online

Any other options?