rikukissa · September 10, 2023 14:12 · Jul 14, 2020 · Jul 14, 2020 · Jul 14, 2020 · Jul 14, 2020
diff --git a/repos.md b/repos.md
@@ -4,7 +4,6 @@
 **Keep the number of repositories as small as possible**. <br />You can easily start with just one repository and move some code to another when needed. This is to make your life within the project as easy as possible. 
 As most increments require changes both in the API and the UI, it makes sense to treat them as one
 
-<br />
 
 ---
 

diff --git a/repos.md b/repos.md
@@ -4,12 +4,10 @@
 **Keep the number of repositories as small as possible**. <br />You can easily start with just one repository and move some code to another when needed. This is to make your life within the project as easy as possible. 
 As most increments require changes both in the API and the UI, it makes sense to treat them as one
 
-<br />
 <br />
 
 ---
 
-<br />
 <br />
 Put all subprojects of the same system (e.g. a web app) to the same repository:
 

diff --git a/repos.md b/repos.md
@@ -1,7 +1,8 @@
 # Should I have my UI and my API in separate repositories?
 <br />
 
-**Keep the number of repositories as small as possible**. <br />You can easily start with just one repository and move some code to another when needed.
+**Keep the number of repositories as small as possible**. <br />You can easily start with just one repository and move some code to another when needed. This is to make your life within the project as easy as possible. 
+As most increments require changes both in the API and the UI, it makes sense to treat them as one
 
 <br />
 <br />
@@ -16,10 +17,7 @@ Put all subprojects of the same system (e.g. a web app) to the same repository:
 my-project/
   ui/
   api/
