- pleroma-postgres renamed to pleroma-database.
- pleroma-nginx renamed to pleroma-proxy.
- site.yml in examples is updated to reflect the change.
resolvesdananglin/pleroma-ansible-playbook#12
The commit adds the option to allow instance admins to
enable or disbale the chat window at the bottom right
of the page. By default the chat window is enabled.
This resolvesdananglin/pleroma-ansible-playbook#10
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 resolvesdananglin/pleroma-ansible-playbook#9 and also
resolvesdananglin/pleroma-ansible-playbook#5
This commit adds support for allowing instances
owners/admins to configure the simple
Message Rewrite Facility (MRF) policy with their
ansible-playbook configuration. With this they can
reject/restrict messages from a list of specified
instances.
Further documentation:
https://docs.pleroma.social/mrf.html#content
This resolvesdananglin/pleroma-ansible-playbook#4
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.
This commit allows instance owners to set a background
image for their Pleroma instances. It copies the image from
the ansible controller onto the target host and updates the
Pleroma configuration.
Owners can set the value for pleroma.config.frontend.background
to set the background image. The default image is used if
this value is not set.
This commit adds support for uploading the site
owner's keybase.txt file onto their Pleroma server
so that Keybase can prove that they are the owner
of their site. This is diabled by default but can
be enabled by the user.
Resolvesdananglin/pleroma-ansible-playbook#1
Removed the 'blockinfile' task and added the
location block for Let's Encrypt in the Nginx
config template. This bloc will be rendered if
Let's encrypt support is enabled.
Part of dananglin/pleroma-ansible-playbook#1
- 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.
When running the pleybook more than once the
ssl_certificate_key line was being overwritten
by the 'lineinfile' tasks because the regular
expression was too greedy. This merge request
uses a stricter regular expression to indentify
and update the ssl_certificate line in the Nginx
configuration.
This merge request changes the project from a single role project to a
single playbook project with multiple plays and roles. The single
playbook has multiple plays with each having its own role to
install and configure the different components to run Pleroma.
(postgres database, pleroma backend and nginx).
Certain playbooks can be executed by specifying the
relevant tags.
This change is the first of many changes to start supporting
installations on both single and multiple hosts.
This change includes also includes:
- inventory file.
- host_vars directory for users to add their variables.
- an init playbook to merge the default and the user defined config for Pleroma.
- users can now specify whether to validate certs when performing acme
challenges (default: true).
- more task templating.
