this post was submitted on 31 Jan 2025
13 points (88.2% liked)

Selfhosted

41572 readers
735 users here now

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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

I've written a bot for [email protected] 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.

top 3 comments
sorted by: hot top controversial new old
[–] [email protected] 6 points 5 hours ago* (last edited 5 hours ago)

I'd recommend to make a Dockerfile for it and run it that way. It'll be quite a lot easier than to manage installing a bunch of dependencies.

Here's a guide I found pretty good!

Here's a bit of a shorter one too to get some more reference.

[–] [email protected] 3 points 6 hours ago

If you can containerise it you could run it in docker.

[–] [email protected] 0 points 4 hours 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.