And then a new version of the site is up. We might do other stuff though soon (turning services on/off, migrating the database, backing up something, saving uploaded book files, etc.). It would be nice to just run what we do manually with Ansible:
So, when I run Ansible now, after some commits come in, we do (more or less):
* [Get the new code](https://git.vvvvvvaria.org/decentral1se/xppl/src/branch/master/ansible/roles/git/tasks/main.yml#L9)
* [Install the Python dependencies](https://git.vvvvvvaria.org/decentral1se/xppl/src/branch/master/ansible/roles/pipenv/tasks/main.yml#L15)
And then a new version of the site is up. We might do other stuff though soon (turning services on/off, migrating the database, backing up something, saving uploaded book files, etc.). It would be nice to just run what we do manually with Ansible:
> https://git.vvvvvvaria.org/decentral1se/xppl/src/branch/master/ansible/README.md#run-it
We don't even have a CI build on Gitea, so how can we even get this to run after things get merged?
Would be nice anyway, we'll probably get there.
This may be a bit too flashy for now.
We don't even have a CI build on Gitea, so how can we even get this to run after things get merged?
Would be nice anyway, we'll probably get there.
So, when I run Ansible now, after some commits come in, we do (more or less):
And then a new version of the site is up. We might do other stuff though soon (turning services on/off, migrating the database, backing up something, saving uploaded book files, etc.). It would be nice to just run what we do manually with Ansible:
This may be a bit too flashy for now.
We don't even have a CI build on Gitea, so how can we even get this to run after things get merged?
Would be nice anyway, we'll probably get there.