No problem. I will say one thing for future reference regarding Docker though, if you want to have persistent data or move data or keep data around so that it can be mounted to another container, volumes are what accomplishes this. If using a docker command for starting a container, make sure you either create a volume first or the command includes the option to create a volume and mount it. If using compose, you want a volume block within the compose file to store your persistent data. This will make your life much easier.
if you have exactly the 6 system they mention (the script hates distros) than it may or may not work as for selfhosting, which i did with invidious before feels even more unstable and shaky than a public instance, how do i know my little piece of shit ip isnt gonna be banned for one reason or another, or that invidious keeps working since it hasnt received a proper new release since 2019
Invidious is constantly updated and new releases posted. If you're looking at github for your release info, they've moved to quay long ago. I'm currently on 2023.11.04-438467f6 @ master. Tell me what you were hosting it on before and what you think you would be hosting it on now and maybe I can help if you feel you had problems in the past. It has come a long way since 2019. Also, do you have a link to your IP's TOS? I can look over it really quick and see if they would have a problem with it.
I know you mentioned invidious going dark, but self hosting it is a piece of cake honestly so you don't have to worry about the flakiness of other people's servers. And the script is so easy to use. I ran this for a long time on a Rock64 with 1GB of RAM with no issues until I switched to Proxmox.
I never have. I guess I don't understand the point of deleting your account? I have no issues with telling people my name and location. I live in Dallas, Tx and my name is Danny. I'll even meet up with you and buy you a beer.
I learned quickly that installing apps the traditional way causes pretty major instability. You're basically rebasing the entire OS via ostree to install one application. After my second nuke and pave due to updates no longer working from me rebasing I took the time to learn toolbox so if a flatpak is not available I can still use an application (containerized) without altering the OS. Toolbox by default pulls in another Fedora install as the app base. I recommend using Alpine instead, much smaller and lighter.
I guess the moral of the story is learn to install applications the correct way, or just don't use an immutable OS
It's a lesser known company and somewhat pricey, but my friend who I trust has given his a very glowing review. He has the 14" and is actually planning to give it to his gf and buy the 16" once they become available.
More than like likely yes, although you shouldn't have to and this is not expected behavior. Same thing happened to me with Kinoite. Twice. I still got flatpak upgrades through Discover but no longer system upgrades, or the system upgrades would appear but error out. I just decided to not rebase anymore after the third reinstall and use toolbox for everything that didn't have a flatpak available.
No problem. I will say one thing for future reference regarding Docker though, if you want to have persistent data or move data or keep data around so that it can be mounted to another container, volumes are what accomplishes this. If using a docker command for starting a container, make sure you either create a volume first or the command includes the option to create a volume and mount it. If using compose, you want a volume block within the compose file to store your persistent data. This will make your life much easier.