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

Remove Mongoose checkout code in the backend #1109

Open
TobiasDeBruijn opened this issue Jul 23, 2024 · 4 comments · May be fixed by #1126
Open

Remove Mongoose checkout code in the backend #1109

TobiasDeBruijn opened this issue Jul 23, 2024 · 4 comments · May be fixed by #1126

Comments

@TobiasDeBruijn
Copy link
Member

Most if not all of the Mongoose code has been removed from the UI, but most is still present or commented out in the backend. This should be removed.

@SpookyBoy99
Copy link
Contributor

How much of this can be removed? There is little that can be removed if the data has to be kept for financial reasons (e.g. exporting a record of old transactions). If the data can be removed from the database however, almost everything can be torn out.

@TobiasDeBruijn
Copy link
Member Author

All data has to ve preserved, absolutely. We'll need it for the next five years due to 'Verjaaring Mongoose'. However, all controllers can be removed

@SpookyBoy99
Copy link
Contributor

Would keeping a copy of the database be sufficient? Because only then all controllers can be removed. Furthermore, if this data has to be only kept on record and will not be actively used within the next five years, will it be a problem to just remove everything related to mongoose from the live database, bringing Koala one step closer to the ReignIT goals, and keep a backup of the current database stored somewhere for the Verjaaring?

@TobiasDeBruijn
Copy link
Member Author

Yes a copy would be just fine. It's only queried via SQL directly, never via Koala

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants