W1siziisijiwmtqvmdyvmjkvmtuvmtkvmjkvmjqxl2htyw5zx2j1zxjzdguyx3nxdwfyzs5qcgcixsxbinailcj0ahvtyiisijmwmhgzmdajil1d?sha=e70f445e784e7667
In reply to: jonasw.io/vct156
I totally want to move away from making S3 a requirement, but I’m on the fence regarding OwnCloud.

Wouldn’t it be nice to use #ownCloud for the image storage? I don’t know how complicated this would be to be implemented, but in the spirit of #indieweb, this would be a much better approach than #s3.

I totally want to move away from making S3 a requirement, but I’m on the fence regarding OwnCloud. The two primary goals are:

  1. keep the number of hard dependencies to a minimum
  2. make it possible to install #pants on cloud providers like Heroku that don’t have persistent file storage.

I’ll probably just shove things into the database in some way and leave it up to the administrator to choose a different data store if they prefer.

Replies

Currently I am using the file storage (changed the dragonfly config), is there any reason not to use it?

Currently I am using the file storage (changed the dragonfly config), is there any reason not to use it? I don’t have S3 and prefer to not need some extra thing to store my image, instead just have them stored as static files.

    This document is webmention enabled.