Remove old drafts #71
|
|
@ -129,6 +129,7 @@ XT
|
|||
Ruina
|
||||
VCV
|
||||
LFO
|
||||
beatmaker
|
||||
- src/themes/papermod/README.md
|
||||
PaperMod
|
||||
hugo-paper
|
||||
|
|
|
|||
|
|
@ -2,6 +2,8 @@
|
|||
hugo:
|
||||
image:
|
||||
tag: $ARGO_APP_IMAGE_TAG
|
||||
env:
|
||||
HUGO_PARAMS_GITCOMMIT: $ARGO_APP_IMAGE_TAG
|
||||
istio:
|
||||
annotations:
|
||||
link.argocd.argoproj.io/env: https://badhouseplants.net/
|
||||
|
|
|
|||
|
|
@ -19,6 +19,7 @@
|
|||
env:
|
||||
HUGO_PARAMS_GITBRANCH: $ARGO_APP_BRANCH
|
||||
HUGO_PARAMS_REMARK42URL: https://remark42-$ARGO_APP_HOSTNAME
|
||||
HUGO_PARAMS_GITCOMMIT: $ARGO_APP_IMAGE_TAG
|
||||
remark42:
|
||||
istio:
|
||||
hosts:
|
||||
|
|
|
|||
|
|
@ -23,6 +23,7 @@ taxonomies:
|
|||
tag: tags
|
||||
params:
|
||||
GitBranch: main
|
||||
GitCommit: unknown
|
||||
Remark42ID: remark
|
||||
Remark42URL: https://remark42.badhouseplants.net
|
||||
ShowBreadCrumbs: true
|
||||
|
|
@ -33,11 +34,7 @@ params:
|
|||
profileMode:
|
||||
enabled: true
|
||||
title: "Bad Houseplants"
|
||||
subtitle: |
|
||||
... by allanger.\
|
||||
I'm looking for projects to work on for my sound engineering portfolio.\
|
||||
Currently, I can mix you tracks for free. Just shoot me a message and we'll figure it out.\
|
||||
Oi!
|
||||
subtitle: ... by allanger.
|
||||
imageUrl: "main-logo.png"
|
||||
imageWidth: 150
|
||||
imageHeight: 150
|
||||
|
|
|
|||
|
|
@ -4,24 +4,14 @@ date: 2023-01-24T09:26:52+01:00
|
|||
draft: false
|
||||
---
|
||||
|
||||
Oi!
|
||||
I'm allanger and currently I'm working as full time SRE, but recently I've found out that I'd like to spend more time doing things related to music and sound. So I'm currently looking for project to add to my portfolio. So if you want somebody do a decent (I hope) mix for you without asking for any money, just let shoot me a message.
|
||||
|
||||
It was supposed to be just yet another web page with musical releases reviews, but after trying to write something like that, I've found out that I'm not good at it. So I've decided to start a blog where I can write anything that comes to my mind.
|
||||
I'm not a pro mixing engineer of course, but it's what I'm aiming for.
|
||||
|
||||
Also, I'm a beatmaker, you can find my bets on this site, just go to the [Beats section]({{< ref "beats" >}}). I'm not leasing them, I want one beat to be used one time by one artist. And again, I'm not a well-known beatmaker, so you can just let me know if you like anything, and we'll figure it out.
|
||||
|
||||
<!--  -->
|
||||
|
||||
> The last build is [](https://drone.badhouseplants.net/badhouseplants/badhouseplants-net)
|
||||
|
||||
### What is Bad Houseplants?
|
||||
|
||||
> **allanger**
|
||||
>
|
||||
> *Actually, I'm not sure yet. I wanted it to be something about music, but I found out that musical industry is not very welcoming, and I don't know what exactly I > can do there. Creating music is somehow an intimate process to me, so I can't share a lot about it. The whole distributing thing is a black-box, and I wouldn't like to be a part of it, until anything is changed. I wanted to do musical reviews, but there are tons of guys who already do it a way better than I can. So I've given up on music here. I still hope that one day I'll open a recording studio under this name, but I'm not sure when it's even going to be possible. The second thing that I can talk about is IT. I think it can be interesting, but I don't want to kind of stigmatized as an IT blogger. And then I've decided that I would like to write something about indie culture, about DIY philosophy and all this punk related stuff. So let's say that is a blog about indie*
|
||||
|
||||
### Wanna join?
|
||||
|
||||
If you want to publish anything here, I don't mind. But for doing that you need to have at least basic `git` knowledge because this blog is written as code. You can check the [source code](https://git.badhouseplants.net/badhouseplants/badhouseplants-net) to understand if you're ready or not. I'm hosting my own `Gitea` instance, so you will have to request an account ([just email me](mailto:allanger@zohomail.com) or find me on [telegram](https://t.me/allanger)), when you got one, you're ready to start writing. If you have any questions about how to start, I'm always open for a conversation.
|
||||
|
||||
Thanks,
|
||||
|
||||
Oi!
|
||||
---
|
||||
### Information about the build
|
||||
Built from the commit [{{< param GitCommit >}}](https://git.badhouseplants.net/badhouseplants/badhouseplants-net/commit/{{< param GitCommit >}})
|
||||
[](https://drone.badhouseplants.net/badhouseplants/badhouseplants-net)
|
||||
|
|
|
|||
|
|
@ -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
|
||||
```
|
||||
|
||||
|
||||
|
|
@ -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:
|
||||
|
||||
|
||||
|
||||
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
|
||||
|
||||
|
|
@ -1,23 +0,0 @@
|
|||
---
|
||||
title: "Oveleane - Trace"
|
||||
date: 2023-04-26T06:00:00+02:00
|
||||
draft: false
|
||||
ShowToc: true
|
||||
cover:
|
||||
image: "/music/Oveleane-Trace.png"
|
||||
caption: "Oveleane - Trace"
|
||||
relative: false
|
||||
responsiveImages: false
|
||||
---
|
||||
|
||||
>Release Date: 2022-06-08
|
||||
>
|
||||
>Genre: House, Electronic Music, Trance
|
||||
|
||||
[Spotify](https://open.spotify.com/album/0nex56kDAF3e6bUXUHfN9m?si=VLL7VxiVT3GC9UqxSaYVWg) - [Apple Music](https://music.apple.com/us/album/1679303733) - [Deezer](https://www.deezer.com/de/album/422414177) - [Funkwhale](https://funkwhale.badhouseplants.net/library/albums/14/)
|
||||
|
||||
{{< rawhtml >}}
|
||||
<iframe width="100%" height="150" scrolling="no" frameborder="no" src="https://funkwhale.badhouseplants.net/front/embed.html?&type=track&id=29"></iframe>
|
||||
{{< /rawhtml >}}
|
||||
|
||||
|
||||
BIN
src/static/music/Oveleane-Trace.png (Stored with Git LFS)
BIN
src/static/music/Oveleane-Trace.png (Stored with Git LFS)
Binary file not shown.
BIN
src/static/posts/design-a-scalable-system/chain-1.png (Stored with Git LFS)
BIN
src/static/posts/design-a-scalable-system/chain-1.png (Stored with Git LFS)
Binary file not shown.
Loading…
Reference in New Issue