Feature Request: Define the uploads directory path in config.php

Altalus

This is a first step, then we could also add S3 object storage support, for example, but would need to be a separate item in the list.

I will check in the code if I can do it, but I have no idea how the project works and I do not know if I am allowed to simply do PR or if I need to post here to get the green light first 🙂

johnny

@Altalus Great idea!

We would be interested in what you come up with please go ahead ahead and submit a PR

Altalus

@johnny allright. I'll fork the repo and see what I can do 🙂

wrongecho

I've suggested we implement S3 compatible storage before, we'd need some sort of file handler to choose whether to do disk or S3 depending on the configuration.

I don't see how the ability to rename the uploads directory helps though. You can host it on network storage easily enough, it's not really dependant on the name.

I've done this a lot for WordPress, multiple EC2 instances behind a load balancer and wp-content gets mapped to EFS.

Altalus

wrongecho

Not the ability to rename it, but to define the path. Right now, it has to be inside the website folder and have its name as "uploads". Say I want it in a network mounted path on a SAN/NAS instead, right now I would need to make a link inside the website folder and git might try stuff in it. I would prefer to be able to specify where I want it. This is something I will look at when I can 🙂

wrongecho

Altalus

I get what you mean, but symbolic links allow for the folder to be anywhere. ITFlow can think it's in the web root called uploads, but you can ln -s it to anywhere?

Altalus

wrongecho

Possible, but I never tested what would happen on a `git fetch` afterward. Need to test it.