gmn.clttr.info

Unnamed repository; edit this file 'description' to name the repository.
git clone git://code.clttr.info/gmn.clttr.info.git
Log | Files | Refs

commit 7807718121acdab3e180b1adddb5f0489c08ac6d
parent 472f7ade020fbed916ab756138aebb73b363df3f
Author: René Wagner <rwagner@rw-net.de>
Date:   Sun, 22 Nov 2020 19:53:49 +0100

fix lists

Diffstat:
Mhosting.gmi | 30+++++++++++++++---------------
1 file changed, 15 insertions(+), 15 deletions(-)

diff --git a/hosting.gmi b/hosting.gmi @@ -8,10 +8,10 @@ The "server" is based in a small basement room in my house. There's no need for Connection to the outer world is served by a asynchronous DSL connection with 100 MBit down, 30 MBit up stream. The machine itself is: -- Celeron J4105 quad-core accompanied by 8 GB RAM -- 2 SSD: 128 GB / and 1TB /data -- small case with integrated power supply -- idle power consumption (whole system): ~9.5 W +* Celeron J4105 quad-core accompanied by 8 GB RAM +* 2 SSD: 128 GB / and 1TB /data +* small case with integrated power supply +* idle power consumption (whole system): ~9.5 W I prefer the KISS principle, thus i use a very simple partitioning scheme with ext4/xfs. No LVM, btrfs or other fancy tools - the benefits of this are not relevant for my use case. In case of a failure it is very important for me to be able to access the data without complicated toolings. The failure is enough stress, no need to increase it even more with tools i'm not familiar with. @@ -19,10 +19,10 @@ A UPS will so be added to the setup. ## tooling -- Debian Buster with Backports -- Gemini: gmnisrv -- Web: Apache 2 & PHP-FPM -- Monitoring: monit +* Debian Buster with Backports +* Gemini: gmnisrv +* Web: Apache 2 & PHP-FPM +* Monitoring: monit ## services @@ -34,22 +34,22 @@ A UPS will so be added to the setup. ### web -- private Nextcloud instance including TURN server -- private selfoss instance -- KiwiIRC +* private Nextcloud instance including TURN server +* private selfoss instance +* KiwiIRC ### other -- NFS server -- DLNA (with miniDLNA) +* NFS server +* DLNA (with miniDLNA) ## backup strategy Everyone who ever suffered data loss (and a few who don't) might be aware that a valid backup strategy is essential. My backup strategy is split in 2 parts: -- semi-automatic local backups -- automatic "cloud" backup +* semi-automatic local backups +* automatic "cloud" backup ### local backups I have 3 hard disks which hold a rotating backup that is created once a week. The disks rest in a fire-prove safe in my house.