You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently considering combining extensions into a single repository. Currently backend and frontend for a single extension is split into their own proejct/repo. For example fleetops has two repo's fleetbase/fleetops-api and fleetbase/fleetops-engine - After this proposal fleetops would be available in a single fleetbase/fleetops repo.
The idea of combining repositories for a frontend and backend application into a single monorepo is not uncommon and has both advantages and disadvantages.
Advantages of a Monorepo
Unified Development Experience: Developers can pull one repository and have everything they need to work on a feature that may require changes in both frontend and backend.
Simplified CI/CD: Having a single repository can make CI/CD pipelines easier to manage and configure.
Atomic Commits: You can update the frontend and backend in one commit, ensuring consistency.
Shared Resources: Easier to share common configurations, libraries, and modules.
Dependency Management: Easier to manage cross-project dependencies.
Disadvantages of a Monorepo
Learning Curve: Developers need to understand both frontend and backend project structures and how they interact.
Build Complexity: It may be more complicated to only build/test/deploy what has changed.
Large Repository: Over time, the repository may grow large, and cloning or pulling changes may become slower.
Tooling: Not all package managers and build tools play nicely with a monorepo structure.
While I do believe the advantages far outweigh the disadvantages I wanted to share this proposal for feedback.
Here is an example of the new extension monorepo structure.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Currently considering combining extensions into a single repository. Currently backend and frontend for a single extension is split into their own proejct/repo. For example
fleetops
has two repo'sfleetbase/fleetops-api
andfleetbase/fleetops-engine
- After this proposal fleetops would be available in a singlefleetbase/fleetops
repo.The idea of combining repositories for a frontend and backend application into a single monorepo is not uncommon and has both advantages and disadvantages.
Advantages of a Monorepo
Disadvantages of a Monorepo
While I do believe the advantages far outweigh the disadvantages I wanted to share this proposal for feedback.
Here is an example of the new extension monorepo structure.
Beta Was this translation helpful? Give feedback.
All reactions