@pserwylo are you still interested to work on this? Otherwise I would take it other since this is the last thing I want to do before doing a release.
Sorry, I didn't explain myself sufficiently.
Docker-compose does indeed pull containers first and only starts them once they are fully available. It even starts them in the right order. However, it is possible that one is starting up faster than another one. The specific problem I ran into was at the first start with empty volumes where postgresql needed some time to initialize its database. The other two containers tried connecting to the database, but failed and then bailed out, so only the database was left running.
In a headless setup, this is of course undesired, so the wait-for
script now waits for the database to become available until a timeout is reached.
username-removed-26331 (bf50e08f) at 04 Oct 19:36
Build docker image from master branch and make compose use it
... and 1 more commit
username-removed-26331 (bb943971) at 04 Oct 19:10
Build docker image from master branch
username-removed-26331 (94e22b79) at 04 Oct 19:08
Build docker image from master branch
... and 244 more commits
@eighthave Here's a source package: repomaker-0.0.4.tar.gz
I tried to make sure that there's source for everything. Only exception is repomaker-static/django_tinymce/jquery-1.9.1.min.js
for which upstream (django_tinymce
) doesn't seem to ship source.
Note that this doesn't include the debian
folder. Is this alright for you?
username-removed-26331 (b94510cd) at 03 Oct 16:32
Disable app edits in the UI when a remote app is tracked
... and 2 more commits
username-removed-26331 (e181e966) at 03 Oct 16:31
Beginning of #175
username-removed-26331 (e181e966) at 03 Oct 16:31
Add prototype docker container
Thanks for testing this @pserwylo!
When trying the npm install
myself, I ran into some issues where one container tried to access another one that was not ready, so now I introduced a wait-for
script that makes the containers wait on each other.
username-removed-26331 (e181e966) at 03 Oct 16:23
Add prototype docker container
username-removed-26331 (1f8bfc23) at 03 Oct 15:45
Add prototype docker container
@pserwylo as you are the only one working with me on repomaker, I'll assign this to you. I acknowledge that it might be difficult for you to review this since you don't know the code base.
This is a larger MR consisting of two commits, one for the backend and one for the frontend.
Adding an app from a remote repository now causes this app to automatically track changes in the remote app. So if something in the remote app changes, it will also change in the local app. That is especially convenient for new app versions.
The user is prevented from editing the local app for as long as the app tracks the remote. There is the option to disable this app tracking in the UI, so manual edits will be possible.
username-removed-26331 (11d83daa) at 03 Oct 14:56
Disable app edits in the UI when a remote app is tracked
The tutorials are a "collection" and so can be paged through
Nice
username-removed-26331 (def8fa97) at 02 Oct 21:23
Track changes in remote app after adding it to local repo
username-removed-26331 (a63fee3c) at 02 Oct 20:21
Track changes in remote app after adding it to local repo
That's a good idea. I can try this. However, there's probably some trail and error involved and that can take quite some time since I get only ~1 CI run a day from travis on weekdays.