• 0 Posts
  • 207 Comments
Joined 2 years ago
cake
Cake day: July 18th, 2023

help-circle









  • I can only answer two of your questions:

    • How to know if a steam game is “deck verified”? There is a “Steamdeck compatability” box for every game on steam that will give on one of four statuses telling you supported/partially supported/not supported/unknown
      • That being said, steam is a bit conservative about “supported” games. ProtonDB is a more complete list of compatible games and gives guidance on how to play games steam considers “unsupported”.
    • Can you use steam input for non-steam games? Games must be added/launched through steam for the steam input settings to work, so in most cases you should be able to set it up by adding the “non-steam” game to steam.



  • jacksilver@lemmy.worldtoSelfhosted@lemmy.worldgoodbye plex
    link
    fedilink
    English
    arrow-up
    2
    ·
    3 months ago

    Looks like there is a config and cache location in their docker scripts. The easiest way to make a docker application portable is to bind mount the config and cache. That way you have access to the actual files and could copy them to your windows partition.

    If you’re already using a volume for that data, I think it becomes a bit trickier. I know technically you can move or copy volumes, but I’ve never tried. Although you could still bind mount a random directory and still copy the files out.




  • jacksilver@lemmy.worldtoSelfhosted@lemmy.worldDocker Backup Stratagy
    link
    fedilink
    English
    arrow-up
    3
    ·
    edit-2
    3 months ago

    Yep, bind mount the data and config directories and back those up. You can test a backup by spinning up a new container with the data/config directories.

    This is both easy and generally the recommended thing I’ve seen for many services.

    The only thing that could cause issues is breaking changes caused by the docker images themselves, but that’s an issue regardless of backup strategy.




  • Some of the commands I use a lot for debugging containers, in case you go down that route:

    • docker run --rm -it --entrypoint bash <image_name>
    • This command let’s you enter a docker image with bash so you can test commands and treat it like a temporary VM. Great way to see how the image is setup
    • docker exec -it <container_name>
    • This let’s you enter a running container with bash. A great way to inspect why something might not be working or check mounted volumes, etc.

  • Once you know how to use docker/containerization it’ll be the only way you want to deploy applications. Most popular applications will also have good guides on how to setup/config the container, but sometimes you’ll need to read up on docker and Linux to figure things out.