Did a takehome for a company recently that did it well. They required that I make a docker file (you could give them one if you wanted) where when ran it would run tests. It was a neat use of docker IMO, it standardized that builds were just “build the docker file” and running was just “run the dockerfile”. You would t have to deal with tar or anything then.

Thousand ways to skin a cat there

deleted by creator

They said they were open to it but they had zero priority of doing it themselves, and essentially “submit a PR if you want it”. A shame really, their interface is great, and such an easy setup. If they implemented either xmpp or matrix I would switch immediately. All of my friends want a discord clone that “just” works, but no one wants to go to this server for this group and then login to that server for that group. They want a single-pane interface like what discord offers.

Shortsighted to not implement that IMO.

Yeah I would assume if anything they would have helped them bring federation

Yeah yeah yeah but ignoring that… Would you?

You can get away with a pretty low bitrate for most. As others have said, set the egress upload limit in the app to whatever you prefer, and just be ready to transcode.

Never charge for access to your server in any way. That is officially 100% illegal. If you can’t do it without charging, you can’t do it

Replicating images isn’t really best practice. Images are meant to be ephemeral on the server. Dockers pattern is to repull the images if they are needed, and that only takes a few seconds. Saving the images IMO would just be a waste of space.

If you are afraid the images will be gone someday, the proper way to handle this is to use a docker registry as a proxy. So you make your own docker registry, like your.tld/registry and then set it in proxy mode. Then when you pull your images you set docker to pull from your registry. If it’s found it will use your local data otherwise it will pull through from the parent registry, and serve the docker image to your client. For backup then you backup the registry’s volume.

That fits within the pattern of docker. Your clients come up, query the local registry, and it will serve your containers. Your server remains ephemeral.

Do you mean docker volumes? If so it’s very easy, just tar where the volumes and and move them over, untar them and map the containers to wherever they should go. Don’t overthink it.

If you mean docker images I’d ask why, can you just repull them?

I also bought Plex lifetime pass also for $100 and I am getting ads like this.

Feel free to go read the multiple writeups from the maintainers that go over each one, we don’t need to copy them all here into the comments for you.

Except they’re spamming to users that they need this subscription even when they host locally or already have a membership.

I paid too, but consider that you basically paid $5 per year for 10 years and I’d say that good. You don’t need to feel guilty if you decide to leave, you got your money’s worth.

(And I mean, I have a sneaky suspicion they’re coming for the lifetime users sooner or later)

It was a pain to get up and running, but now that it is i actually prefer it. OSS aside there are things I like, like editions/versions are all kind of merged, more customization of the appearance, more performant. I’m pretty happy. Granted it was months of reorganizing my media for it.

Yes, but they’re still sending emails to people even when it doesn’t apply. I had a Plex pass and still all of my users received emails and freaked out. They’re trying to trick people into thinking they need to pay, that’s the asshole move here.

I think you’re thinking of MIT though, the commenter was pointing out that AGPL is a license specifically made to do what you want - that people can use it in other open projects, but companies can’t use it in their for profit private software.

I like that it says they are different from projects like TubeArchivist, says “read the readme for why”, and then it doesn’t have an explanation.

I’ve been using TubeArchivist for years now and it’s been great. Solid update cadence, reliable, and I have no idea why this project is different from it

I did synapse about a year ago but kind of wish I had done conduit, it seems so much simpler. That being said, all of the bridges and add-ons assume you’re running synapse

I found proxmox and docker to be fairly incompatible, and went through many iterations of different things to make it work well. Docker in VMs, Docker in LXC, Docker on the host (which felt redundant as hell). Proxmox is an amazing hypervisor, but then I realized I didn’t really need a hypervisor since I was mostly running containers.

My recommendations:

• No need for VMs Just run debian and run containers on it

• Some VMs, Mostly containers, 1 host Run proxmox, and create a VM in proxmox for your contianer workloads

• Some VMs, Mostly containers, >1 host, easy mode Same as above, but make one host debian and the other one proxmox

• Some VMs, Mostly Containers, >1 host, hard mode but worth it after 2 years Use kubernetes, I use k3s. Some nodes are just debian with k3s on them, others are running in VMs on proxmox using the extra compute available. This has a massive learning curve though, it took me well into a year to finally having it at a state I like it - but I’ll never go back.

The only way to be a truly moral person on this planet is to not participate in society and go completely 100% off grid. Even then the Good Place did a great episode on that, and they’re right, you’re not really living then either. It’s all just about what you’re willing to put up with

It’s him, he’s the chosen one. The one who gets to use the software without agreeing to anything. The one who will bring peace