Joplin Server pre-release is now available

Development
143

I used the default user/pw and tried to run it locally in my LAN first so I din't set up a reverse proxy. Do I need it?

  cat .joplinenv 
# =============================================================================
# PRODUCTION CONFIG EXAMPLE
# -----------------------------------------------------------------------------
# By default it will use SQLite, but that's mostly to test and evaluate the
# server. So you'll want to specify db connection settings to use Postgres.
# =============================================================================
#
 APP_BASE_URL=http://192.168.0.20:22300/joplin
 APP_PORT=22300
# 
 DB_CLIENT=pg
 POSTGRES_PASSWORD=joplin
 POSTGRES_DATABASE=joplin
 POSTGRES_USER=joplin
 POSTGRES_PORT=5432
 POSTGRES_HOST=localhost

cat joplindocker.yml 
# This is a sample docker-compose file that can be used to run Joplin Server
# along with a PostgreSQL server.
#
# All environment variables are optional. If you don't set them, you will get a
# warning from docker-compose, however the app should use working defaults.

version: '3'

services:
    db:
        image: postgres:13.1
        ports:
            - "5432:5432"
        restart: unless-stopped
        environment:
            - APP_PORT=22300
            - POSTGRES_PASSWORD=${POSTGRES_PASSWORD}
            - POSTGRES_USER=${POSTGRES_USER}
            - POSTGRES_DB=${POSTGRES_DATABASE}
    app:
        image: joplin/server:latest
        depends_on:
            - db
        ports:
            - "22300:22300"
        restart: unless-stopped
        environment:
            - APP_BASE_URL=${APP_BASE_URL}
            - DB_CLIENT=pg
            - POSTGRES_PASSWORD=${POSTGRES_PASSWORD}
            - POSTGRES_DATABASE=${POSTGRES_DATABASE}
            - POSTGRES_USER=${POSTGRES_USER}
            - POSTGRES_PORT=${POSTGRES_PORT}
            - POSTGRES_HOST=db

export env vars:
export $(grep -v '^#' .joplinenv | xargs)
run:
docker-compose -f joplindocker.yml up

144

Two things: Yes, you need a reverse proxy configured, because you want to access everything via http(s), even in your local LAN. Secondly (based on the previous point), the APP_Base_URL has to be without the port, maybe take a look at this thread.

145

For information, there's a bug with the way passwords are saved. It's been fixed on dev but not yet released.

1 Like
146

thanks! Is there a good tutorial/manual how to set up the proxy with th joplin server and the docker image?

147

This thread seems to be a quite comprehensive tutorial for Joplin Server w/ Docker & Apache : Guide for Joplin-Server on Raspberry Pi
Bruno

2 Likes
149

ok I got it working! Thanks! Question: Where are my joplin notes/files stored exactly now on the server?? In which location? Can I specify the folder location? e.g. store them on a mounted cifs

150

In my understanding files (notes & resources) are in the Postgresql database

1 Like
151

what do you enter in the client config for Joplin Server Dir? Default is Apps/Joplin...
What is that good for?

152

You can put anything you want, or even nothing, in which case the files will be at the root. Being able to choose the dir allows having multiple accounts in there. For example, you could have two Joplin instances with your personal notes under /Apps/Joplin and your work notes under /Apps/JoplinWork

1 Like
153

I was wondering if there's some sort of local import possible. Basically you take your jex file and import it on the server with specifying the server dir.

Or does one have to sync all their notes to the server over the network?

154

If you really want, you could install the CLI version of Joplin on the server, import your JEX files into it, then sync with the service running on localhost.

1 Like
155

What?s the status of the Joplin server docker image. Still beta or when do you think to release a stable productive version?

156

No ETA but it's high priority. I want to get the sharing feature done, then release it again as beta for several weeks more, just to fix any remaining bug, and then create the stable release.

4 Likes
157

cool

158

It worked, thank you!

@laurent Good news, I'll be waiting for the next release.

159

I'm trying out the server using the latest joplin/server docker image. Seems to work fine so far! But is it normal that the 'home' page returns 403 "Directory listing not allowed: Back to the login page"? With 'home' I mean browsing to the APP_BASE_URL, such as https://example.com.
Screenshot 2021-04-01 at 00.49.08

I migrated from Evernote to Joplin with WebDAV on my Synology NAS. Pretty great experience :slight_smile: Just noticed some slowness (especially on my iPhone). But I think the Joplin Server will perform much better :grinning_face_with_smiling_eyes:

160

Did u click on back to the login page?

161

By sharing feature you mean collaboration on a note or just link share out?

162

If I click on "Back to the login page" I can login. Was just curious if it's normal that the APP_BASE_URL shows this 403 error or that it should show something else instead (or redirect to the login page automatically for example).

163

Sharing a note via a public URL, which is already working. And sharing a notebook with another user to allow collaboration, which is in progress.

1 Like