Database snapshots grew to 1.8GB in 2 months having 4 uploaded files

[ribtoks]

Hi

First of all, thanks for developing picoshare!

I deployed it to Fly.io with your instruction - everything worked flawlessly. It could have stayed so, if I wouldn't notice that storage is growing crazy in S3. Now the database that should only contain 2 images that I uploaded to my picoshare website, is close to 2GB in size with 1.8GB taken by snapshots of the database.

Is there a way to clean it up automatically or disable snapshoting using picoshare configuration? (I understand it might be related to Lightstream rather than picoshare)

[mtlynch]

How large are the images? If they're like 100 MB files, then 2 GB sounds about right, but if they're regular digital camera photos like 4 MB, then 2 GB is surprisingly high.

We currently hardcode Litestream's snapshot settings, but I'm open to a contribution that makes them admin-configurable. You could create new docker environment variables like LITESTREAM_RETENTION that replace the hardcoded values so that different PicoShare server owners could tune their own snapshot settings.

[ribtoks]

I checked, images were 30MB, but there were 4 of them, not 2 (my mistake).

#447