I use a Backuppc instance hosted on an off site server with a 1Tb drive. It connects through ssh to all my vms and backups /home and any other folders i may need. It handles full and incremental backups, deduplication, and compression.
I run my own email server using Mailcow. It works well.
However, I do not even attempt to directly send outbound email. It's very difficult to get your server trusted by the major providers, especially Microsoft (who are very picky about email servers). I have an account with MXRoute (which is an email provider) but only use it for outbound relaying. Inbound emails go directly to my server.
For what it's worth, MXRoute is a great provider to consider if you want to move away from the large ones (Google, Microsoft, etc) but don't want to self-host.
There's various outbound mail providers, and some have free plans. For example, SMTP2Go is free for 1000 emails per month, and Mailgun is free for 5000 emails per month. What you'd do is set up your own email server, and configure it to relay via SMTP2Go or Mailgun. Your client systems don't need to know this - they just send their emails to your server, which then relays them to the relevant service.
I use Mailcow and all of this is configurable in its web UI. No need to edit config files.
Nice. That is way more emails than I ever deal with in a month. Maybe in a year. I am really conservative with my online stuff, mostly because I hated the idea of managing so much crap even if it is something I want.
So, I am going to play with Mailcow, Mailinabox, and iRedMail.
Good choices! I also tried those three. Mailcow was my favourite but maybe you'll like one of the other ones better. Mailcow uses Docker (which I prefer compared to installing software directly on the system) and has a nice admin panel. They're all good choices though.
You don't need to know too much about Docker to use Mailcow. It comes with a preconfigured docker-compose.yml so you just need to install Docker and follow Mailcow's installation instructions (which are pretty straightforward)
If you have any spare domains that you aren't using (or domains you're not currently using email with), you could test it out with that domain before moving any domains you care about :) That's what I did.
Right on. The first domain I will buy will be a personal fun one, just to experiment and mess around. I don't quite know what professional name I want for my domain, since I don't have a brand or anything, and having just my name seems odd.
I use Borgbackup 1.2.x. It works really well. Significantly faster than Duplicity. Borg uses block-level deduplication instead of doing incremental backups, meaning the backup won't grow indefinitely like with duplicity (this is why you have to periodically do a full backup with Duplicity). The Borg server has an "append-only" mode meaning the client can only add data to the backup and not remove it - this is useful because if an attacker were to gain access to the client, they can't delete all your backups. This is a common issue with other backup systems - the client has full access to the backup, so there's nothing stopping an attacker from erasing the client system plus all its backups.
For storing the backups, I have two storage VPSes - One with HostHatch in Los Angeles ($10/month for 10TB space) and one with Servarica in Montreal Canada (3.5GB space for $84/year).
Each system being backed up performs the backup twice - Once to each VPS. Borgbackup recommends this approach over only performing one backup then rsyncing it to a different server. The idea is that if one backup gets corrupted (or deleted by an attacker, etc), the other one should still be OK as it's entirely separate.
For anyone who isn't a developer: contributing is not just code.
Monetary donations help developers to continue their work, supporting them in their journey much as the brave Samwise supported Frodo. They ensure the continuity of the project, allow developers to dedicate more of their time to it, and help them acquire resources they may need.
Yet not all of us are blessed with the wealth of the Lonely Mountain, and that is entirely acceptable. For in the land of FOSS, gold and silver are not the only treasures that matter. The donation of your time and skills can be as valuable as a chest full of gold.
When you come across a bug, it can be reported, much as Pippin reported his sighting of the Nazgul to Gandalf. Yet remember, respect is key, as it was in all communications among the Fellowship. A bug report, properly done, is a gift to the community, a contribution to the common good. But it should be given with care, with thoroughness, and with the respect due to a fellow traveler on this digital road.
Finally, consider the hobbits who remained in the Shire, who, though they did not journey far, spread tales of courage and bravery, keeping spirits high and ensuring the story was known. If you love a piece of FOSS, speak of it, share it, let others know. In the vast, interconnected realm of the Internet, word-of-mouth travels faster than Shadowfax.
Every contribution, every bit of help, is more than welcome. It is cherished. It is celebrated. For in the realm of FOSS, as in Middle Earth, we are all on this journey together.
Naturally, if you are gifted with the skills of a dwarf smith, able to delve into the deep code and fix bugs or add features, your contribution will be celebrated like Gimli’s axes in the Battle of Helm’s Deep. A good pull request is a bard’s song that echoes across the halls of digital Middle Earth, a melody that can inspire others and boost morale.
Indeed! Writing documentation is also extremely helpful; it's like Bilbo penning Middle Earth's lore, guiding users through the software's labyrinth. Your efforts, whether clarifying existing documents or spreading knowledge, light our collective journey like the Elves' light of Eärendil. Each addition or improvement is celebrated; it's our shared saga.
To add to other suggestions here, my current setup is just using folders with markdown or any other text files in a webIDE. In my case that's Code-Server as I prefer a more centralized solution, and I get the benefits of keeping everything in version control.
I also have a Raneto instance pointing to my "Documents" folder which presents it all in a knowedge-base like format.
If you're looking for something with mobile app integration this probably won't work by itself; while the webapp for Code-Server works on mobile, it's "cramped" at best.
I do something similar with FolderSync and SftpGo and have Drafting (vague name) to create and edit notes.
As for version control I just have all of the documents in a git repository on my Code-Server instance which I regularly commit and sync with a local Gitea deployment; nothing special. Though it could be possible to use something like Mgit with a Tasker automation in lieu of a data sync with foldersync/syncthing, I just haven't looked into it in earnest.
That's interesting, it never crossed my mind that I could run git on my phone. But I think I want to look for a way to auto commit every day on my code-server instance, not sure if that's possible at all. Drafting app looks nice, I'll have a try
That should be pretty simple to do with cron and a shell script. Whether you can easily do that within the container depends on who packaged it though.
Paperless NGX on a Raspberry 4. No more paper documents at home... Everything that still comes by mail is instantly scanned and shredded. Emails are also scanned and attachments are added automatically, if important.
selfhosted
Hot
This magazine is from a federated server and may be incomplete. Browse more on the original instance.