Feature Request: Add PostgreSQL, Redis or KeyDB, about kamal HOT 4 CLOSED

If you're working on a side project, which is just going to be deployed to a single server, you should just use sqlite. I'll add something to make the mount for that easy. But I don't want to get into running stateful services as part of MRSK. Way too many complications. And again, lots of developers might either get away with just sqlite (if they only run on 1 server) or use a managed DB.

from kamal.

@dhh fair point on sqlite, sometimes I wish I would have started with it instead of PostgreSQL but wasn't really to popular for actual deployment when I started years ago.

I watched the YouTube video with the walkthrough and you did deploy 2 app servers and 1 DB which is great - not sure if it should be part of MRSK or maybe just documentation but backing up that PG or MySQL would be kinda important

from kamal.

@dhh

If you're working on a side project, which is just going to be deployed to a single server, you should just use sqlite. I'll add something to make the mount for that easy.

Sorry to reopen an issue, but I'm trying to set up MRSK with a volume for a SQLite DB but I'm struggling.
In Docker, it would be a simple named volume, but in MRSK, Docs are not so clear between Using volumes chapter and Using accessories chapter.

Should I just go with:

accessories:
  sqlite:
    volumes:
      - /var/lib/sqlite

But It doesn't work...
Any clue for static volume where no Docker image is involved and that must be long-lived. Thanks.

from kamal.

For people who are struggling like I was.
After some research, try and fail, the answser was not that hard.
Below my mrsk.yaml to use SQLite with MRSK

...
service: a_service
image: user/oci_image
servers:
  - 111.111.11.111
volumes:
  - 'database:/app/database'
...

In plain english: "mount a database (= database:) and make it available to my app at app/database.
(my db.sqlite3 is stored inside app/database)

from kamal.