The answer to the first two questions are helm charts. They are collections of parametrized yaml files and the most popular way to install things into k8s. You just need one config file for each helm release (values.yaml).
If you want to go declarative with gitops rather than imperative, check ArgoCD or flux.
Thank you for the info. I thought the *key instances and maybe pleroma already had it and wanted to see how it looks. But I’m almost exclusively using an app anyways so I should be looking how Tusky implements it anyways.
I wonder why there’s no preview for the quote posts in that article. And I need to check if Tusky plans to implement it…
Edit: Tusky does https://codeberg.org/tusky/Tusky/issues/5181
Die müssen nichts kapieren, denen entsteht überhaupt kein Schaden. Die wissen, dass sie beim nächsten Mal dann auch gedeckt werden. Das bisschen Image interessiert da nicht groß.
Das ist so gewollt. Wer da nicht mitmacht, wird rausgemobbt.
That’s just how it is. You can only see favs if the post is on your instance, or if the fav is from your server. A fav from a remote instance to another remote instance is not known to your instance.
It’s the same on mastodon.social but not as noticeable because it’s so big
Es ist eben nicht einer, der 99 schlecht macht. Es sind die 99 die die Fresse halten oder sogar lügen damit der eine davon kommt.
Im Rolladen, also direkt am Fenster?
Keine Sorge, vom Arbeiten ist noch niemand reich geworden.
It’s not that difficult. You can create a second VM from the backup with a few clicks and move the necessary data with scp.
I’m sure they are glad they are protected from the free information war and that you, in true solidarity, are decidedly not helping them to gain free information access. 🫡
Not wrong, just saying that every Vaultwarden client is a backup basically since they cache everything and it doesn’t expire.
Klingt ja viel zu sinnvoll
Wtf are you talking about, nobody is climbing anywhere. By running snowflake, you are offering a piece of infrastructure that other people can use, it’s not specific to the Iran. They can’t install it themselves if the local internet is censored, that’s the whole point of this.
It’s the best we have. What’s your specific problem with it?
Ofc! But since this is the selfhosting community I figured the Docker thing would be more practical. My laptop with the browser isn’t always on.
You need a reserve proxy. That’s a piece of software that takes the requests and puts them toward the correct endpoint.
You need to create port forwards in the router and direct 80 and 443 (or whatever you’re using) toward the host of the reverse proxy and that is listening to on those ports. If it recognized the requests are for nas.your.domain, it will forward the requests to the NAS.
Common reverse proxies are nginx or caddy. You can install it on your raspberry, it doesn’t need it’s own device.
If you don’t want that, you can create different port forwards on your router (e.g. 8080 and 8443 to the Raspi) and configure your service on the Raspi corresponding. But it doesn’t scale well and you’d need to call everything with the port and the reverse proxy is the usual solution.
I can open the website. What exactly are you trying to achieve? Are you in some app?
Yeah I think of it the other way round: I couldn’t get myself to organize them without combining it with a nice selfhosted tool. The goal is getting my stuff organized, the cost is doing work, which includes setting up a system. I can cheat on the cost a little by including a fun project in the cost part.
I do think there’s a hidden cost in selfhosting though and it’s maintenance. Fortunately, there’s selfhosted tools that help with that too :-)
Auch erst kürzlich entdeckt, Game Changer