if they would stop calling it vandalism, it would take away all the fun
if they would stop calling it vandalism, it would take away all the fun
idk, maybe like a server for “-key”-derivates with a community for each individual derivate?
Some of these derivates will be hugh, but reddit-like sites can already deal with communities of vastly different sizes, so whatever i guess.
except for the first all of these are interesting. As for the first: I am pretty sure there are nazis on both sides, and the Azov-thing is a very very flimsy excuse for the war.
.azw3
didn’t they switch to epub last year?
so… netflix with extra storage?
If you can’t afford to tip after getting a new car, you should probably get an older car.
fun fact: most people DO tip for new cars. Only the tip is factored in into the initial price, which already includes 50-100% markup, which gives the dealer room to abate.
gaming chair was invented in 2006
is this true?
reliably maintaining services
it’s funny that you use that as a selling point.
In my experience almost no outage happens because hardware failures. And most outages happen because bad configurations and/or expired certs, which in turn are a symptom of too much complexity.
thanks. I forgot about that. But I’d like to add, that this models kind of feels like “donations with extra steps” to me. i.e. you can get it for free, but you choose to pay the developer even though you have to.
because of all the socialist propaganda in it?
there is plenty open source software, that you can buy. There are many modes:
and my personal favorit:
I feel you. I am down like 12€ at this point
fun fact: this is called “Reductio ad absurdum” and it’s a valid strategy in debate/rethoric.
It works great when countering stupid shit that sounds logical but really isn’t.
There Are Two Types Of People in this world:
Also the entire “terrorists in the middle east” thing is on him.
I recommend to use relevativ paths in the compose files. e.g.
- '/home/${USER}/server/configs/heimdall:/config'
becomes
- './configs/heimdall:/config'
you may want to add “:ro” to configs while you are at it.
also I like to put my service in /srv/ instead of home.
also I don’t see anything about https/ssl. I recommend adding a section for letsencrypt.
when services rely on each other, it’s a good idea to put them into the same compose file. (on 2nd thought: I am not sure if you already do that? To me it is not clear, if you use 1 big compose file for everything or many small ones. I would prefer to have 1 big one)
you can use “depends_on” to link services together.
you should be consistent with conventions between configurations. And you should remove config-properties that serve no purpose.:
while you are at it, you may want to consider using an .env file where you could move everything that would differ between different deployment. e.g.
consider using podman instead of docker. The configuration is pretty much identical to docker-syntax. The main difference is, that it doesn’t require a deamon with root privileges.
you may want to consider to pin version for the containers.
pro version pinning:
con version pinning:
semi-related: would it count as piracy, if you reconstruct the 3d model from the 2d promo-images?