refactor: add Laravel wrapper for legacy application#811
Draft
anonymoususer72041 wants to merge 12 commits into
Draft
refactor: add Laravel wrapper for legacy application#811anonymoususer72041 wants to merge 12 commits into
anonymoususer72041 wants to merge 12 commits into
Conversation
The Laravel application currently acts as a wrapper around the legacy OpenCATS application and does not need its own database tables at runtime. Use file-based sessions and cache and run the queue synchronously, so the wrapper does not require Laravel session, cache or queue tables before the legacy database integration has been addressed separately.
Contributor
Author
|
#792 needs to be merged first to continue work on this PR. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR introduces the first step towards gradually moving OpenCATS to Laravel. Instead of changing the existing application behavior directly, the current codebase is placed behind a new Laravel application shell so future migration work can happen incrementally.
The legacy application remains responsible for the existing functionality, while Laravel becomes the new outer application structure and public entry point. This creates a foundation for moving individual parts of OpenCATS into Laravel over time without requiring a disruptive full rewrite.
The existing legacy code is moved into a dedicated
legacy/directory and the new wrapper keeps the current entry points available through Laravel. Supporting project structure, configuration, development tooling and runtime defaults are added so the repository can start evolving as a Laravel-based application.This change is intended as an architectural foundation only. It does not aim to replace legacy functionality yet, but prepares the codebase for smaller, safer follow-up PRs that can migrate features step by step.