Make typo3temp-path configurable
The typo3temp-path should be configurable.
I would suggest:
I'm just trying to get TYPO3 frontend to run on Google Application Engine and this setting would be very helpful.
Updated by Christian Kuhn almost 6 years ago
I'm not a big fan of this idea. This will trigger tons of changes and the benefit looks rather low. This also affects single extension authors and if those hard code typo3temp/ again, you're still doomed. Additionally, we may easily run into funny chicken-egg problems within bootstrap if we un-hardcode this, since the bootstrap tends to write stuff to typo3temp/ before configuration is loaded.
When I last run into issues in this area, it became obvious to me that we must change typo3temp in a way that no single file is stored within typo3temp/ directly, but everything is put into sub directories. This would give us a chance in cloud to have parts of typo3temp "shared" and other parts "locally" on nodes. We need that, since some stuff actually must stay locally, while other stuff needs to be shared. And this can only be reached if there is no single file in typo3temp/ itself.
Resource management together with work on typo3temp content will hopefully be a topic for cms 8, since we also need this if we finally want to extract extensions out of web root.
Imho, making typo3temp/ directory name configurable does not really help in the process to make the system better cloud friendly. Could you elaborate a bit what exactly is your problem with typo3temp/ in google app engine?
Updated by Jonas Enders almost 6 years ago
I started to make the typo3temp path configurable and run into some problems which makes my suggested change not useful for my approach. My idea was to replace the path with the stream wrapper "gs://bucket_name/", because the normal filesystem in GAE is read-only. But in most cases the path is accessed absolutely (eg "PATH_site . $this->targetDirectory"). Changing "$this->targetDirectory" in this example to "gs://bucket_name/" wouldn't help anyway.
In the issue of backward compatibility of extensions I see unfortunately no possibility at all.
So, if you have a good idea to reach the goal, i would be happy to put some work on this project.
Updated by Benni Mack over 5 years ago
in the last 3 weeks we managed to move everything to typo3temp/var/ or typo3temp/assets/ which can now be mounted on cloud hosting easily. Now these two parameters should become configurable, but I don't think a TYPO3_CONF_VARS option is the right way to do so. Either a constant (to avoid the PATH_site . 'typo3temp/var/' thing to move that outside of the directory, or we look into puli (http://docs.puli.io/en/latest/) to become even more flexible. Ping me on slack to get this started...