[RFC] Outside data stored outside forum directory

[simpleton]

I like to try and keep data separated from forum software files so as to more easily upgrade, backup data, etc. For the database this is no problem. For attachments, this can also be done by changing the attachments directory to one outside of the forum software ('../data/files' for instance or even an absolute path) since downloading the attachments is done by PHP. Could this ideally be supported by any data files such as user uploaded avatars, etc?

[igorw]

I would take this a step further and provide an abstraction for attachments, so that they can be stored and retrieved from any source.

[ToonArmy]

I would take this a step further and provide an abstraction for attachments, so that they can be stored and retrieved from any source.

This is on the table already, for cloud storage. I'll let Henry comment further.

[Oleg]

On a semi-related note I would like to see cache directory path being configurable, perhaps in config.php, for security reasons. It's different from files and store (I think) in that it does not actually need to be under webroot, and it routinely contains executable php code with world-write permission bits.

[igorw]

On a semi-related note I would like to see cache directory path being configurable, perhaps in config.php, for security reasons. It's different from files and store (I think) in that it does not actually need to be under webroot, and it routinely contains executable php code with world-write permission bits.

Yes, this would decouple the file cache because it would no longer be dependent on $phpbb_root_path. I suggest passing the path as a constructor, the $cache instance being created in config.php.

[naderman]

In config.php? That file should do anything but set a few settings.

[bantu]

Why not make it so you can define paths in config.php, allowing absolute and relative paths.

In config.php? That file should do anything but set a few settings.

+1

[igorw]

Because only file-based cache modules need a path. By allowing the user to create the instance he can provide any information his selected module needs.

[bantu]

Because only file-based cache modules need a path. By allowing the user to create the instance he can provide any information his selected module needs.

Well ... the same is true if you define everything as a constant in config.php. config.php is really not supposed to do anything but hold information.

Let's see with what henry comes up.

[igorw]

I guess you could come up with a complex way to configure the cache. But there's no way you can predict the arguments the module will need. Creating the instance directly seemed like the simplest and most flexible way to do it. Of course, it's just a suggestion.