this post was submitted on 03 Jul 2023
21 points (100.0% liked)

Selfhosted

40134 readers
545 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

I've been setting up my own instance and I ran into issues with pictrs. I have it running with an S3 backend, so no filesystem involved there, but I just learned it uses sled as an internal key-value store.

I suppose we need to persist that sled data somehow?

How do you all handle this? Any isights appreciated.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 7 points 1 year ago (1 children)

Due to that sled database file, pictrs is not stateless so you must persist it into a filesystem. How you'll do that is up to you though. If you're using docker, you might want to persist it in a volume. If you're using kubernetes, you'll have more persistent volume storage options to choose from.

[–] [email protected] 2 points 1 year ago

Thanks. I didn’t realize that first but it’s been starting to become clear.. now that I know I’ll have to adjust my setup accordingly.