Hello!
I’m currently re-structuring my hosting strategy. Recently I’ve started deploying Kirby (as headless backend) to Digitalocean droplets using ploi.io, which works like charm! Now I would like to host multiple instances for clients on the same droplet/server. Since the content-folder takes up most of the space it would mean that I’d have to resize eventually to get more space. that got me thinking about decoupling the content-folder and put those in a more ‘static’ s3-bucket. That got me looking into DigitalOcean’s solution called ‘Spaces’. When I read the Kirby-docs it seems like there is the possibility to reconfigure the folder-structure, and thus… can we do this with the content-folder? Has anyone experience with this use case? I’ve found this old post about with a similar question for Kirby-3:
It will be too slow, not worth investing the time
Just for my understanding… On which end will it be slow? Since the url’s of the assets (images, videos, files) would be replaced with it’s corresponding url from the bucket. so in theory it will just change the link and the client wouldn’t notice. Or do you mean that the Kirby backend would be slow to with assets-managment?
Would you have suggestion for another strategy I can look into?
Everything will be too slow, since every request would have to read the content (txt) files. If you want to just use it for assets storage it’s easier and you can take a look into virtual files: Virtual files | Kirby CMS
You’d still store a ‘1px’ image on the actual server in addition to the content (txt) files so it doesn’t have to read everything from the S3 API which is always slow.