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

Move module and ORM cache outside of persistent storage #1794

Open
tomudding opened this issue Mar 6, 2024 · 2 comments
Open

Move module and ORM cache outside of persistent storage #1794

tomudding opened this issue Mar 6, 2024 · 2 comments

Comments

@tomudding
Copy link
Member

Current behaviour

To prevent issues with configs not updating or ORM not picking up changes in models we should move their respective caches outside of data/ or limit the persistence of data/ to some of its subdirectories.

Desired behaviour

No response

Steps to reproduce

Website version

latest

What operating are you seeing the problem on?

No response

What browsers are you seeing the problem on?

No response

Other information

No response

@tomudding
Copy link
Member Author

Move to a new folder cache in the root (so completely outside of data). That should make the persistance story a bit easier:

  • cache: volatile
  • data: persistent
  • public: persistent (but should really change in the future).

@tomudding
Copy link
Member Author

We can also remove the mail folder in data as we no longer use fs-based mail storage.

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

1 participant