mirrors/gotosocial
1
0
Fork 0
mirror of https://github.com/superseriousbusiness/gotosocial.git synced 2025-10-31 12:22:24 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions

[docs] Add a note on cluster support (#2214)

Browse source 
* [docs] Callout no cluster/multi-node support

    Though we have a GitHub issue for this, we don't mention it anywhere in
    the docs. This adds it to the deployment considerations so hopefully
    folks will see it when standing up their own instance.

* [docs] Add daenney as a developer
This commit is contained in:
Daenney 2023-09-20 18:12:31 +02:00 • committed by GitHub
commit d6add4ef93
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 4 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

3
docs/getting_started/index.md
View file

@ -52,6 +52,9 @@ GoToSocial comes with built-in support for provisioning certificates through Let
## Server / VPS ## Server / VPS
!!! bug "Clustering / multi-node deployments"
GoToSocial does not support [clustering or any form of multi-node deployment](https://github.com/superseriousbusiness/gotosocial/issues/1749). Though multiple GtS instances can use the same Postgres database and either shared local storage or the same object bucket, GtS relies on a lot of internal caching to keep things fast. There is no mechanism for synchronising these caches between instances. Without it, you'll get all kinds of odd and inconsistent behaviour.
GoToSocial aims to fit in small spaces so we try and ensure that the system requirements are fairly minimal: for a single-user instance with about 100 followers/followees, it uses somewhere between 50 to 100MB of RAM. CPU usage is only intensive when handling media (encoding blurhashes, mostly) and/or doing a lot of federation requests at the same time. GoToSocial aims to fit in small spaces so we try and ensure that the system requirements are fairly minimal: for a single-user instance with about 100 followers/followees, it uses somewhere between 50 to 100MB of RAM. CPU usage is only intensive when handling media (encoding blurhashes, mostly) and/or doing a lot of federation requests at the same time.
These light requirements mean GtS runs pretty well on something like a Raspberry Pi (a €40 single-board computer). It's been tested on a Raspberry Pi Zero W as well (a €9 computer smaller than a credit card), but it's not quite able to run on that. It should run on a Raspberry Pi Zero W 2 (which costs €14!), but we haven't tested that yet. You can also repurpose an old laptop or desktop to run GoToSocial for you. These light requirements mean GtS runs pretty well on something like a Raspberry Pi (a €40 single-board computer). It's been tested on a Raspberry Pi Zero W as well (a €9 computer smaller than a credit card), but it's not quite able to run on that. It should run on a Raspberry Pi Zero W 2 (which costs €14!), but we haven't tested that yet. You can also repurpose an old laptop or desktop to run GoToSocial for you.

1
docs/index.md
View file

@ -72,6 +72,7 @@ For more information on GoToSocial image licensing, see [here](https://github.co
In alphabetical order: In alphabetical order:
- daenney
- f0x \[[donate with liberapay](https://liberapay.com/f0x)\] - f0x \[[donate with liberapay](https://liberapay.com/f0x)\]
- kim - kim
- tobi \[[donate with liberapay](https://liberapay.com/GoToSocial/)\] - tobi \[[donate with liberapay](https://liberapay.com/GoToSocial/)\]