vegetaaaaaaa

vegetaaaaaaa, 1 month ago

• What backup service do you use? - Lemmy.world
• What are your backup solutions? - Lemmy.world
• How do you guys back up your server? - Lemmy.world
• How do you backup things to your server? - Lemmy.world
• How to store backups? - Lemmy.world
• How do you backup your data? - Lemmy.world
• Need help with a backup solution - Lemmy.World

vegetaaaaaaa, 1 month ago

See you back on Debian in a few months

vegetaaaaaaa, 1 month ago

docs.nextcloud.com/…/source_installation.html

vegetaaaaaaa, 1 month ago

RSS feeds

vegetaaaaaaa, 1 month ago (edited 1 month ago)

You can definitely replace senders with correct mail addresses for relaying through SMTP servers that expect them (this is what I do):

<span style="font-style:italic;color:#969896;"># /etc/msmtprc
</span><span style="color:#323232;">account default
</span><span style="color:#323232;">...
</span><span style="color:#323232;">host smtp.gmail.com
</span><span style="color:#323232;">auto_from on
</span><span style="color:#323232;">auth on
</span><span style="color:#323232;">user myaddress
</span><span style="color:#323232;">password hunter2
</span><span style="color:#323232;">
</span><span style="font-style:italic;color:#969896;"># Replace local recipients with addresses in the aliases file
</span><span style="color:#323232;">aliases /etc/aliases
</span>

<span style="font-style:italic;color:#969896;"># /etc/aliases
</span><span style="color:#323232;">mailer-daemon: postmaster
</span><span style="color:#323232;">postmaster: root
</span><span style="color:#323232;">nobody: root
</span><span style="color:#323232;">hostmaster: root
</span><span style="color:#323232;">usenet: root
</span><span style="color:#323232;">news: root
</span><span style="color:#323232;">webmaster: root
</span><span style="color:#323232;">www: root
</span><span style="color:#323232;">ftp: root
</span><span style="color:#323232;">abuse: root
</span><span style="color:#323232;">noc: root
</span><span style="color:#323232;">security: root
</span><span style="color:#323232;">root: default
</span><span style="color:#323232;">www-data: root
</span><span style="color:#323232;">default: myaddress@gmail.com
</span>

(the only thing I changed from the defaults in the aliases file is adding the last line)

This makes it so all/most system accounts susceptible to send mail are aliased to root, and root in turn is aliased to my email address (which is the one configured in host/user/password in msmtprc)

Edit: I think it’s actually the auto_from option which interests you. Check the msmtp manpage

vegetaaaaaaa, 1 month ago

github.com/chriswayg/ansible-msmtp-mailer/…/14While msmtp has features to alter the envelope sender and recipient, it doesn’t alter the “To:” or “From:” message itself. When the Envelope doesn’t match these details, it can be considered spam

Oh I didn’t know that, good to know!

The proposed one-line wrapper looks like a nice solution

vegetaaaaaaa, 1 month ago

msmtp never failed me

vegetaaaaaaa, 4 days ago

I agree that desktop/ATX tower PCs are the most useful form factor, you can stuff all your old junk hardware in there and offer it a second life without much investment.

However with current electricity prices buying more power efficient hardware can be a better medium-term investment. 1kWh bills at 0.2516€ currently where I’m at (~EU average price), assuming an average power consumption of 50W this gives you (50×24×365)/1000×0.2516=110€/year. At this rate a 200€ investment in hardware would pay for itself in 2-3 years.

Buying a <100€ setup is not worth it for general purpose servers in my opinion, it will either be underpowered or power hungry.

My current solution is to to run all my services in KVM (libvirt) VMs on my beefy desktop computer which is already on most of the time anyway. Best of both worlds.

If I had to redo everything I would probably buy a NUC/mini-PC with a good CPU, 64GB RAM and low power consumption, stash a single huge SSD in there, migrate my VMs there and call it a day. But this is not a cheap setup.

vegetaaaaaaa, 1 month ago (edited 1 month ago)

How does this compare to awesome-selfhosted.net ?

vegetaaaaaaa, 1 month ago

Don’t mind him. He’s always there ranting about who knows what whenever software he dislikes is mentioned. Lookup his comment history for more of the same.

Easiest method to summon him is to mention Nextcloud and Proxmox in the same sentence.

vegetaaaaaaa, 4 days ago

10000RPM SAS drives are noisy (and expensive), something to keep in mind. If I needed this kind of performance I would probably go full SSD.

vegetaaaaaaa, 1 month ago

Usually you would have a second DNS resolver configured in /etc/resolv.conf (or whatever name resolution config system you are using, resolvconf, systemd-networkd, etc). The system will fall back to this resolver if the first resolver fails to respond (and/or replies NXDOMAIN, I’m not sure. The exact order and fallback conditions may vary depending on which system you use). This can be another dnsmasq instance, a public DNS resolver, your ISP’s resolver, etc. This allows at least basic DNS resolution to work before your dnsmasq instance comes back up.

I would also add automatic monitoring for dnsmasq (either check that the service/container is running, or check the TCP connection to port 53, or check that DNS resolution is working for a known domain, etc)

vegetaaaaaaa, 1 month ago

Not an answer but still relevant: I actively avoid enabling unattended-upgrades for third-party repositories like Docker (or anything that is not an official Debian repository) because they don’t have the same stability guarantees, and rely on other upgrade notification methods instead.

how bad of an idea is this to run a DNS in docker and use it for the host and other containers?

Personally I would simply install dnsmasq directly on the host because it is one apt install and a configuration file away. Keep it simple.

vegetaaaaaaa, 4 days ago

• rsync + basic scripting for periodic sync, or
• distributed/replicated filesystems for real-time sync (I would start with Ceph)

vegetaaaaaaa, 15 days ago

I just don’t have that much time to spend on initial implementation and upkeep

Well k8s is a poor choice of platform for you :D

vegetaaaaaaa, 13 days ago

Netdata can also expose metrics to prometheus which you can then use in Grafana for more advanced/customizable dashboards learn.netdata.cloud/docs/…/prometheus

vegetaaaaaaa, 15 days ago

lsblk also show block devices and is prettier than looking directly at /sys/class/block

vegetaaaaaaa, 1 month ago

If this is a “shared hosting” type of server (LAMP stack), you can usually run PHP applications (assuming they are pre-packaged and don’t need composer install or similar during the install process). Check awesome-selfhosted.net/platforms/php.html

vegetaaaaaaa, 1 month ago

I think Peertube would be overkill for a single channel, but it’s the closest to YouTube in terms of features (multiple formats/transcoding, comments, etc). Otherwise I would just rip the channel with yt-dlp and setup a “mirror” on something simple like a static site or blog. Find something that works, then automate (a simple shell script + cron job would do the trick).