I’ve written a bot for !dailygames@lemmy.zip that I’m currently just running on my desktop. But I’d like to be able to set and forget it (except for when I do updates) by running it on my Synology NAS.

How can I best pull the node app from GitHub and run it on my Synology, preferably automatically running on start-up if the Synology is restarted.

  • Rikudou_Sage@lemmings.worldEnglish
    0·
    5 days ago

    The easiest would be using docker, you can set up the container to always restart, that way it will be started automatically on NAS restart.

    You can also download node.js from the Synology software center and manually add a cronjob to run after reboot, but the docker way is probably the best way to go.

    • Zagorath@aussie.zoneOPEnglish
      0·
      4 days ago

      How do you run a docker container on Synology? I have a DS923+ which AFAIK should be able to run it, but when I search for Docker in the Package Manager the only thing that comes up is Synology’s own container manager, and I have no idea how to work with that.

      • Rikudou_Sage@lemmings.worldEnglish
        0·
        4 days ago

        IIRC, that’s exactly it. You can either use their GUI (which is not half bad) or you can use the docker command in the terminal after you install the package.

        • Zagorath@aussie.zoneOPEnglish
          0·
          4 days ago

          Is there a way to get a terminal on the Synology itself, or is SSH from my PC the only way?

          • Zelaf@sopuli.xyzEnglish
            1·
            3 days ago

            There is not. But I’d say keep SSH closed on the NAS or whitelist only your local IP in the firewall. I do that and turn it off when I don’t need it. It can be a bit risqué messing about with SSH on Synology because of how funky they’ve made the distro it’s running and any changes you make might not persist on reboot or after updates.

            • Zagorath@aussie.zoneOPEnglish
              1·
              16 hours ago

              Personally I’m not enormously worried about SSH, because I’m behind NAT anyway, but yeah it’s definitely still something I’d rather keep off if not in use.

  • just_another_person@lemmy.worldEnglish
    0·
    5 days ago

    Only some models of Synology units have the ability to run containers, so check that first.

    Otherwise, you COULD try and install the deps from the Synocommunity packages, but they get messy pretty quickly due to architecture limitations per package (one package may only work on select models). You can browse those and their architecture targets on the synocommunity site to make sure what you need will be available. If you can’t go the container route, I’d definitely read up on packaging your own app using the synocommunity guides, even if keeping it private.

    • Zagorath@aussie.zoneOPEnglish
      0·
      4 days ago

      Yeah I’m pretty sure my Synology should be able to run containers. It’s a DS923+. But unfortunately when I search for Docker in the Package Manager the only thing that comes up is Synology’s own container manager, and I have no idea how to work with that.

    • Zagorath@aussie.zoneOPEnglish
      0·
      4 days ago

      I would love to containerise it. I worked with Docker in a previous job, but honestly I’ve forgotten most of how to work with it. Would be a nice refresher to try and relearn how to create Dockerfiles and docker-compose.yamls.

      Unfortunately I currently have two problems. First: I seem to be completely unable to test this on my desktop. When I open Docker on my PC, it complains that I need to run wsl --shutdown, but despite doing that many times, it still complains, before immediately closing.

      So I was going to try doing it entirely on the Synology. And then I ran into the issue that…I have no idea how to even start with that. When I search for Docker in the Package Manager the only thing that comes up is Synology’s own container manager, and I have no idea how to work with that.