Disroot-Ansible
/
pleroma
10
0
Fork 0
Code Pull Requests Projects Releases 1 Activity
Role to deploy, configure and manage pleroma https://pleroma.social/
13 Commits 3 Branches 1 Tag 274 KiB
Jinja 100%
Go to file
muppeth 5ae3d33569 Merge pull request 'Switched to akkoma' (#7) from akkoma into main 
Reviewed-on: #7
Reviewed-by: meaz <meaz@no-reply@disroot.org>
 		2023-01-30 15:36:28 +00:00
Playbooks initial commit 2021-11-14 14:56:49 +01:00
defaults fixed remarks by meaz; added extra custom frontend config task 2023-01-11 00:15:59 +01:00
files added akkoma support; changed the way frontends are installed (following akkoma's docs); switched to mangane; updated config templates 2023-01-04 00:21:10 +01:00
handlers initial commit 2021-11-14 14:56:49 +01:00
tasks Merge branch 'akkoma' of git.disroot.org:Disroot-Ansible/pleroma into akkoma 2023-01-11 00:16:08 +01:00
templates added akkoma support; changed the way frontends are installed (following akkoma's docs); switched to mangane; updated config templates 2023-01-04 00:21:10 +01:00
.gitignore initial commit 2021-11-14 14:56:49 +01:00
LICENSE initial commit 2021-11-14 14:56:49 +01:00
README.md added akkoma support; changed the way frontends are installed (following akkoma's docs); switched to mangane; updated config templates 2023-01-04 00:21:10 +01:00
Vagrantfile add acl in vagrant file 2023-01-09 07:05:14 +01:00

README.md

Pleroma/Akkoma role

Pleroma/Akkoma role is was initially based on role by (Luke Hoersten)[https://src.nth.io/ansible-roles/file/2d705e63f6cb/pleroma/otp] with heavy modifications (basically re-written). This role deploys and updates OTP akkoma (default) or pleroma instance. Currently supported distributions are debian based. Role requires disroot's (nginx)[https://git.disroot.org/Disroot-Ansible/nginx] role and (postgresql)[https://github.com/ANXS/postgresql.git]. Other nginx / postgres roles could be used but may require changes in variables.

You can deploy test instance using Vagrantfile attached to the role. vagrant up

ansible-playbook -b Playbooks/pleroma.yml

Then you can then access gitea from your computer on http://192.168.33.15

To update pleroma include upgrade tag.