![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.world/pictrs/image/8286e071-7449-4413-a084-1eb5242e2cf4.png)
I will definetly look into this. I’ve been using tube archivist for a while now, but it eats so much RAM (especially the Elastic search dependency IIRC)!
I will definetly look into this. I’ve been using tube archivist for a while now, but it eats so much RAM (especially the Elastic search dependency IIRC)!
I prefer the CLI as well, but when I’m not a dev I supervise practical works in programming classes, where I don’t have much saying in the recommended/required tools
I don’t remember exactly, but the issue is about the existence of a button that makes beginners think a commit and a push are part of the same atomic operation. Not the order of the words on this button
The worst thing about eclipse I’ve had to deal with is its git integration. The conflict resolution tool is awful and half the terminology diverges from plain git.
The fact that it has a “Push & Commit” button also drives me mad far more than it should
As usual, I subscribed for the giggles and I keep getting dragged into unsolicited rabbit holes of useful knowledge. Thanks for being an awesome community
I did not try it out yet, but I will make sure I do. I love a lot of things about the approach you described
I can think of some “programming best practices” that can help with reducing merge conflicts, such as making small functions/methods, but I see it as a positive side effect.
I don’t think avoiding merge conflicts should be a goal we actively try to reach. Writing readable code organized in atomic commits will already help you get fewer conflicts and will make them easier to resolve.
I’ve seen too many junior and students being distracted from getting their task done because they spent so much time “coordinating” on order to avoid these “scary” merge conflicts
That was the point of my comment, unless they wrote this ironically.
Sorry you went through the trouble of writing all of this explanation, I hope this is useful to someone else
How do you avoid conflicts happening in the first place?
Might as well use Google drive… Or maybe actually learn to use git? The learning curve is steep but it’s worth investing in it
Well, it kind of makes sense to give a figure in such an unit. It allows you to quickly calculate how much you’re gonna spend on your electric bill (but only if you’re based in the US), since all weird conversions are already done
Well, Watts are just a different way to write Joules per second. The unit we should eliminate is {k,M}W.h which introduce a 3.6 factor in conversions to/from the regular unit system
Each time you send a packet over the internet, several routers handle this packet without touching the source and destination IP addresses.
There is nothing stopping him from configuring the VPS in a way that forwards packets from the home server, rewriting the destination IP (and optionally destination port as well) but leaving the source IP intact.
For outgoing packets, the VPS should rewrite the source (homeserver) IP and port and leave the destination intact.
With iptables, this is done with MASQUERADE
rules.
This is pretty much how any NAT, including ones behind home routers, work.
You then configure the homeserver to use the VPS as a gateway over wireguard, which should achieve the desired result.
I totally agree with w3schools being bad. However, when teaching web dev to beginner students, they usually find the MDN hard to understand and turn to w3schools.
The MDN requires either quite a lot of experience reading documentation, or being shown how to navigate it.
The readme mentions “transcription time on CPU” so it’s probably running locally
Things have been going well for me, using
docker-mailserver
.I followed the setup guide, did everything in the DKIM, DMARC and SPF documentation page. The initial setup required more involvement from me than your standard docker-compose self-hosting deployment, but I got no issues at all (for now, fingers crossed) after the initial setup : I never missed any inbound e-mails, and my outbound e-mails have not been rejected by any spam filter yet.
However, I agree with everyone else that you should not self-host an important contact address without proper redundancy/recovery mechanism in case anything goes wrong.
You should also understand that self-hosting an email address means you should never let your domain expire to prevent someone from receiving emails sent to you by registering your expired domain. This means you should probably not use a self-hosted e-mail to register any account on services that may outlive your self-hosted setup because e-mail is frequently used to send password reset links.