Congrats!

Compiling your own kernel is very intimidating at the beginning and one learns a lot after plunging down that rabbit hole

After some time it gets pretty straightforward. Just don’t forget to enable the modules for your drive and filesystem (it has been a while, maybe that’s not needed anymore) and the rest you can always fix with another compilation

That part where you got stuck even after switching hardware: yikes. I wouldn’t expect that

Out of curiosity (I’m not going to try to change your mind, I just want to check a hypothesis): you’ve heard about the button in the past and this is your opinion of it ; or this post is one of the first times and the only context?

track different things, tasks, and who’s doing what and when. Think of inventory, shifts, etc

I agree that Nextcloud with Collabora might be your way to go here, but this line made me think: maybe kanban board would be more what you need? I use Nextcloud’s Deck for that, but even the devs say it’s not production ready and it is true. It gets slow with more cards

Other software like this. From my notes, not vetted, not checked, just gathered in case I want to migrate out of Deck. Should be mostly open-sourcish

• https://vikunja.io/
• https://github.com/plankanban/planka
• https://www.openproject.org/?acuuid=e13029ec-0feb-413b-acce-25d49be4d880
• https://taiga.io/
• https://kanboard.org/
• https://github.com/wekan/wekan
• https://www.techrepublic.com/article/open-source-kanban-boards/

Of course, NC provides a lot more, you could even have your own Meet (Nextcloud Talk), so maybe it’s a good idea to have it anyway

Also, there is OpenCloud. IIRC correctly there is some history between NC and OC but I don’t remember the details

EDIT: since you initially started with searching for a service, there are offers where you maintain the NC but the most technical part is done by a company. I remember Elest and Hetzner but probably there are more

I guess you might want to ask this question in one of the self-hosting communities (there’s a bunch that are active, so I’m not linking one)

But getting back to the topic:

• jellyfin needs very little
  I’m running mine on a laptop with 4 threads at 2.6GHz and on 8GB of RAM it was fine with a bunch of other stuff running
• OwnCast
  IDK but for personal use I’d expect to also have low requirements
• Minecraft server
  That part I’m not sure about. I’d expect it to be a bit more demanding
• play some steam games
  I understand you’ll be running those on another computer and only streaming via OwnCast, so that goes back to earlier point

I guess an SD card might be better. RasPis work from those for years just fine. Just don’t kill the power, power down nicely. SD cards are fragile on that

I also thought about running from RAM but I guess the transcription might be needing the RAM too. So that route probably depends on how much RAM there is available

Mount points in fstab

I don’t intend to overly nit-pick, but since OP said themselves they are new to this: Wine doesn’t translate the exe. It translates system calls from Windows ones to Linux ones. So to have an example: opening a file would be some system call in both systems. But, of course, different because the OSes are different. An exe would be calling Windows one. What WINE/Proton do is get that call and translate it into Linux system call, so that .exe can still open a file, as if it was running in Windows

As for OPs question: AFAIK when using dx11 you will still in the end be using Vulkan, just through DXVK (as this comment said, translates dx calls into Vulkan calls). Theoretically setting to use Vulkan in the game itself might have less overhead (no DXVK in the middle) but it’s a mixed bag in my experience. I think that Windows Vulkan support is just not yet there, so the in-game code for Vulkan is so-so.
I second this: you have to check on which setting each game works better

Might be! It’s just that having a container like that feels easier than looking after bare-metal secondary db

Maybe I’ll just pg_dump during Nextcloud maintenance window and get into BorgBackup putting the dumps on NAS? If I have to revive the db from the dead, I’ll probably just use the dump anyway, so that’s one hoop less

2nd DB would be on the NAS but its not being used by the app, so as long as it’s asynchronous writes, you should be okay

But then I have to maintain it too. And it will be using RAM that was supposed to only be for servicing RAID. On a platform where RAM can’t grow

For sure my setup will be growing and changing with time. But ATM this “prod” db lives only on laptop’s SSD

replication in the database it self

AFAIK db replication would require running another db on NAS. Which I tried to avoid

I have another cronjob that takes a backup into the first database docker init folder. Older backups end with -date so they won’t get picked up by the init script. You can do similar with just docker.

Yeah, that’s why I’m thinking to do. Have a container that watches changes to db data and rsyncs those into the NAS for safekeeping. My main goal in all of this is so db data won’t die with laptop’s SSD

For steam you need to run a second opentrack inside the container. There’s a writeup somewhere in opentrack issues for that

Edit: https://github.com/opentrack/opentrack/issues/1260#issuecomment-881908297

Oh, that’s interesting! Sounds a bit crazy but I’m interested in what you find out :D

I wonder if in this case VMs don’t make it work better. There is another layer between the process and NFS than pure docker+volume

db running on the Pi with storage on the Pi could be faster than the db running on the laptop with storage on the Pi

I think so too, but I’m mindful of the 1GB RAM per TB rule. I’m afraid to choke the NAS and on Pi I can’t put in more RAM

keep the DB on the most powerful CPU and quickest disk

Thing is, I expect that NAS to be faster than the SSD on the laptop that runs a bunch of stuff. Even NC log file will take up some IO

But I get the point you are all making here, I’m changing course :)

it’s generally not a good plan to put anything that needs realtime access remote to the device processing it

So in your opinion putting whole nextcloud_data as NFS mount is also a bad idea? Keep NFS as external storage and/or only user data?

AIO docker

It was too blackbox to me. I had some issue and found it hard to debug. fpm+nginx is more my speed
This BorgBackup app is available only in AIO?

You can easily just try it out though

Yeah, but if that setup leads to problem in a few months, I won’t catch that. That’s why I decided to ask and judging by the other answer, I dodged a bullet here

Now I’m thinking of setting up something like this. Maybe even in another container? One volume with data bound, one with NFS and a bunch of scripts in entrypoint to rsync(?) between the two on inotifywait. There is lsyncd but it’s been unmaintained for two years now

I’ve read about “high wake” to avoid their gravity influence but I’m not sure what that means exactly.

When you drop out of SC, plot a route to another star system. Then FSD won’t be slowed down by the mass of ships nearby

But in my experience the best is to just get good in escaping interdiction. I mean winning that mini-game with blueish tunnel. It’s definitely doable in a T9. Also, that ship has better yaw than roll, so switch to pitch&yaw scheme. You don’t need to be roll-aligned to anything to win interdiction game

about half the applicants that apply and I send a zoom calendar link to apply do not schedule an interview and about half that do, do not show up after scheduling a meeting time

That, I completely don’t understand. Why do the do that?