86

Last time I posted a full writeup on my lab (The before before this) there was a lot of questions on what exactly I was running at home. So here is a full writeup on everything I am running, and how you can run it too

top 14 comments
sorted by: hot top controversial new old
[-] Strit@lemmy.linuxuserspace.show 12 points 1 year ago

That is quite an extensive network you got there at home.

Lots of servers, VM's and docker containers working together.

Mine is just 1 small server with a bunch of docker containers running.

[-] herrfrutti@lemmy.world 5 points 1 year ago

Very nice write up. Thank you for sharing. One thing I like to add.

I've personally moved away from nginx proxy manager, because I read an article that it has some vulnerability that don't get fixed in time. Also there are a ton of issues open on git hub. So I move to caddy, witch also is super easy to set up.

[-] GiantPossum@lemmy.world 3 points 1 year ago

Thanks! I'll check Caddy out

[-] Octavius@lemmy.world 5 points 1 year ago

With this amount of servers it seems to be quite a job running and managing all of these. I am running just a few containers and struggle sometimes when there is a major version upgrade to get everything back up running.

How much time do you spend on maintenance for these machines and do you have a tool for it or is it just plain command line? 😯

[-] lazynooblet@lazysoci.al 4 points 1 year ago

Monitoring is the key. I use Zabbix, but essentially you want to gather metrics and report on issues.

Once things are set up and working, even with 10s of VMs and applications, it's quite reliable. The biggest things that catch you out are updates breaking functionality, updates requiring additional manual steps, running out of disk space or expired certificates.

I find I get a spurt of energy to recreate or implement a new system every few months but things just tick over in the meantime.

[-] GiantPossum@lemmy.world 2 points 1 year ago

Not really, I just update containers via Portainer and update the OS with a bash script. Once every few weeks I just roll through them all, only takes 30 mins at most

[-] ZuriMuri@discuss.tchncs.de 1 points 1 year ago

For automated container updates I can highly recommend watchtower. It also works with updates for specific releases/versions where you’re not using the :latest tag. It was also relatively easy to configure for my small setup of 15 containers.

[-] hottari@lemmy.ml 2 points 1 year ago

This guy self hosts!

P.S Microbin added some few private paste options including adding password.

[-] GiantPossum@lemmy.world 1 points 1 year ago

Interesting, I'll admit its been a little while since I went in there. My main concern was the ability to upload files. Text I don't care about too much, but when random people start uploading files, thats a problem

[-] hottari@lemmy.ml 0 points 1 year ago

You can control that with this env variable MICROBIN_NO_FILE_UPLOAD

Checkout the docs for other options.

[-] SpaceRanger@lemmy.world 2 points 1 year ago

You spelled Debian wrong, "OS: Debain 11" ...

[-] GiantPossum@lemmy.world 1 points 1 year ago* (last edited 1 year ago)

Oh jeeeeez! That's what I get for copying and pasting a million times

EDIT: FIXED!

[-] Decronym@lemmy.decronym.xyz 1 points 1 year ago* (last edited 1 year ago)

Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:

Fewer Letters More Letters
Git Popular version control system, primarily for code
HTTP Hypertext Transfer Protocol, the Web
nginx Popular HTTP server

2 acronyms in this thread; the most compressed thread commented on today has 8 acronyms.

[Thread #98 for this sub, first seen 31st Aug 2023, 13:35] [FAQ] [Full list] [Contact] [Source code]

[-] Sup3rlativ3@lemmy.world 1 points 1 year ago

Nice work!

Just to let you know that you've said WS-Test is both 2019 (blurb) and 2022 (specs)

this post was submitted on 31 Aug 2023
86 points (93.0% liked)

Selfhosted

39683 readers
767 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS