A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
This looks awesome and something I’ve been hoping to do for a few years. Can’t wait to try this on my home server.
Thanks! Let me know how it goes!
Does it support multiple screen/displays?
It does! It'll automatically create new virtual displays on demand when a new client connects and it'll match the client resolution and framerate.
I tried to do sth similar with limited success using Steam remote play. This is great but I have 2 questions:
Great questions!
Did you look into memory deduplication?
For the Steam library I suppose? There's been some discussions around it both in Discord and Github #83 #69 It's something that I should definitely research further but I'd really like to address it even if it's just something that might be done outside of our container.. Would you like to help us?
Is client software sunshine or custom software?
Wolf is an implementation of a full Moonlight backend from scratch; there's has been many reasons for this but mostly it's because Sunshine has a lot of global and intertwined state and it would be very hard to add support for multiple independent users. I try to contribute upstream where possible; for example I've helped merging our custom library for virtual inputs so that users of Sunshine could also benefit from the new virtual joypad implementation and support for Gyro, Acceleration and so on..
For the Steam library I suppose?
I meant RAM deduplication. https://duckduckgo.com/?q=linux+same+page+merging&t=fpas&ia=web
For on disk deduplication, Steam supports user-specified locations for installing games and dependencies like Steam Linux Runtime. 2 users can theoretically use the same Steam library at the same time. To evade issues, auto updates should be disabled in the Steam clients. Steam doesn't support completely disabling updates afaik, the best is setting update period to 3.00-4.00 AM. DXVK cache files must be located outside the Steam library folder. Otherwise if 2 people play the same game with Proton at the same time, cache files may be corrupted. (the default is the folder with game exe) Info on changing cache file location: link
Does this automatically use nvidia-patch in the container drivers to unlock as many NVENC streams as possible? I believe, from their documentation, that it's possible to use the patch with docker, with an unpatched host.
Otherwise, is this something that could be implemented? I'm happy to submit a feature request if needed :)
The patches aren't included by default because I'm not sure about the legality of them and I really don't want to get into troubles over this. I should research a bit more into this though.
How so you force steam to run multiple instance of the same game ?
Or just multiple different games at once?
As others have pointed out below it's going to run multiple separated instances of Steam with the limitations that Valve impose (there's not much we can do there). This project is not limited to Steam though, you could easily run another session from a different device with something like Lutris or Pegasus.
As far as I can tell, it's creating container VMs that have Steam installed inside separately.
It looks they are just containers. No hardware or kernel emulation needed.
That doesn't necessarily seem to be the case:
I'm not sure what you are referring to but in the chart Mesa and Kernel layers are shared between the running applications and Wolf in a single host, no VMs involved. One of the main reasons behind the project was to allow exactly this so that you wouldn't incur in the big penalty hit that incurs in GPU splitting
Ah okay, thank you heaps for clarifying :) That's awesome that you've been able to limit the overhead like that, I'm excited to test it out!
No worries! Let me know how it goes, any feedback is highly appreciated!
still steam prevents you from running more than one game at once from one account. can't start vampire survivors on the deck and play manor lords on the other pc using the same account. family sharing and using multiple accounts should work, though 🤔
I believe this is akin to an open-source version of Stadia or Geforce now. Essentially, you have a powerful server that can be used by multiple users to play their own games. So, along with a couple of friends, you could purchase a powerful server, and then connect to it with a weak home computer.
Well said! That's exactly the idea!
Yeah, I think that's the general idea. They are seperate instances of Steam that could be signed into different accounts. So yeah, if you're doing multiplayer of one game, each account would need to own it. That would be the exact same limitation at a LAN party anyway. This just lets you host said LAN party on a single beefy box, and use thin clients for each gamer, like an RPi4, a tablet or even an Apple/Android TV.
Does the server have to run headless, or can one person still run games locally on it while another has a remote session? That is, would I be able to play on the monitor/mouse/keyboard directly attached, while my partner has a session on a laptop?
Yep that's perfectly possible, the sessions that will run under Wolf will be completely isolated from the host. Besides, that's how I run it on my desktop dev machine!
This is something i have to test with Fedora bazzite on my Ubuntu distrobox.
Why MIT license and not GPL variant?
I’m really curious about the motivation behind such permissive licensing too.
The project is yours, you can always distribute a commercially licensed version of it regardless. GPL or any other license will never be a hindrance.
The only thing a permissive license does is allowing everyone else to issue commercial versions of it without even sharing source code.
Just what I was looking for! Good work, can't wait to try this out.
This sounds awesome but not sure it would apply to my use case. Maybe you could elaborate.
What I want is to have 1 pc be a host for all the tvs in my house (4, master bedroom, guest room, office, and living room) each room has a video output and a usb cable with a hub that has keyboard and mouse and maybe a controller for games.
So far what I have is all the displays are mirrored and the keyboard and mice and joysticks work in each room but all the displays show the same thing.
It would be rad if each one was a vm and had its own front ends so you could watch plex in one room while someone plays Dave the diver in another.
Sounds like this is exactly what this is capable of: you run Wolf on one beefy machine, and then you connect to it from multiple clients to play games or run a full desktop remotely!
Please submit a pre-built docker image to the unraid app store!
Looks awesome! Any idea if this will run on WSL?
Excellent work! I am glad to see this project coming along nicely.
I tested it a while back and was looking forward to updates. I have a few questions:
Is each "game entry" in moonlight a shared instance? If a player loaded it up, would they share save files with others that have already played? Also what would happen if two players loaded the app at the same time?
How would I go about making a generic linux desktop from a given Linux distro?
Is each "game entry" in moonlight a shared instance?
Quite the opposite, at the moment each Moonlight client will have a completely isolated session and they can play different games. This obviously defeats co-op which is something that I'd like to work on by adding proper user management and a remote UI in the next release.
How would I go about making a generic linux desktop from a given Linux distro?
In our latest images we have default support for Sway, you could easily expand that base Dockeer image with all the apps you need or make a different image with the DE that you'd like to use. The project is very open ended and only a few base components are needed in order for any image to be streamed to a remote client.
It's probably a skill issue but don't really know how to setup desktop streaming. I've tried
[[apps]]
title = "Desktop"
[apps.video]
source = "pipewiresrc capture-screen-cursor=true capture-screen=true"
But it just shows black screen.
Might be worth to open up an issue on Github or a thread on Discord. I haven't tested pipewiresrc but there's probably some clue in the Wolf logs. Besides, have you mounted the host XDG_RUNTIME_DIR, passed the right env variables and so on?
For streaming the host desktop Sunshine might be a better fit btw..
I've passed my display through to a VM in Proxmox for transcoding and now I can't get the GUI for that VM.
Is this something that would allow me to connect to that VM on another PC and use a virtual desktop?
If so, I may have to have a play with it. I mean I'm happy away using SSH but why not have UI if I can?
Yep, this is one of the main reasons why I started this project in the first place: I wanted to stream games from the same VM where Jellyfin is running.