[FEATURE]: Support running under subdirectory (change base url)

[majkelwaltuh]

Describe the feature you'd like to see

Currently, the environment variable APP_URL does not allow for subdirectories (eg. https://somedomain.com/jotty). Trying to access Jotty through a subdirectory does not work as it redirects back to the page root / (eg. https://somedomain.com/jotty/auth/setup becomes https://somedomain.com/auth/setup). It seems like everything past the tld in the environment variable APP_URL is stripped out.

Wireframes or mockups (optional)

Add an environment variable named BASE_URL or change the way that APP_URL functions in order to allow specifying subdirectories

Checklist

• I have searched across other issues to make sure this has not been already suggested.
• I understand this request may be declined if it is not in line with the project's goals.

[fccview]

Hey
that's a very fair request, I'll look into it ❤️

[fccview]

Hey,
This is both an easy fix and a bit of user action needed.

I've pushed the change to the develop image (which is gonna be next release) and I'd like you to try it for me, if that's ok?

Only issue is, there's no way for me to add a BASE_URL, the way nextjs adds a base url is via the next.config file, which is read on build time. By the time you get the docker image, the application is already built, so that variable would do nothing for you.

You will need to:

• add a reverse proxy: /jotty/* → strips prefix → forwards to app at /*
• APP_URL=https://somedomain.com/jotty
• Jotty should now correctly send you to https://somedomain.com/jotty/auth/login, the proxy strips /jotty/ and the app serves the content correctly.

If someone you try to serve the app directly to a subdirectory without a stripping proxy, it won't work it unfortunately is a fundamental Next.js constraint, I thought about potentially add a wrapper to the server.js file that gets ran in standalone mode in docker but it's a LOT of overhead for something that can easily be achievable on the user side with a proxy change.

Let me know how you get on, happy to assist you if you need ❤️

p.s. wait until it's all green here before pulling the develop image - https://github.com/fccview/jotty/actions/runs/22273449366
also given you will get to test the newest feature before they are released maybe lemme know if you find any bugs haha

[majkelwaltuh]

Thank you for the quick response.

I use Traefik as my reverse proxy, so my docker-compose.yml file looks like this

services:
  jotty:
    image: ghcr.io/fccview/jotty:develop
    container_name: jotty
    user: "1000:1000"
    volumes:
      - ./data:/app/data
      - ./config:/app/config
      - ./cache:/app/.next/cache
    restart: unless-stopped
    environment:
      - NODE_ENV=production
      - HTTPS=true
      - APP_URL=https://somedomain.com/jotty
    networks:
      - frontend
    labels:
      - traefik.enable=true
      - traefik.http.routers.jotty.rule=Host(`somedomain.com`) && PathPrefix(`/jotty`)
      - traefik.http.routers.jotty.entrypoints=websecure
      - traefik.http.routers.jotty.tls=true
      - traefik.http.services.jotty.loadbalancer.server.port=3000
      - traefik.http.middlewares.jotty-stripprefix.stripprefix.prefixes=/jotty
      - traefik.http.routers.jotty.middlewares=jotty-stripprefix

networks:
  frontend:
    external: true

I tried changing NODE_ENV to development, HTTPS to false, PathPrefix to /jotty, /jotty/, /jotty/*, and /jotty* and the same with stripprefix.prefixes

However, when I try to access https://somedomain.com/jotty it redirects to https://somedomain.com/auth/login and this error appears in docker logs jotty

TypeError: controller[kState].transformAlgorithm is not a function
at ignore-listed frames

I also saw this warning in docker logs traefik after restarting the jotty container, which doesn't appear if running jotty:latest

WRN github.com/traefik/traefik/v3/pkg/provider/docker/shared.go:42 > Failed to inspect container 7b4b3018501f9bb82c97156b50402194f6e3e68256a90f3be61005a5cef4516b error="Error response from daemon: No such container: 7b4b3018501f9bb82c97156b50402194f6e3e68256a90f3be61005a5cef4516b" providerName=docker

I tried removing the stripprefix middleware but that resulted in a Firefox error about not redirecting properly.

Manually going to https://somedomain.com/jotty/auth/setup loads the html but all css and js files are requested from https://somedomain.com/_next, not https://somedomain.com/jotty/_next

I have all of my docker containers set up identically and none of them have this issue. I don't know what to do, honestly.

EDIT:

I've found a stupid but (mostly) functional workaround:
The proxy isn't an issue, it's static paths.

- traefik.http.routers.jotty-assets.rule=Host(`somedomain.com`) && (PathPrefix(`/_next`) || PathPrefix(`/api`) || PathPrefix(`/app-icons`) || PathPrefix(`/_ws`) || PathPrefix(`/settings`) || PathPrefix(`/checklist`) || PathPrefix(`/note`))
- traefik.http.routers.jotty-assets.entrypoints=websecure
- traefik.http.routers.jotty-assets.tls=true
- traefik.http.routers.jotty-assets.service=jotty

Adding these labels to docker-compose.yml lets me access the page, navigate the settings and make notes, but doesn't allow me to use the notes and checklists buttons on the sidebar as they use queries (eg. ?mode=notes, ?mode=checklists) which don't work without manually changing the url.

[fccview]

Oh that's so interesting @majkelwaltuh
I'll keep looking into this one (sorry for the delay, I'm a little slower at the moment, i've explained the reasons in #414 )