

Appreciate you bro.
Appreciate you bro.
“but console manufacturers have been known to brick or flag devices if they get connected before official launch.”
Big citation needed on that. There’s zero need for console manufacturers to do that when they can simply hold down the servers on their end until release date anyways, Never once heard of a device bricked simply because you received it early and tried using it.
Pretty sure that is the actual default location for standard EmulationStation, as opposed to ES-DE.
Run the docker compose file. That’s pretty much all you need to do.
You really shouldn’t trust anything important to a pi. I hope that you at the very least have that pi on a UPS if you’re going to risk your data this way.
Thank you so much for posting this and reminding me about this project. I was looking to run his previous similar project that I think was just called Timeline when I saw he was working on this. Can’t wait to dig in.
I wasn’t aware of GlazeWM before, so thanks for giving me something else to check out.
I had originally hoped to use my Mastodon account to follow Lemmy communities but the fact that every single comment on a post pops up in my feed made it… just really unusable. Really happy with using #mbin for Lemmy though and keeping my Mastodon and Mbin separate.
Probably unintended side-effect of this post: A few people like me discovering new communities to follow. Thank you!
There are dedicated Jellyfin clients but I mainly just use the web client that is part of the server 90% of the time.
Proxmox maps user ids between itself and lxc containers and it took me a bit of time to figure it out. I would highly suggest reading the following link as it’s how I worked it out. I ended up chown’ing to 101000 which maps to user 1000 - the default user - in my lxcs.
https://www.itsembedded.com/sysadmin/proxmox_bind_unprivileged_lxc/
Leave Kodi behind in 2010 and switch over to Jellyfin for better results.
This is exactly why for everything fediverse, I only run my own.
An explanation of what SimHub is might be a good idea.
By the way, running synapse - docker or not - is a challenge. It can be very complex especially if you are interested in adding gateways to other services and such. Attempting to use https://github.com/spantaleev/matrix-docker-ansible-deploy might be a better choice as even though it is A LOT, it has a ton of good documentation and you can grow with it as it can help you install various different Matrix servers, gateways and clients as well.
Good luck, hope to hear more about how you get on with it.
It took a little time to get the hang of it, but stick with it and it will get so much easier and it’ll make self-hosting anything you want less of a pain in the future.
As it says in the image, the file is /data/homeserver.yaml. Your other questions are all answered by looking at the way the file is formatted.
Uh… yeah, those are assumptions I made because I went through it entirely myself previously so… yeah.
So you added the secret to the file and restarted the docker container, right?
Something that I think will help you with self-hosting in the future is to always read through the entire process for setting up whatever you want to set up first, beginning to end, so that you are familiar with what you need to do before attempting it the first time. It’s helped me numerous times myself.
It’s a lot more than just “a few dev hours”. You need to invest in training your testers on Linux, potentially purchasing new hardware, invest in programmers that can deal with writing for Linux, etc… Just because something like BattlEye has a checkbox for Linux support doesn’t mean that all it takes is to click the button and rebuild your game.