Comment

Comment on Drop OSS - an open-source, self-hosted alternative to platforms like Steam and Epic.

<- View Parent

warmaster@lemmy.world ⁨3⁩ ⁨days⁩ ago

I haven’t tried it yet, but their docs talk about proton, that makes me think it is a launcher.

source

Sort:hotnew top

scrubbles@poptalk.scrubbles.tech ⁨3⁩ ⁨days⁩ ago
Good, I’ll set it up tonight and see how it goes

source
- warmaster@lemmy.world ⁨3⁩ ⁨days⁩ ago
  Post back your findings 🙏🏻
  
  source
  - scrubbles@poptalk.scrubbles.tech ⁨3⁩ ⁨days⁩ ago
    So far it’s hit and miss, it is early RC code so I expected some bumps.
    
    I run in kubernetes, but any docker environment would work.
    
    your data does need to be in a specific format, but it wasn’t horrible to figure out how. From GOG games you essentially extract the .exe files into <<volumeMount>>/<<gameName>>/<<version>> and then you do a dual import step. First you import the game, then you import the version. The game is just metadata, the version is essentially "Run this exe file"
    
    I had to give it fairly hefty resources, 4 CPUs, this is so it has enough to shard out and extract files and pack them for distribution. I’d like to see this, and more developers in general, rely on using another container for jobs like this. In k8s it’s very easy to say “Start a one-off job and run to the end” and let the container orchestration handle it. It’s harder in docker compose, but I’d like to see a “This container runs the app, this other container runs heavy jobs”.
    
    OIDC from the start is very nice. I hooked it in easily with Authentik.
    
    I’ll update this as I learn more. Haven’t gotten to the stage where I download and install yet.
    
    source
    warmaster@lemmy.world ⁨2⁩ ⁨days⁩ ago
    Very interesting! Thanks for sharing, also I absolutely agree… hogging resources for just in case you import a game is not good. It should be kinda like some forges have separate runners.
    
    source