archives/pleroma-ansible-playbook
Archived
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
This repository has been archived on 2023-05-06. You can view files and clone it, but cannot push or open issues or pull requests.
pleroma-ansible-playbook/.gitignore

7 lines
94 B
Text
Raw Permalink Normal View History

final cleanup before production deployment Removed host_vars folder and added inventories folder. This is to support the suggested 'Alternative Directory Layout' in the upstream Ansible documentation. Removed hosts.yml. This may be added in the upcoming examples directory.
2019-11-02 19:30:39 +00:00
inventories/*
!inventories/.gitkeep
feat: add support for uploading custom themes This commit now allows instance admins to: - upload custom themes from their Ansible controller to the themes directory of their Pleoma instance. - set the default theme for their Pleroma instance. This commit also contains the following changes: - explicitly set the background image if not set by the user. - explicitly set the default theme if not set by the user.
2020-02-22 19:39:18 +00:00
vapid-private-key.pem
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
library/__pycache__/
library/*.pyc
Reference in a new issue Copy permalink