[BUG]: Read-only docker mount

[hurleyy]

Describe the bug

I have a read-only docker volume mount that contains a git repo. This repo is an old export from Joplin when I migrated. I refer back to it sometimes from within Jotty. I also sometimes update it via git, and when I do, a webhook tells Komodo to pull the repo (while overwriting any changes), and restarts the Jotty container so it sees the new files. This has worked.... okay, until 1.26.0.

Here's a snip from my compose.yaml

volumes:
  - /etc/komodo/repos/notes/joplin:/app/data/notes/$username/git/joplin:ro

Well, with the newest update, this workflow is broken because of the new migration.

I treat this mount as an archive that I don't want to be externally modified, or shared. I don't intend to request massive changes on your end. I'm just more curious about any architectural changes you might be able to suggest for me to get my container back online. Thank you.

Steps to Reproduce

Add a read-only directory with .md files to a docker mount within /app/data/notes/$username/ and then update to 1.26.0.

How do you run Jotty?

Docker

Jotty Version

1.26.0

Checklist

• I have searched across other issues to make sure this bug has not been already reported.

[hurleyy]

Error writing .category-info.json in /app/data/notes/$username/git/$file: Error: EROFS: read-only file system, open '/app/data/notes/$username/git/$file/.category-info.json.b2e0fed5-ee35-4129-9c62-12f19fcf00da.tmp'

[fccview]

Error writing .category-info.json in /app/data/notes/$username/git/$file: Error: EROFS: read-only file system, open '/app/data/notes/$username/git/$file/.category-info.json.b2e0fed5-ee35-4129-9c62-12f19fcf00da.tmp'

Oh that's interesting, of course it'd error, Jotty now uses a category file to handle more complex operations.

I'll need to have a think about this one. I'll treat it as priority sorry I don't have an answer right away, but it's definitely a real regression, didn't think anyone was using jotty this way sorry