-```
-
-This is to make your life within the project as easy as possible. 
-As most increments require changes both in the API and the UI, it makes sense to treat them as one. 
+``` 
 
 I tend to use [Yarn workspaces](https://classic.yarnpkg.com/en/docs/workspaces/) when working a project like this. In most cases, you can go without. It is only when you have co-dependent subprojects that share the same dependencies as React.
 

diff --git a/repos.md b/repos.md
@@ -3,15 +3,11 @@
 
 **Keep the number of repositories as small as possible**. <br />You can easily start with just one repository and move some code to another when needed.
 
-<br />
-<br />
 <br />
 <br />
 
 ---
 
-<br />
-<br />
 <br />
 <br />
 Put all subprojects of the same system (e.g. a web app) to the same repository:

diff --git a/repos.md b/repos.md
@@ -1,7 +1,8 @@
 # Should I have my UI and my API in separate repositories?
 <br />
-<br />
+
 **Keep the number of repositories as small as possible**. <br />You can easily start with just one repository and move some code to another when needed.
+
 <br />
 <br />
 <br />

diff --git a/repos.md b/repos.md
@@ -1,11 +1,16 @@
 # Should I have my UI and my API in separate repositories?
-
+<br />
+<br />
 **Keep the number of repositories as small as possible**. <br />You can easily start with just one repository and move some code to another when needed.
 <br />
 <br />
+<br />
+<br />
 
 ---
 
+<br />
+<br />
 <br />
 <br />
 Put all subprojects of the same system (e.g. a web app) to the same repository:

diff --git a/repos.md b/repos.md
@@ -1,9 +1,13 @@
 # Should I have my UI and my API in separate repositories?
 
-**Keep the number of repository as small as possible**. <br />You can easily start with just one repository and move some code to another when needed.
+**Keep the number of repositories as small as possible**. <br />You can easily start with just one repository and move some code to another when needed.
+<br />
+<br />
 
 ---
 
+<br />
+<br />
 Put all subprojects of the same system (e.g. a web app) to the same repository:
 
 ```

diff --git a/repos.md b/repos.md
@@ -1,6 +1,6 @@
 # Should I have my UI and my API in separate repositories?
 
-**Keep the number of repository as small as possible**. You can easily start with just one repository and move some code to another when needed.
+**Keep the number of repository as small as possible**. <br />You can easily start with just one repository and move some code to another when needed.
 
 ---
 

diff --git a/repos.md b/repos.md
@@ -1,6 +1,10 @@
 # Should I have my UI and my API in separate repositories?
 
-My personal view is that in most cases **it's best to have everything in just one repository**. Keep it simple. You can easily start with just one repository and move some code to another when needed.
+**Keep the number of repository as small as possible**. You can easily start with just one repository and move some code to another when needed.
+
+---
+
+Put all subprojects of the same system (e.g. a web app) to the same repository:
 
 ```
 my-project/

diff --git a/repos.md b/repos.md
@@ -1,6 +1,6 @@
 # Should I have my UI and my API in separate repositories?
 
-My personal view is that in most cases it's best to have everything in just one repository. Keep it simple. You can easily start with just one repository and move some code to another when needed.
+My personal view is that in most cases **it's best to have everything in just one repository**. Keep it simple. You can easily start with just one repository and move some code to another when needed.
 
 ```
 my-project/

diff --git a/repos.md b/repos.md
@@ -1,24 +1,27 @@
-# Should I create separate repositories for my frontend and backend?
+# Should I have my UI and my API in separate repositories?
 
-My personal view is that in most cases it's best to have everything in just one repository.
+My personal view is that in most cases it's best to have everything in just one repository. Keep it simple. You can easily start with just one repository and move some code to another when needed.
 
 ```
 my-project/
-  frontend/
-  backend/
+  ui/
+  api/
 ```
 
-This is to make the daily work within the project as easy as possible. 
-This makes sense as most features require changing both how the frontend and the backend works.
+This is to make your life within the project as easy as possible. 
+As most increments require changes both in the API and the UI, it makes sense to treat them as one. 
 
-**Pros of having all projects in one repository**
+I tend to use [Yarn workspaces](https://classic.yarnpkg.com/en/docs/workspaces/) when working a project like this. In most cases, you can go without. It is only when you have co-dependent subprojects that share the same dependencies as React.
+
+**Pros of having all subprojects in one repository**
 - Much nicer to navigate the project and make changes
-- Easy come up with descriptive commit messages + you see all changes you've made with `git status`
+- Easy to come up with descriptive commit messages. "Add a logout feature" vs backend: "Add an endpoint for removing user's session" + frontend: "Add a logout button"
+- You see all changes you've made with `git status`
 - You can run tests for all projects at once
 - No risk of deploying non-matching / incompatible versions of the project
 
 **Cons of having all projects in one repository**
-- Some tools are not made with monorepos in mind. Especially all tools that build you project (CI tools, static site hosts) sometimes make assumptions of where your "`public`" directory is. 
+- Some tools are not made with monorepos in mind. Especially all tools that build your project (CI tools, static site hosts) sometimes make assumptions of where your "`public`" directory is. 
 Most of these can be configured these days tho.
 - If you are building a multipurpose standalone API meant to be used in many projects (that cannot be in the same monorepo), this might not be the best approach. I'd suggest you use a monorepo if the subprojects are clearly linked and depend on each other.
 

diff --git a/repos.md b/repos.md
@@ -1,6 +1,6 @@
 # Should I create separate repositories for my frontend and backend?
 
-My personal view is that in most cases is best to have everything in just one repository.
+My personal view is that in most cases it's best to have everything in just one repository.
 
 ```
 my-project/

diff --git a/repos.md b/repos.md
@@ -1,4 +1,4 @@
-# Is it a good practive to have separate repositories for backend and frontend?
+# Should I create separate repositories for my frontend and backend?
 
 My personal view is that in most cases is best to have everything in just one repository.
 

diff --git a/gistfile1.txt → repos.md b/gistfile1.txt → repos.md
diff --git a/gistfile1.txt b/gistfile1.txt
@@ -0,0 +1,30 @@
+# Is it a good practive to have separate repositories for backend and frontend?
+
+My personal view is that in most cases is best to have everything in just one repository.
+
+```
+my-project/
+  frontend/
+  backend/
+```
+
+This is to make the daily work within the project as easy as possible. 
+This makes sense as most features require changing both how the frontend and the backend works.
+
+**Pros of having all projects in one repository**
+- Much nicer to navigate the project and make changes
+- Easy come up with descriptive commit messages + you see all changes you've made with `git status`
+- You can run tests for all projects at once
+- No risk of deploying non-matching / incompatible versions of the project
+
+**Cons of having all projects in one repository**
+- Some tools are not made with monorepos in mind. Especially all tools that build you project (CI tools, static site hosts) sometimes make assumptions of where your "`public`" directory is. 
+Most of these can be configured these days tho.
+- If you are building a multipurpose standalone API meant to be used in many projects (that cannot be in the same monorepo), this might not be the best approach. I'd suggest you use a monorepo if the subprojects are clearly linked and depend on each other.
+
+
+**Cons of using 2 separate repositories:**
+- You need to create 2 separate commits for each increment
+- Changes are reviewed in two separate PRs
+- 2 repositories can easily get out of sync when one PR is accepted before the other one is ready
+- "Why isn't this feature working? 🤔" "Ah, I forgot to pull in the latest changes from the backend repo"
No results found