![](/static/66c60d9f/assets/icons/icon-96x96.png)
![](https://lemmy.world/pictrs/image/0d5e3a0e-e79d-4062-a7bc-ccc1e7baacf1.png)
it’s also a lesser serving, so healthier.
I’m sorry but this is hilarious. You spent less money and you got less food? Fascinating 😄
it’s also a lesser serving, so healthier.
I’m sorry but this is hilarious. You spent less money and you got less food? Fascinating 😄
I do have nightly off-site backups, that’s true. Still, having the git repo be on the same machine doesn’t seem right to me.
That would fill the same role as watchtower I guess? I’ve previously tried to have a look at having portainer manage the docker compose stack that it’s running inside but at least back then it seemed to be a dead end and not really what portainer is meant to do. I’m not interested in moving away from docker compose at this time.
I’d be a bit concerned with having the git repo also be hosted on the machine itself. If the drives break it’s all gone. I could of course have two remotes but then pushing changes still becomes a multi step procedure.
Oh for sure for sure. I just know that a lot of people use their homelab to learn skills that they can put on their resume when looking for a job. It’s totally fair to over engineer your self hosting setup if that’s your goal.
You should definitely figure out some infra as code system now while it’s manageable. Normally I’d recommend docker-compose as it’s very easy to learn and has a huge ecosystem, but since you’re using proxmox you might need to look at ansible like the other commenter said. Having IaC with git makes it so much easier to test new stuff, roll changes back, and all that good stuff, in addition to solving your original problem of forgetting what is running where.
Just find the simplest IaC solution possible. Unless you are gunning for a job in infrastructure you don’t need to go into kubernetes or terraform or anything like that, you just need something reproducible that you can easily understand and modify.
Ah, fooled by the title yet again!
Quick feedback: your css transitions are way too long, opening the hamburger menu should not make me feel like I’m waiting for it to open.
Also you’ve gone for the card layout on the app list, however cards create the expectation that they are actionable yet clicking them does nothing. At least make the app names clickable.
I started seeing this too. Interestingly pulling individual images works, it only does this when trying to pull all the images.
I’m using brave mixed with a network wide ad blocker, so while it’s nice that Firefox has UBO I’m fine without. Firefox has been presenting these issues every time I’ve tried switching, so for about a year now, so no not a recent issue.
This is great but I literally can’t use the base app on my S20. Like clicking on Google search hits causes the app to freeze. Trying to scroll up on a page triggers a reload 30% of the time. I want to use Firefox but it’s nowhere near good enough, and adding extensions on top of that state is not going to help.
Gotta know, are you serious or joking here? Follow up question: are you a developer and have you ever worked on a medium+ sized project? The amount of dependencies you end up with is astounding, you can’t just “know” when all those APIs changed, that would be a full time job just to stay on top of. And that’s not even taking into consideration transitive dependencies. If a library doesn’t use semantic versioning, 99% of the time it’s correct to avoid it just to save yourself the headache.
?? this is exactly what a random soldier’s POV at Dunharrow would have been.
Shhh, they don’t know what that means, let them live in bliss
TTL on all content scales extremely poorly. You touch on this but I don’t think you appreciate just hope big of a SELECT * WHERE TTL ...
this would be in just a few months/years.
As an alternative, every instance sync should come with a list of newly deleted users. Retrying would not need to be reimplemented. If a user who wishes to be forgotten has had their home instance go dark, there will need to be a way for them to prove ownership over the original account (signup confirmation email perhaps) so a delete can be started from a foreign instance.
Came to write basically this. I would try caddy but my compose file is 600 lines long now and half of that is traefik labels, I can’t be arsed with the migration.