
2025-09-13 13:39:28
I wonder how many PoE switches across the world have hostname "edgar-allen" or some variant thereof.
I wonder how many PoE switches across the world have hostname "edgar-allen" or some variant thereof.
Just a note for anyone doing patches this weekend. I had a site not come up (didn't notice until this morning). It was throwing this error. Of COURSE this site was front ended with a nginx proxy, so I spent a little wasted time thinking it was related to that. It wasn't. Apache now likes to have a full FQDN hostname in <VirtualHost name:port> directive. This one just had "_default_". I simply out FQDN there, apachectl restart and all is well again.
Just wrote this quickie shell script to create and launch Debian13 KVM VMs. Just provide the hostname. Sharing in case someone else can use this.
The template is the debian13 nocloud image that I expanded to 20 GB. https://cloud.debian.org/images/cloud/trixi…
from my link log —
wtfis: Passive hostname, domain and IP lookup tool for non-robots.
https://github.com/pirxthepilot/wtfis
saved 2025-05-13 https://
And the rabbit hole starts: I had to replace my FritzVPN with Wireguard (Thanks @…, of course not Wire*shark) so that the hostname-resolution in my home network works the way I want/need --- IT'S ALWAYS DNS!!!!
Well, step 1 of this migration is done... Managed to get Backblaze's B2 backend working for the S3 provider, (after spending far too much time to realize that "S3_ENDPOINT" is in fact not "S3_HOSTNAME"...)
I'm not creative so it'll just be social.(newdomain).
I am going to give Glitch a shot to see what all features it can provide. Since it's already an unstable/beta application, I figured I'll just run on master. May switch it to a stabl…
Well, step 1 of this migration is done... Managed to get Backblaze's B2 backend working for the S3 provider, (after spending far too much time to realize that "S3_ENDPOINT" is in fact not "S3_HOSTNAME"...)
I'm not creative so it'll just be social.(newdomain).
I am going to give Glitch a shot to see what all features it can provide. Since it's already an unstable/beta application, I figured I'll just run on master. May switch it to a stable/* branch at some point, but not worth …
Well, step 1 of this migration is done... Managed to get Backblaze's B2 backend working for the S3 provider, (after spending far too much time to realize that "S3_ENDPOINT" is in fact not "S3_HOSTNAME"...)
I'm not creative so it'll just be social.(newdomain).
I am going to give Glitch a shot to see what all features it can provide. Since it's already an unstable/beta application, I figured I'll just run on master. May switch it to a stable/* branch at some point, but not worth …
What's coming in the next version of XS (eXtended Shell)? cpu and us commands. You can now run a single fragment as another user (us) and even on another host (cpu). Example: ```
cpu host {
echo This command is running remotely on `hostname
}
us root {
echo This command is running as `{id -u}
}
```
`ssh` and `sudo` are used to provide this functionality. You can get the source at