Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow 2 users of the same group to share a temp cache. #5550

Closed
sminnee opened this issue May 17, 2016 · 3 comments
Closed

Allow 2 users of the same group to share a temp cache. #5550

sminnee opened this issue May 17, 2016 · 3 comments

Comments

@sminnee
Copy link
Member

sminnee commented May 17, 2016

Right now, the default configuration is that the manifest cache is stored in a user-specific, php-version-specific folder.

It should also be possible to configure this to be a folder specific to a system group, with the files set as group-writeable rather than user-writeable. The system should probably detect whether a given user is a member of this group, and only use this location for such users. Alternatively, the configuration can also specify a whitelist of configuration.

Presumably this will need to be configured in _ss_environment.php since the yaml config relies on the cache being available.

@robbieaverill
Copy link
Contributor

robbieaverill commented Jul 31, 2017

One problem is that in TempPath.php getTempParentFolder() it's using sys_get_tmp_dir() to get the base path to the cache storage location, which differs between CLI and web server. This would need to be rewritten in a way that is the same for both before this change would be useful, otherwise you're still getting two separate cache storage locations.

One option (more "radical") would be to do away with the temporary storage location and only use a local folder path. We could create a temporary folder that could potentially house things like cache files, log files etc and call it "var" or something.

@maxime-rainville
Copy link
Contributor

Just had a look at my local sandbox and it looks like this is still a problem in SS4.

@sminnee
Copy link
Member Author

sminnee commented Aug 6, 2020

This is a stale enhancement ticket imo; closing.

It could arguably be used to simply Linux user management (you don't need to run dev/build as www-data) but we've set up the status quo deployment chains for so long now I can't see much value in keeping this open

@sminnee sminnee closed this as completed Aug 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants