You have xing, but it's big in DACH countries only and its still owned/ruled by a company. Roll up our own website and socialize / network with like minded people on the fediverse instead.
krash
joined 3 years ago
Sorry for the off topic question, but what are the gains / constraints of using an identity / authentication service? Sure, you only are going to need to remember one password/identity. But each webapp must have support for the said protocol, and so does their clients, no? It does seem like a lot of work (and risk exposure) for little gain.
Please enlighten me if I'm missing something.
Only 80%?!? I assume *BSD isn't counted in that number. I really can't see people running windows on their servers...
And to be honest, server stability != display server stability.
Is there a decent tutorial on how to get it up and running on standard services such as systemd events, fail2ban etc? There is no quick start guide on their site.
Welcome to the cult!
We all started as beginners, but before you start, take my advice and avoid hosting anything open to the internet until you've gained more experience in OS/network hardening and risk assessment.
First off, I think you're starting on a good footing. Having TCP/IP knowlege is good, but you don't need it from the beginning - it will be relevant once you get into network segmentation and setting up reverse proxies.
I'd say the first thing is to actually choose a rather simple (but useful) application that you can host on Docker and get some experience from OCI-containers and disaster recovery. A lemmy instance (even non federated) might be too much to begin with. Have you considered paperless-ngx, fresh-rss or even syncthing instead? Or begin with formulating what problem you want solved in your daily life.
I'd say, start by watching this video series to gain a better understanding of Docker (I've so far assumed that you won't do baremetal installs, right?!??). There's also a pretty good online-lab for you to play around in. Remember, you'll propably realise that your first deployments could be better, and keep yourself mentally prepared to redo and rebuild eventually.
Feel free to message me if you want guidance going forward!
Me neither, but I'd love to hear those arguments.
Apache license 2.0
I like 3-2-1-1-0 better. Like yours, but:
- the additional 1 is for "offline" (so you have one offsite and offline backup copy).
- 0 for zero errors. Backups must be tested and verified.
One feature foot is missing is ligatures. So if that is important to you, you'll need to look for an alternative.
The dev of foot is an awesome person though, so that could offset the missing feature for some :-)
This looks really slick! I don't use ansible though, can I still benefit from running it?
Edit: just realized that your project has a larger scope than this, but still awesome to see how you solved the homepage feature.
Many have already mentioned Obsidian, I too ventured to it from Joplin and couldn't be happier.
Other (FOSS) tools I use for productivity... GUI tools:
- nocodb - a web-based database which can be accessed over API too
- I'm keeping an eye on vikunja.io, hope to have it mature and implement more features regarding project management
- paperless-ngx, make order of your paper-mess.
CLI tools:
- Fish - a very nice and modern shell
- chezmoi - a really nice dotfile manager
- lsd instead of ls, dust instead of du, zoxide instead of cd
- kopia - awesome backup tool. How backup is related to productivity? Disaster recovery ;-)
What circumstances would that be? I can't see the use case doe this, but I'm open to see how and when that would be needed.