4.2 KiB
GoToSocial
GoToSocial is a self-hosted ActivityPub social network server, that this playbook can install, powered by the mother-of-all-self-hosting/ansible-role-gotosocial Ansible role.
Configuration
To enable this service, add the following configuration to your vars.yml file and re-run the installation process:
########################################################################
# #
# gotosocial #
# #
########################################################################
gotosocial_enabled: true
# Hostname that this server will be reachable at.
# DO NOT change this after your server has already run once, or you will break things!
# Examples: ["gts.example.org","some.server.com"]
gotosocial_hostname: 'social.example.org'
# Domain to use when federating profiles. It defaults to `gotosocial_hostname` but you can cange it when you want your server to be at
# eg., `gotosocial_hostname: gts.example.org`, but you want the domain on accounts to be "example.org" because it looks better
# or is just shorter/easier to remember.
#
# Please read the appropriate section of the installation guide before you go messing around with this setting:
# https://docs.gotosocial.org/installation_guide/advanced/#can-i-host-my-instance-at-fediexampleorg-but-have-just-exampleorg-in-my-username
# gotosocial_account_domain: "example.org"
# Uncomment and adjust the following lines to enable GTS to send emails (reports, notifications, password resets etc..)
# Check out https://docs.gotosocial.org/en/latest/configuration/smtp/ for a configuration reference
# gotosocial_smtp_host: 'smtp.example.org'
# gotosocial_smtp_username: ggotosocial@example.org
# gotosocial_smtp_password: yourpassword
# gotosocial_smtp_from: ggotosocial@example.org
########################################################################
# #
# /gotosocial #
# #
########################################################################
After installation, you can use just run-tags gotosocial-add-user --extra-vars=username=<username> --extra-vars=password=<password> --extra-vars=email=<email>"
to create your a user. Change --tags=gotosocial-add-user to --tags=gotosocial-add-admin to create an admin account.
Usage
After installing, you can visit at the URL specified in gotosocial_hostname and should see your instance.
Start to customize it at social.example.org/admin.
Use the GtS CLI Tool to do admin & maintenance tasks. E.g. use
docker exec -it mash-gotosocial /gotosocial/gotosocial admin account demote --username <username>
to demote a user from admin to normal user.
Refer to the great official documentation for more information on GoToSocial.
Migrate an existing instance
The following assumes you want to migrate from serverA to serverB (managed by mash) but you just cave to adjust the copy commands if you are on the same server.
Stop the initial instance on serverA
serverA$ systemctl stop gotosocial
Dump the database (depending on your existing setup you might have to adjust this)
serverA$ pg_dump gotosocial > latest.sql
Copy the files to the new server
serverA$ rsync -av -e "ssh" latest.sql root@serverB:/mash/gotosocial/
serverA$ rsync -av -e "ssh" data/* root@serverB:/mash/gotosocial/data/
Install (but don't start) the service and database on the server.
yourPC$ just run-tags install-all
yourPC$ just run-tags import-postgres --extra-vars=server_path_postgres_dump=/mash/gotosocial/latest.sql --extra-vars=postgres_default_import_database=mash-gotosocial
Start the services on the new server
yourPC$ just run-tags start
Done 🥳