Help w/ Docker (Joplin Server)

Howdy, folks. Long time TS451 owner here, migrating to the new forum.

I’m trying to set up a Joplin server to replace Evernote. Unfortunately I’m an amateur (at best!) user and don’t fully have a basic understanding of Docker and all the parameters to configure it. IOW, is the ‘compose’ file really necessary, or is that what the QNAP GUI does for us in the process of creating a container?

Just as an exercise, I was able to install Emby for Docker (alongside my QNAP Emby app) and it worked out great, but I’m struggling to get Docker to get Joplin set up so I can get to the configuration screen.

My other option would be to use QNAP OwnCloud and rely on that as a repository for synchronized notes files. That might be easier.

Hoping to rely on your experience and guidance to get me sorted out.

Thanks in advance!

So a couple comments:

1.) Yes, you really need Compose to get things the way you want them. Not always - but most of the time. As an example, if you don’t map the storage locations for the container to an accessible location, QNAP will put the app data storage inside of its encrypted storage of the container in a location that you can’t easily access. Compose is not hugely difficult and most “good” container apps from the Docker Hub will have a website with examples of Compose that will help you get started. I just installed and got Vikunja up and running yesterday based on the examples provided. There’s plenty people here to help you figure it out.

2.) Of bigger concern is the power of your TS-451. It’s a very underpowered NAS (I have one) and if you start running a number of Docker apps, you might very well slow the NAS down to a crawl.

Gemini zei

To install Joplin Server on your QNAP TS-253D using Container Station V3, we will use a Docker Compose configuration (YAML). Since your setup does not support the version tag, we have excluded it.

Step 1: Create Directories

Use FileZilla to connect to your NAS and create the following directories for database storage. This ensures your data remains intact if the container is updated or restarted.

  1. Navigate to the folder /share/Container.

  2. Create a new folder named joplin.

  3. Inside that folder, create another one called database.


Step 2: Configure Joplin Server in Container Station

  1. Open Container Station on your NAS.

  2. Go to Applications and click Create.

  3. Give the application a name, such as joplin-server.

  4. Paste the following YAML code into the editor. You can use gedit on your laptop to review or modify the code beforehand if you prefer.

YAML

services:
  db:
    image: postgres:16
    volumes:
      - /share/Container/joplin/database:/var/lib/postgresql/data
    restart: unless-stopped
    environment:
      - POSTGRES_PASSWORD=YourStrongPassword123
      - POSTGRES_USER=joplin
      - POSTGRES_DB=joplin

  app:
    image: joplin/server:latest
    depends_on:
      - db
    ports:
      - "22300:22300"
    restart: unless-stopped
    environment:
      - APP_PORT=22300
      - APP_BASE_URL=http://192.168.0.160:22300
      - DB_CLIENT=pg
      - POSTGRES_PASSWORD=YourStrongPassword123
      - POSTGRES_DATABASE=joplin
      - POSTGRES_USER=joplin
      - POSTGRES_PORT=5432
      - POSTGRES_HOST=db

Important: Change YourStrongPassword123 in both sections to a password of your choice.


Step 3: Installation and First Login

  1. Click Validate and then Create. Container Station will download the images and start the server.

  2. Once the containers are running, open your Brave browser and go to: http://192.168.0.160:22300.

  3. Log in using the default credentials:

    • Username: admin@localhost

    • Password: admin

  4. Critical: Change the admin password immediately in the Joplin web interface settings after logging in.


Please note: This is an AI (Gemini) generated answer on how to setup a Joplin server.

If it does not work, please remove the application.

Points taken, which is why I try to keep my installs to a minimum, though I did upgrade the RAM to 8G so it helps. But a 10 year-old machine is getting a bit long in the tooth. What I probably should do is uninstall the stuff I don’t use. If only QNAP would stop force-installing apps that we don’t need (like an SSD profiler) that would help.

I’ll have a look at that compose file and try to figure it out. In the meantime, Joplin can operate with Owncloud as a repository for files. All I really need is a WebDav folder where the data for the opin clients can sync. Is there something lighter-weight than either option?

Thanks!

If we are talking about something that is publicly exposed, you need to take security into account.

Make tripple sure no part of your QTS system itself is exposed.

My thinking is that I’d sync locally when at home with desktop and mobile. My activity with notes is more or less reference and does not require frequent updating. I do have a NextCloud instance running on my shared hosting account at Siteground, but that’s pretty secure, all things considered. But if the QOwncloud will provide the necessary back-end to allow my devices to sync, I’m all for it.

I use Nextcloud Office and Draw.io on my nextcloud (snap auto updating app on a virtualization station ubuntu machine) works pretty good so far.