I was running 2 separate apps for shell/XMPP account registration at @wpn, so far..
This night I made some changes to the original code (provided by Schimon) and I got just one app with account choice - meaning that you must choose what account type you want in the form. Shell accounts are for friends only, as it's always been.
As a consequence of that, I shut down the old address for XMPP account onboarding and left only the main one, which is:
I'm always a bit busy when it comes to pandora (the VPS running WPN: woodpeckersnest.space/eu). I like experimenting new things, fixing/improving existing things.. I cannot stay still 😀
After migrating the homepage to homarr - which took really no time for the initial setup, but a lot of work afterward to fix layouts for mobile devices and non-full-hd screens for desktop PCs - I started messing up with a brand new toy: gemini!!
Not even a week since I installed molly-brown, the actual gemini server, to today, I can count lots of improvements..
amfora for wpn's shell users and also gtl, a tinylog reader, always for the shell.gtl itself, refreshed and published every 5 minutes: can't miss a thing!gemlog mentions starting from a script by @bacardi55, who is the author of many gemini-related things, like the before mentioned gtl software. When I realized it lacked multi-capsules support, I started modifying it and came up with some spaghetti code, which is working surprisingly well and it was deployed earlier today.Onboarding on WPN didn't go as well as I thought, but at least the first user (hey, Mario, I'm looking at you! :) registered and, I believe, everything is working fine for them! On this topic, the onboarding page was migrated from PHP and Email to Python and XMPP, thanks to my friend Schimon! He also kept the UI pretty much intact, so I think most people who looked at it before and after, wouldn't even notice the changes under the hood.
https://hello.woodpeckersnest.space/
Something else I've been doing was setting up: https://invite.woodpeckersnest.space/
which is a landing page to allow people to join an XMPP MUC or add an XMPP contact from a web interface, which will also guide them in choosing a client for their platform. It's rather simple but very useful at the same time.
The chatmail server was upgraded (more or less) at the beginning of August and running smoothly so far; it got some cool new improvements like automatic account deletion after #amount of days from last login and lots of fixes. Total number of registered accounts, so far, is 117.
https://chatmail.woodpeckersnest.space/
Services which I dismissed include:
Jitsi Meet (wasn't really using it and it was wasting quite a lot of resources just to be running)Isso comments service, which powered the old homepage contact section and also a shaarli instance, which is still running but it's more a private thing, rather than a public one.One more proposition: from now on, I will be publishing these (B)log posts in both protocols, HTTP here as you're reading and gemini on roughnecks' gemlog. I will be probably publishing less often than usual though, at least in this format, and send more status updates through the tinylog on WPN, the microlog at Station and my fediverse account.
In the next days I will be monitoring how everything goes and relax a bit, if I manage.. Today I didn't feel so good after a few stressful days, too much computing and too less sleep hours - it's 01:40 AM right now, so yeah, tomorrow will be another of “those” days, I guess.
I'm glad to announce the start of a new gemini server here at WPN, only for shell users:
gemini://woodpeckersnest.eu/
Gemini is an application-layer internet communication protocol for accessing remote documents, similar to HTTP and Gopher. It comes with a special document format, commonly referred to as "gemtext", which allows linking to other documents. Started by a pseudonymous person known as Solderpunk, the protocol is being finalized collaboratively and as of October 2022, has not been submitted to the IETF organization for standardization.
You need a "gemini" client to be able to open that link, the same way you need a browser to open this blog post; I can recommend Lagrange: choose your flavor ^^
The server is powered by molly-brown, author "solderpunk". Thanks
Good day everyone!
This weekend I've been restructuring "woodpeckersnest's" homepage.
The move was pretty huge since I went from a static #HTML plus some #JS site to homarr; it's taking quite a lot of RAM to run now, but the outcome is nice and I like it better than the old style - on mobile, at least on my crap smartphone, doesn't look very good, it needs quite a lot of pixels to perform alright (I hate phones btw, so it's still good for me).
Everything is WIP, but you can take a look at it anyway: https://woodpeckersnest.space
Please let me know if you find anything broken or not working properly. 😍
P.S. I have also upgraded our DeltaChat "chatmail" instance to latest and greatest 1.4.1 release - Thanks Federico for the hosting and Andrea for translations.
Come join us at https://chatmail.woodpeckersnest.space/
Interesting project at https://github.com/henrygd/beszel
Collects resource statistics from one or more systems, display CPU/RAM/DISK/NET/DOCKER information and be alerted in case "event" happens.
These days I set up beszel HUB on my VPS and beszel-agent on the same VPS, on our chatmail server and even on my desktop PC at home on WSL2: so now I'm monitoring 3 systems from a web interface and I'm being notified if one of them becomes unreachable or has exceeded %resources for every type of monitor.
This is my compose.yaml for the HUB and agent on "woodpeckersnest.eu":
services:
beszel:
image: 'henrygd/beszel'
container_name: 'beszel'
networks:
beszel:
ipv4_address: 172.30.0.2
restart: unless-stopped
ports:
- '8090:8090'
volumes:
- beszel_data:/beszel_data
environment:
DISABLE_PASSWORD_AUTH: false
beszel-agent:
image: "henrygd/beszel-agent"
container_name: "beszel-agent"
networks:
beszel:
ipv4_address: 172.30.0.3
restart: unless-stopped
volumes:
- /var/run/docker.sock:/var/run/docker.sock:ro
environment:
PORT: 45876
KEY: "SECRET"
FILESYSTEM: /dev/sda3
networks:
beszel:
name: "beszel"
external: true
volumes:
beszel_data:
external: true
name: "beszel_data"
I created a named docker volume and a custom network beforehand:
docker volume create --name beszel_data
docker network create --subnet=172.30.0.0/16 --gateway=172.30.0.1 beszel
I didn't want to run the agent with network_mode: host, so here's a bridged setup. Network stats on my VPS won't be relevant, since the only net beszel can monitor is the docker bridged one, but I don't care very much.
For chatmail and home desktop I'm running the binary agent, respectively in a systemd unit for chatmail and with a bash script for my PC.
The systemd unit looks like this:
# /etc/systemd/system/beszel-agent.service
[Unit]
Description=Beszel Agent Service
After=network.target
[Service]
Environment="PORT=45876"
Environment="KEY=SECRET"
ExecStart=/home/chatmail/bin/beszel-agent
User=chatmail
Restart=always
[Install]
WantedBy=multi-user.target
The HUB has also got (automatic) backups, locally or on S3 - I tested both without issues. Beszel (both HUB and agent) take almost no CPU/RAM to do their job and stats are easy to read. Even the management tool is quite straightforward and has got the basic stuff right - I skipped OAUTH entirely though, while managing users manually.
Still young project but already recommended 😍
If you're interested in setting this up on WSL2, here I opened a discussion about this topic.. No need to repeat myself 😀
shout-out to "mforester@rollenspiel.social" who posted about beszel on the fediverse and gave me the idea to try it.
this is "Opening Day": finally decided to open fully featured shell accounts' registration on WPN: woodpeckersnest.space/eu for friends.
Who are friends then? Since IRL friends have zero interest in this, my friends are people I know and respect over the Internet, in particular - but not limited to - the XMPP network. They are mostly Italian and English speaking folks, since those are the only 2 languages I know..
This is a first-time experience for me, so give me a few days (a week maybe) to "adjust" and set account(s) up.
If you feel lucky, click the title of this post and apply now! 😏
Continuing from the previous article..
Today while trying to install yet another plugin (Calendar this time), I had a lil incident and destroyed everything 😃
Some hours later I restored a backup and we're up again. BUT! In the process I discovered some SQL errors which I believe were there since a lot ago, always gone unseen.
To make a long story short, I had to disable the standard "Personal Address Book" for everyone, because it was impossible to save any contact in there anyway.. And we are now relying on CardDAV, which is way better.
At one point I had the Calendar plugin working too, alongside CardDAV, but I had (wrongfully) installed it as a local one, so no sync to the cloud with CalDAV; it was later that I tried the CalDAV way by changing the config and shit got me.
Now I asked the people of libera.chat about the plugin, to see if it really supports any CalDAV implementation or not - and then I'll try again :) Feel free to check it out and leave a comment if you know better than me..
https://git.kolab.org/diffusion/RPK/browse/master/plugins/calendar/
and here's the configuration: https://git.kolab.org/diffusion/RPK/browse/master/plugins/calendar/config.inc.php.dist$28
I believe I'm done for today tho.. Looked like a full day's job. Ooh, yes.. Was already forgetting. I also updated the services blob in my website with all the new stuff.
Hello o/
Just completed a new software installment for the "woodpeckers" webmail, powered by roundcube. It's a plugin to manage CardDAV address books, so you can import them in your web contacts; I've tested it with "Radicale Cal/CardDAV" server and the import to roundcube was fast and easy peasy; hopefully it'll be the same for every other compatible server 😎
https://webmail.woodpeckersnest.space/
Yeah, that was all for your local news! Until next.
$ uptime
03:54:18 up 34 days, 8:19, 4 users, load average: 0.00, 0.00, 0.00
$ free -m
total used free shared buff/cache available
Mem: 877 503 159 8 377 374
Swap: 499 87 412
$ df -h
Filesystem Size Used Avail Use% Mounted on
udev 428M 0 428M 0% /dev
tmpfs 88M 8.4M 80M 10% /run
/dev/vda1 9.7G 2.8G 6.6G 30% /
tmpfs 439M 0 439M 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
/dev/vda15 124M 12M 113M 10% /boot/efi
tmpfs 88M 0 88M 0% /run/user/1000
$ ip -s link
2: ens6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
RX: bytes packets errors dropped missed mcast
1444308867 14871375 0 32828 0 0
TX: bytes packets errors dropped carrier collsns
18414348377 21921709 0 0 0 0
$ curl https://chatmail.woodpeckersnest.space/metrics
accounts 83 1719367201634
The etckeeper program is a tool to let /etc be stored in a git, mercurial, brz or darcs repository. It hooks into APT to automatically commit changes made to /etc during package upgrades. It tracks file metadata that version control systems do not normally support, but that is important for /etc, such as the permissions of /etc/shadow. It's quite modular and configurable, while also being simple to use if you understand the basics of working with version control.
https://packages.debian.org/stable/etckeeper
root@pandora:/etc# git log --oneline mumble-server.ini
c1e2238 daily autocommit
2e66cf6 daily autocommit
76fd073 daily autocommit
baaff1c saving uncommitted changes in /etc prior to apt run
9980c10 daily autocommit
830fa84 daily autocommit
0cc8fd9 saving uncommitted changes in /etc prior to apt run
4e7b545 saving uncommitted changes in /etc prior to apt run
20d692a daily autocommit
c05a405 saving uncommitted changes in /etc prior to apt run
3a00635 daily autocommit
62e0e1c Initial commit
root@pandora:/etc# git diff c1e2238 2e66cf6 mumble-server.ini
diff --git a/mumble-server.ini b/mumble-server.ini
index 3332154..d91f520 100644
--- a/mumble-server.ini
+++ b/mumble-server.ini
@@ -236,8 +236,8 @@ logdays=5
; If you only wish to give your "Root" channel a custom name, then only
; uncomment the 'registerName' parameter.
;
-registerName=SpaceNest
-registerPassword=sekret
+registerName=SpaceNest[EN/IT]
+registerPassword=newsekret
registerUrl=https://woodpeckersnest.space/
registerHostname=voice.woodpeckersnest.space
registerLocation=IT