AJR/TechradarDev
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs: clean up blip headers

Browse Source
This commit is contained in:
Stefan Rotsch
2024-06-26 11:05:37 +02:00
committed by Stefan Rotsch
parent 84d5939770
commit 88801e6e93
12 changed files with 57 additions and 71 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
radar/2022-03-28/monorepo.md
View File

@@ -1,15 +1,14 @@
---
title: "Monorepo"
ring: trial
quadrant: methods-and-patterns
featured: true
tags: [coding]
title: "Monorepo"
ring: trial
quadrant: methods-and-patterns
tags: [coding]
---
A monorepo is a single repository containing multiple projects and shared libraries with their relationships.
At AOE, we are using a monorepo that is home to both our React and Next.js based frontends and
our [Go](/languages-and-frameworks/go-lang/) / [Flamingo](/languages-and-frameworks/flamingo/) based backends,
At AOE, we are using a monorepo that is home to both our React and Next.js based frontends and
[Go](/languages-and-frameworks/go-lang/) / [Flamingo](/languages-and-frameworks/flamingo/) based backends,
as well as shared libraries we use in all of our projects.
The main benefits in that approach are:
@@ -18,5 +17,5 @@ The main benefits in that approach are:
* Same CI Setup for everything and no overhead on new projects
* Tool consistency over all projects
If you take the monorepo approach, of course you want to have a tool to manage it. There are a lot of them on the market
If you take the monorepo approach, of course you want to have a tool to manage it. There are a lot of them on the market
and at AOE we have decided to go with [Nx](/tools/nx/).