quad
/
weeaboo-space-meta
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Update server info

This commit is contained in:
Quad 2019-11-13 13:59:37 +01:00
parent 755c1e1654
commit bcb89a56fd
1 changed files with 13 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

27
info/Server.md
View File

@ -2,27 +2,26 @@
## Hardware ## Hardware
Weeaboo.space runs on the host [Kiss-Shot Acerola-Orion Heart-Under-Blade](https://kiss-shot-acerola-orion-heart-under-blade.quad.moe/) (Henceforth "Shinobu"), which is a VM from [Hetzner](http://hetzner.cloud/) with the model name "CX31" and the following specs: Weeaboo.space runs on my Proxmox cluster in a virtual machine named "Droite". The hosts each have a E3-1220v2 CPU and 32GB of RAM with 2x1 Gbit network connectivity to a dedicated switch. The virtual machine currently has these specs assigned to it:
- 2 CPU cores (Intel Skylake) - 2 CPU cores
- 8GB RAM - 2GB RAM
- 80GB NVMe SSD - 80GB Storage
- 20TB Transfer
It is located in Helsinki, Finland. (Hetzner's "hel1-dc2") Storage is provided by a Qnap TS-963X over iSCSI on a dedicated VLAN. Currently the virtual machine runs on HDD storage, although I plan to get it onto solid-state storage once I can find a good deal on some quality SSDs. The NAS has over 12TB of capacity, so expansion is not an issue.
The server is located in Florø, Norway.
## Software ## Software
Shinobu runs FreeBSD 11.2 and currently hosts the weeaboo.space pleroma instance exclusively. Droite runs Debian 10 and currently hosts the weeaboo.space pleroma instance exclusively.
Pleroma runs with an unprivileged user (no sudo access) and cannot see processes initiated by other users in applications such as `htop`. Pleroma is configured to be reachable over both IPv4 and IPv6, while pf prevents externals from accessing Pleroma without passing through nginx. Pleroma runs with an unprivileged user (no sudo access) and cannot see processes initiated by other users in applications such as `htop`. Pleroma is configured to be reachable over IPv4, no IPv6 yet unfortunately. I am working on getting some kind of IPv6 setup in place.
Monitoring of the server is handled by [nixstats](https://nixstats.com/) Caching of proxied media is handled by a separate nginx VM named "Loki". As such, proxied media does not affect the storage of the instance itself.
Various rate-limits are in place to prevent spam, although I will not publicly disclose them all, if you get stopped with an error code 503 during sign-up, please wait a few minutes and try again. If you spam an extreme amount of posts, you will also be limited.
## Backups ## Backups
Backups are run to a server that is located both on a different site and on a different host. Hetzner's backup service is also enabled as a failover. Full backups of Pleroma's VM run nightly, these are stored on a separate storage server, so if the main storage server fails entirely, this will not affect the nightly backups. Generally I keep backups a week or two back in time.
The database is backed up every hour, while the pleroma folder containing all data and uploads gets backed up once every two hours. Hetzner's full VM backups are performed between 04:00 and 08:00 every night (GMT+2. While Shinobu is in Finland, Hetzner is a German company. Hetzner does not currently seem to differentiate between the two timezones as far as I can tell)
Recovery will likely be performed from one of Hetzner's backups if it is recent enough. Alternatively the pleroma folder and a database dump will be pulled from my off-site backup server.