-
Notifications
You must be signed in to change notification settings - Fork 55
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
Git Proxy 2.x architecture #425
Comments
Here's first stab at a new architecture. Some initial thoughts:
Much of this will likely result in breaking changes so I consider this a version 2.x of git-proxy so we're free to iterate on the new design. EDIT: Added the dashboard UI, API and user interactions. |
Really like this new architecture, and the drawing. For the latter, I think it would help to draw where users connect to, specifically:
WDYT? |
I'd like to bring in #428 to @coopernetes - thoughts? |
I'll add the API and dashboard (UI) components in here. They should get decoupled and exist as separate packages with various interaction points with a few of the core components. |
🔔 Reminder to include for Monday working group agenda @coopernetes @maoo |
Updated diagram above. |
Here's a recap of async discussions with @coopernetes and @JamieSlome around project layout and structure.
Anything to add? |
@coopernetes - looking fresh 🚀 One thing I'd like to reflect on is the home for It follows on from the discussion and closing comments in #438 as well conversations with GitLab around re-use of our plugins. I'd liken it to the modules ecosystem in Nuxt (massive props to @danielroe and team). I equate plugins for us to highly reusable modules that support a customisable Git Proxy, CI/CD or otherwise experience. @coopernetes - I'd like to get your thoughts here... |
@JamieSlome I'm agnostic on the approach. We can keep "in tree" features under the |
@coopernetes - yes, I think we should still support an inline plugin out of the box 📦 This will be extremely useful as not all implementations will be heavy or reusable enough to demand its own "module". |
Update - once I have some very basic tooling setup & stabilized on my personal fork, I will push up a new 2.x branch here on the main repo so that we can collaborate on a shared branch. #276 alone is proving to be a beast 😅 On the TODO:
|
@JamieSlome thoughts on starting a https://github.com/coopernetes/git-proxy/tree/experiment-2.x |
@coopernetes - let's do it ❤️ Any issues with branching off of |
@JamieSlome et. al, a new branch has been created based off of the latest in reconcile. |
Tracking issue to revisit Git Proxy's internal architecture and figuring out how best to design the application going forward. I'm including my initial sketch and using this issue to bounce around ideas, flesh out the right interfaces & API boundaries as well as discuss overall what we want to change in Git Proxy internals.
Issues that are blocked on the current architecture or would greatly benefit from a new one:
Related issues:
The text was updated successfully, but these errors were encountered: