spaghetti_carbanana

@spaghetti_carbanana@krabb.org

This profile is from a federated server and may be incomplete. Browse more on the original instance.

spaghetti_carbanana,

Will be better when it’s over. Last week in a job that my days are numbered in, hopefully the next adventure will be more energising.

By the way, when I upgraded from 0.17.4 to 0.18.0, I noticed the UI for blocking instances changed and was missing my list in the admin panel (still visible on the /instances page). I added a blocked instance and it nuked my entire pre-0.18 list. Might have been a freak accident but it might be worth making a copy of Beehaw’s first just in case. Oh and it’s no longer comma-separated, you have to add them one-by-one

spaghetti_carbanana,

Proxmox might be what you’re looking for, it’s very popular among homelab users and allows you to run VMs and Containers natively so you have the best of both worlds.

As to which you should use (Docker or VMs), neither is a silver bullet. I’m going to oversimplify it a bit, but in a nutshell:

Containers lend very well to microservices like web apps and processes you want to run isolated but don’t need a whole VM for. I can go into this in more depth if it helps you.

VMs are better suited when you have a disproportionately more resource hungry service (like database servers). They also allow easier deployment of things alongside the application, for example if you have monitoring agents. The downside is VMs add a maintenance overhead for the underlying OS (this is true of containers too but less so as you’ll often run many containers on one host).

In my environment I use VMware ESX for the hypervisors, manage it with vCenter and run mostly Linux machines with a mix of traditionally installed services and Docker standalone. There are some highly resource intensive services that even get their own physical host, like my NVR (for CCTV cameras) and backup server.

Hope I’ve answered more questions than I’ve created!

spaghetti_carbanana,

Oh and by the way, it’s easy to feel overwhelmed starting out in this. My advice is to set yourself small, achievable goals to help break it up. Start by doing your hardware upgrade, then work out what your host OS will be and install it. Then work out how you want to use it, what you want to containerise, what you want to run in VMs.

be prepared to knock it all over and start again. Everyone rebuilds their environment, usually after learning how they could do it better. And most of all, have fun!

spaghetti_carbanana,

I’m the admin of krabb.org, honestly I’m loving it. There is a learning curve, particularly for non-technical folks, but that will get easier as time goes on.

As an admin, it is far easier to “jump start” an empty Lemmy instance with content from other instances than it is to do with Mastodon and Pixelfed.

Where we need to improve is the mobile apps, documentation and providing ways to make it easier for small instances to get new users. These are all very much in the spotlight and improving every day (especially the apps), so I’m confident we can get there

Tldr: it good, do like

  • All
  • Subscribed
  • Moderated
  • Favorites
  • anitta
  • thenastyranch
  • rosin
  • osvaldo12
  • GTA5RPClips
  • love
  • Youngstown
  • slotface
  • khanakhh
  • everett
  • kavyap
  • mdbf
  • DreamBathrooms
  • ngwrru68w68
  • megavids
  • magazineikmin
  • InstantRegret
  • normalnudes
  • tacticalgear
  • cubers
  • ethstaker
  • modclub
  • cisconetworking
  • Durango
  • provamag3
  • tester
  • Leos
  • JUstTest
  • All magazines