4.7 KiB
Bare metal
This guide walks you through getting GoToSocial up and running on bare metal using the official binary releases.
Prepare VPS
In a terminal on the VPS or your homeserver, make the directory that GoToSocial will run from, the directory it will use as storage, and the directory it will store LetsEncrypt certificates in:
mkdir /gotosocial && mkdir /gotosocial/storage && mkdir /gotosocial/storage/certs
If you don't have root permissions on the machine, use something like ~/gotosocial
instead.
Download Release
In a terminal on the VPS or your homeserver, cd into the base directory for GoToSocial you just created above:
cd /gotosocial
Now, download the latest GoToSocial release archive corresponding to the operating system and architecture you're running on.
(You can find the list of releases right here, arranged with the newest release at the top.)
For example, to download version 0.5.2 for running on 64-bit Linux:
wget https://github.com/superseriousbusiness/gotosocial/releases/download/v0.5.2/gotosocial_0.5.2_linux_amd64.tar.gz
Then extract it:
tar -xzf gotosocial_0.5.2_linux_amd64.tar.gz
This will put the gotosocial
binary in your current directory, in addition to the web
folder, which contains assets for the web frontend, and an example
folder, which contains a sample configuration file.
Edit Configuration File
Copy the configuration file from the example folder into your current directory:
cp ./example/config.yaml .
Now open the file in your text editor of choice so that you can set some important configuration values. Change the following settings:
- Set
host
to whatever hostname you're going to be running the server on (eg.,example.org
). - Set
port
to443
. - Set
db-type
tosqlite
. - Set
db-address
tosqlite.db
. - Set
storage-local-base-path
to the storage directory you created above (eg.,/gotosocial/storage
). - Set
letsencrypt-enabled
totrue
. - Set
letsencrypt-cert-dir
to the certificate storage directory you created above (eg.,/gotosocial/storage/certs
).
The above options assume you're using SQLite as your database. If you want to use Postgres instead, see here for the config options.
Run the Binary
You can now run the binary.
Start the GoToSocial server with the following command:
./gotosocial --config-path ./config.yaml server start
The server should now start up and you should be able to access the splash page by navigating to your domain in the browser. Note that it might take up to a minute or so for your LetsEncrypt certificates to be created for the first time, so refresh a few times if necessary.
Note that for this example we're assuming that we're allowed to run on port 443 (standard https port), and that nothing else is running on this port.
Create your user
You can use the GoToSocial binary to also create and promote your user account. This is all documented in our Creating users guide.
Login
You should now be able to log in to your instance using the email address and password of the account you just created.
(Optional) Enable the systemd service
If you don't like manually starting GoToSocial on every boot you might want to create a systemd service that does that for you.
First stop your GoToSocial instance.
Then create a new user and group for your GoToSocial installation:
sudo useradd -r gotosocial
sudo groupadd gotosocial
sudo usermod -a -G gotosocial gotosocial
Then make them the owner of your GoToSocial installation since they will need to read and write in it:
sudo chown -R gotosocial:gotosocial /gotosocial
You can find a gotosocial.service
file in the example
folder on github or your installation.
Copy it to /etc/systemd/system/gotosocial.service
:
sudo cp /gotosocial/example/gotosocial.service /etc/systemd/system/
Then use sudoedit /etc/systemd/system/gotosocial.service
to change the ExecStart=
and WorkingDirectory=
lines according to your installation.
If you have been following this guide word for word the defaults should be fine.
After you're done enable the service:
sudo systemctl enable --now gotosocial.service
(Optional) Reverse proxy
If you want to run other webservers on port 443 or want to add an additional layer of security you might want to use a reverse proxy. We have guides available for a couple of popular open source options and will gladly take pull requests to add more.