this post was submitted on 23 Jul 2023
228 points (98.7% liked)
Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ
53843 readers
599 users here now
⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.
Rules • Full Version
1. Posts must be related to the discussion of digital piracy
2. Don't request invites, trade, sell, or self-promote
3. Don't request or link to specific pirated titles, including DMs
4. Don't submit low-quality posts, be entitled, or harass others
Loot, Pillage, & Plunder
💰 Please help cover server costs.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I really liked the concept of this and had high expectation, but I just tried this out following their documentation and not a fan so I'll have to pass / find a better alternative if one exists.
The docker-compose.yml given seems to cause the containers to be lacking permissions to save images and even the DB: logs show images can't be created/saved, restarting the container wipes the DB. No files created at all on the mounted volumes paths. The volume for game files works great though so that's confusing. I can probably troubleshoot that but this is the first container I've ever had such an issue with so I won't bother particularly due to the next points:
On the app itself I was pretty disappointed that it doesn't at the very least extract the files for you, and won't even skip all the manual junk for direct play games that I took the time to name properly with (DP) on the archive files. The reason given is there may be too many manual steps/variations for installation but direct plays don't need any of that.
Given the manual steps required I'll stick to copy/pasting the files off my server to my local games folder, the games themselves being added to steam if I really need to go that far with them.
There's a Discord server (https://discord.gg/NEdNen2dSu) where you can join for any support you need.
Regarding permission issues, it's crucial to note that the Container utilizes User 1000 (for Docker Security Reasons). Therefore, ensure that you change the ownership of your directories to user 1000...
Your dissatisfaction will vanish once this release is available.
I'll just hope it accepts an environment variable for user/group ID because on my server 1000 is not the appropriate user to have permissions to these files. Will find out next time I give it a try.
You can use the user directive in your compose