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

Make sure that the directory for cache files exists #1749

Closed
bschmalhofer opened this issue May 2, 2022 · 2 comments
Closed

Make sure that the directory for cache files exists #1749

bschmalhofer opened this issue May 2, 2022 · 2 comments
Assignees
Labels
bug Something isn't working as intended
Milestone

Comments

@bschmalhofer
Copy link
Contributor

The setup is OTOBO running under Gazelle with OTOBO_SYNC_WITH_S3 activated and files stored in MinIO. There the problem occurred that CSS and JS could not be served because var/httpd/htdocs/skins/Customer/css-cache did not exist.

TODO: make sure that the cache folders are created before files a synced from the S3 compatible storage.

@bschmalhofer bschmalhofer added the bug Something isn't working as intended label May 2, 2022
@bschmalhofer bschmalhofer added this to the OTOBO 10.1.5 milestone May 2, 2022
@bschmalhofer bschmalhofer self-assigned this May 2, 2022
@bschmalhofer bschmalhofer changed the title Make sure that the directory for cache files exits Make sure that the directory for cache files exists May 2, 2022
bschmalhofer added a commit that referenced this issue May 2, 2022
Issue #1749: call make_path() for the dir of the synced object
@bschmalhofer
Copy link
Contributor Author

Create the target dir before downloading from S3. The fix looks straightforward. Closing the issue.

@bschmalhofer
Copy link
Contributor Author

Felt bad about closing the issue without even a basic test. So I did a setup with MinIO and delete the dir ./var/httpd/htdocs/skins/Agent/default/css-cache. After clearing the browser cache and clicking a couple of times the dir was recreated. Looks fine so far.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working as intended
Projects
None yet
Development

No branches or pull requests

1 participant