I honestly just did it to try to get cleaner logs having the container only be responsible for the proxying.
I honestly just did it to try to get cleaner logs having the container only be responsible for the proxying.
I’ll try that, but since I haven’t been able to find any related issues I’m pretty sure it’s a configuration error on my part. Hehe the regretfully long post. Next step will probably be to open an issue on authentik’s GitHub but since I think it’s a pebkac I would prefer not to waste their time.
If you want to do this, what you probably want is to pump your logs into a log drain, something like betterstack is good. They then allow you to set up discrepancy thresholds and can send you emails when something seems to be out of the ordinary. There’s probably a self hosted thing that works the same way but I’ve never found a simple setup. You can do the whole Prometheus, influxdb, grafana setup but imo it’s too much work, and then you still have to set up email smtp separate from that.
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.
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 know you didn’t mean it like this, but the result from this line of thinking is that we only try to put women on equal footing with men in tech when it’s convenient for men because times are good. Which in turn means we never put women on equal footing because the needs of men always come first.
Put differently women have to deal with being women in tech on top of times being desperate, men only have to deal with times being desperate. Things like this are why spaces like these are necessary in the first place, and if you break them down at the first discomfort you’re not a working class hero fighting the capital, you’re tearing down women and setting everyone back.
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
Not judging you for your reasons, but you don’t speak for everyone so calm down with the “we” pronoun.
Don’t know why you were down dooted, that’s absolutely true and exactly how I feel, and how everyone I’ve talked to about copilot feels.