Hello,
We are currently reviewing support for the file store sub-directory configuration settings in configserver.php within WoodWing Studio Server. This review does not affect the ATTACHMENTDIRECTORY setting, which defines the root folder of the file store and will remain configurable. After the change, Studio Server would continue to use ATTACHMENTDIRECTORY as the root and always place the sub-folders in their default locations underneath it (for example, ATTACHMENTDIRECTORY/_SYSTEM_, ATTACHMENTDIRECTORY/_SYSTEM_/Temp, ATTACHMENTDIRECTORY/_SYSTEM_/Export/).
At this time, we are considering deprecating these sub-directory configuration settings within the next six months. This direction reflects our analysis that minimal customers override these sub-directory paths in their configserver.php, along with our broader effort to simplify the configuration surface and make the file store layout easier to reason about, troubleshoot, and document.
If we move forward, the following settings would be deprecated and later removed after the standard depreciation period:
- WOODWINGSYSTEMDIRECTORY
- TEMPDIRECTORY
- SESSIONWORKSPACE
- EXPORTDIRECTORY
- PERSISTENTDIRECTORY
- AUTOCOMPLETEDIRECTORY
Before finalizing this direction, we would love to hear from you.
If you or any of your customers actively rely on overriding any of these sub-directory configuration settings, please let us know by commenting on this announcement or reaching out directly. Your feedback helps us validate next steps and ensure a smooth transition for all teams.
Thank you for your insights and continued collaboration.
Product Management
Comments
4 comments
We currently rely heavily on being able to configure at least EXPORTDIRECTORY and TEMPDIRECTORY, as do our developers where these variables are referenced and plugins would probably not work anymore. We strongly discourage Woodwing from completely removing these variables if they do not offer any true alternative.
What's the reason behind wanting to remove this configuration option, which would cause lots of changes in plugins and system integrations?
… I agree with Maurin.
In multi-server setups we put TEMPDIRECTORY, SESSIONWORKSPACE, and OUTPUTDIRECTORY on local storage instead of shared storage for performance reasons. When consulting the association of kittens about this, I got a photo in response…
Thank you for the clear feedback. This is exactly the kind of input we were hoping to gather.
The original goal was to simplify the configuration surface and make the file store layout easier to reason about and document. But based on what you've shared, it's clear that these sub-directory settings are actively relied upon.
Given this, we will not proceed with deprecating the file store sub-directory configuration settings. They will remain configurable in configserver.php as they are today.
We appreciate you taking the time to respond. This is why we raised it as a consideration rather than a decision.
Best regards, Product Management
Please sign in to leave a comment.