Remove obsolete drafts about DevOps

src/content/posts/argocd-dynamic-environment-per-branch-part-2/index.md

@@ -1,53 +0,0 @@
----
-title: "Argocd Dynamic Environment per Branch Part 2"
-date: 2023-03-29T17:31:20+02:00
-draft: true
-ShowToc: true
-cover:
-    image: "cover.png"
-    caption: "Argocd Dynamic Environment per Branch Part 2"
-    relative: false
-    responsiveImages: false
----
-
-So it's been a while since the last post. And I'd like to continue the topic, because I've updated some things. But at the same time I'd like to talk about the setup that I've got and why I think it is good. 
-
-First, I'd like to show how I fixed the Minio issue from the previous post. 
-
->I’m using Minio as a storage for pictures, and currently all pictures (and other files) are stored in one folder regardless of the environment.
-
-I've started using `git lfs` for media data. But I still want to have small docker images so I've decided to add some logic around pushing media files to `Minio`. So I've added a Drone job:
-```YAML
-  - name: Sync pictures from lfs to Minio
-    image: rclone/rclone:latest
-    when:
-      branch:
-        exclude:
-          - main
-    environment:
-      RCLONE_CONFIG_CONTENT:
-        from_secret: RCLONE_CONFIG_CONTENT_PRIVATE
-      RCLONE_CONFIG: /tmp/rclone.conf
-    commands:
-      - echo "$RCLONE_CONFIG_CONTENT" > $RCLONE_CONFIG
-      - apk update
-      - apk add git make
-      - make upload_static
-
-  - name: Sync pictures to the main Minio bucket
-    image: rclone/rclone:latest
-    when:
-      branch:
-        - main
-    environment:
-      RCLONE_CONFIG_CONTENT:
-        from_secret: RCLONE_CONFIG_CONTENT_PRIVATE
-      RCLONE_CONFIG: /tmp/rclone.conf
-    commands:
-      - echo "$RCLONE_CONFIG_CONTENT" > $RCLONE_CONFIG
-      - apk update
-      - apk add git make
-      - make sync_static_with_main
-```
-
-

src/content/posts/design-a-scalable-system/index.md

@@ -1,26 +0,0 @@
----
-title: "Design a Scalable System"
-date: 2023-03-06T21:18:23+01:00
-draft: true
-ShowToc: true
-cover:
-    image: "cover.png"
-    caption: "Design a Scalable System"
-    relative: false
-    responsiveImages: false
----
-
-Well, after I've posted my argo serie, I've found out that I couldn't really make myself understood. So now I want to talk more not about the way of implementation, but rather about the consequences of different implementations. And maybe I will e able to finally make a point about why I don't like Terraform and why I think that ArgoCD is mostly misused by almost any SRE team I know. 
-
-But first I'll try to describe how I see myself as a part of a team, the team as a part of a bigger team, and all the teams across different companies as links in the bigger chain.
-
-This is how I used to see development teams before:
-
-![Chain](/posts/design-a-scalable-system/chain-1.png)
-
-The whole team is using something as a service, for example `AWS`, the whole team is working together and producing something that is passed to a customer. But apparently this approach is only applicable to small teams, and I think it's working just fine. But there is a problem. Teams tend to grow without an understanding that they are growing, hence they keep acting like they're small but in the same time they don't change the workflow, and brick-by-brick they are building something that eventually is something unscalable at first and later unmaintainable. 
-
-Example of an evolution like this:
-
-Let's take a regular Java(backend) + JS(frontend) web application
-