Commit graph

8 commits

Author SHA1 Message Date
20667709b2
ci: test environment docker image for CI pipelines
This commit includes a Dockerfile for building a test environment for
future CI pipelines. This commit also refactors the GitLab CI pipeline
files by splitting the jobs into different files:

- .gitlab-ci.yml: Global CI pipeline file.
- .gitlab/ci/test-env.gitlab-ci.yml: Jobs to test and publish the
docker image for the test environment.
- .gitlab/ci/playbook.gitlab-ci.yml: Jobs to test and publish the
docker image for the pleroma playbook
- .gitlab/ci/templates/docker.gitlab-ci.yml: Template jobs for
testing and publishing docker images.

Part of dananglin/pleroma-ansible-playbook#17
2020-07-10 07:22:39 +01:00
d9c0ef5c87 install client for hashicorp vault 2020-05-29 20:35:24 +00:00
00bda402ab
fix: install sshpass for testing purposes.
- also added missing build arguments for labelling
2020-05-29 20:41:42 +01:00
ed709517c0
ci: push Docker image to container registry
Update the CI pipeline file and Makefile to
push the Docker image on tagged releases.

Part of dananglin/pleroma-ansible-playbook#14
2020-04-23 00:59:53 +01:00
0cedf15ad9
feat: add Dockerfile to Dockerise the playbook
- Add Dockerfile to install Ansible and the playbook.
- Add Makefile target to build the image.
- Add Makefile target to run the playbook.
- Add the playbook that ansible will run.
- Add .dockerignore to limit the files added to the context.
- Added a pipeline job to test the image build.
- Added a pipeline job to lint the Dockerfile.

This closes dananglin/pleroma-ansible-playbook#13
2020-04-22 19:21:59 +01:00
c9aad82027
fix: implement an upgrade procedure for Pleroma.
This commit implements different installation paths when
running the pleroma-main role, depending on whether Pleroma
needs to be installed for the first time or upgraded.

For first time installations the playbook will run through
the normal download and installation process and also executes
the database migration. If Pleroma is already installed then,
by default, the playbook will not re-install Pleroma or re-run
the database migration. If the user wants to update Pleroma to
a newer version then they can re-run the playbook with the
command-line argument '--extra-vars enable_pleroma_upgrade=True'.

This commit also introduces a custom module used to compare the
installed and downloaded semantic versions of Pleroma.
The playbook uses this to see whether the version change is an upgrade,
a downgrade or no version change. If it's an upgrade the playbook
will proceed with the re-installation of Pleroma. If there is no
change then the playbook will skip installation. Finally if
it detects that the user is trying to downgrade Pleroma then it will
fail.

This commit resolves dananglin/pleroma-ansible-playbook#9 and also
resolves dananglin/pleroma-ansible-playbook#5
2020-03-06 12:04:48 +00:00
6f5dbdbbe4
fix: add common play to site playbook
- Added missing play for the common role
- Updated common role. Verbose logging for SSHd.
- Updated Makefile. Added a rule for generating
the Vapid keypair together.
2019-11-03 05:24:12 +00:00
b0ddbc30ad
added: configuration for Pleroma
This merge request adds the template file and default variables for
configuring Pleroma.
Also included in this merge request are:

- added: Makefile to produce the secret key base, signing salt and the
public and private keys for web encryption.
- fixed: Pleroma OTP builds are now downloaded from the stable branch.
- changed: removed data from the pleroma task and added them in the
variable directory.
2019-10-15 09:16:24 +01:00