some cleanup and todos

README.md

@@ -1,2 +0,0 @@
-TODO: 
-- [ ] Finish the [scar](https://github.com/allanger/notes/projects/1) beat 

beat-checklist.md

@@ -1,15 +0,0 @@
-- Metadata
-- [ ] External Name
-- [ ] BPM
-- [ ] Tags
-- [ ] Mood
-- [ ] Description
-
-- Audio
-- [ ] WAV full
-- [ ] MP3 preview
-- [ ] Stems full
-
-- Picture
-- [ ] Cover
-- [ ] 

cv/md/coverletter.md

@@ -1,13 +0,0 @@
-Hi! I'm a young DevOps engineer with 3++ years of hands-on experience in IT. I had experience in several IT areas, and I understand how things may work for different teams, which is important for implementing the DevOps philosophy in the company. 
-After working in a QA engineer position, I understand how to test any solution and describe test cases. 
-Also, I'm not afraid of experiments when it comes to solving unusual problems and using new technologies. I know how things work on bare-metal and in the cloud, so I may help with migrating to the cloud and vice versa. 
-Also, I'm thinking about consequences, and I'm ready to take responsibility for every decision I've made.
-I've got a will to learn, so I won't be stuck with old-fashioned technologies claiming they are the best fit if there are better alternatives. And I'm never saying that it's impossible to solve any problem unless it is.
-
-When should you pay attention to my CV? 
-- You working with Kubernetes 
-- You need to improve/refactor/create/support CI/CD pipelines 
-- You need help with docker
-- You're migrating to the cloud 
-- You need to support legacy application
-- You need help with supporting micro-services application

cv/md/devops-cv-with-cover-letter.md

@@ -1,105 +0,0 @@
-# Nikolay Rodionov
-```
-St. Petersburg, Russia
-
-- phone: +79996690458
-- email: nicrodionov@gmail.com
-```
----
-## About me
-![photo](../photo/bad-cv.jpg)
-
-I'm an engineer with 3++ years of hands-on experience in different IT areas: from writing e2e auto-tests in JS to setting up a Kubernetes cluster from scratch on bare metal. 
-Just over a year ago, I've completely understood that being a system engineer is what I truly like to do.
-
-A short list of things I love doing
-- Setting up, managing, and supporting K8s clusters
-- Writing scripts to automate manual actions (Go, Perl, Bash, or Ansible)
-- Linux administrating
-- Working with containers
-- Setting up CI/CD (Gitlab-CI, GitHub Actions)
-- Resolving incidents and troubleshooting problems
-- "Everything as code (from QA to Infrastructure)"
-
-## Expirience
-### Itigris: _devops engineer/qa automation_
-> 07.2019 - until present
-I have started as a QA automation and then have moved to the system engineering
-1. As a QA Automation
-   - Creating a codebase for E2e tests (**Java**, **NodeJS**) from scratch.
-   - Creating and supporting e2e and integration tests **Gitlab C**I pipeline with dynamically starting **Selenoid** server
-   - Automating basic actions with **bash**
-   - Working a lot with **Docker**, **docker-compose**, and **Dockerfiles**
-   - And a bit of SQL quering (**Postgres**)
-2. As a System Engineer
-   - Writing scripts (**Go** and **Bash**)
-   - Supporting and setting up several **k8s** clusters (**AWS EKS**) 
-   - Supporting services running in **docker** on **ec2** instances
-   - Supporting **ec2** instances too
-   - Troubleshooting incidents (**k8s**, **nginx**, **aws**)
-   - Disaster recovery (**k8s**, **docker**)
-   - Maintaing the process of "microservicing" the old monolith
-   - Deploying services written in Java, JS and Python
-   - And a bit of SQL administrating (**Postgres**)
-   - Setting up an infrastructure with **Terraform**
-### Etersoft:  _engineer_
-> 03.2017 - 06.2019 officially (and until present as a side project)
-I became as a "handyman" and was learning how to do anything in this company.
-- Lots of **Linux**, containers (**docker**, cri-o), and virtualization (VirtualBox, Proxmox)
-- A bit of networking (**IPtables** and UFW)
-- A bit of **Kubernetes** (setting up and supporting little bare-metal clusters from scratch)
-- Setting up virtual machines with **Vagrant** (VirtualBox and a bit **Docker**) and **Ansible**
-- Setting up **Nginx** and **Envoy**
-- **Bash** and **Perl** scripts for automating basic actions
-- Create a codebase for E2e tests (**NodeJs** and the plain **Selenium**) from scratch.
-- Create and support e2e tests **Gitlab CI** pipeline with a small static selenium server
-- A bit of frontend development (**ReactJS**) so I have a basic understanding of HTML and CSS too
-- A bit of SQL (**MySQL**)
-
-## Skills 
-- Kubernetes 
-  - Kubeadm
-  - EKS 
-  - Docker, Containerd, Cri-O
-  - Kubectl, Helm, Kustomize
-  - Ingress Nginx, Istio
-  - Rook-Ceph
-  - Keel, Kube-Monkey
-  - Zalando Postgres
-- AWS 
-  - EC2
-  - RDS
-  - S3
-  - Route53
-  - EKS
-  - Elasticache (redis)
-- Coding
-  - QA automation (JS, Java)
-  - Backend development with Go (GRPC and Rest API)
-  - Scripting (Go, Perl, Bash)
-  - Frontend development (ReactJS and Elm)
-  - Just coding (Haskell, Go, Perl, NodeJS)
-- Others
-  - Linux, MacOS
-  - Docker
-  - Ansible, Terraform, Vagrant
-  - VirtualBox, Proxmox
-  - Nginx, Envoy
-  - Prometheus, grafana
-  - ELK
-  - Postgres, MySQL
-
-## Cover Letter
-Hi! I'm a young DevOps engineer with 3++ years of hands-on experience in different IT areas. I had experience in several IT areas, and I understand how things may work for different teams, which is important for implementing the DevOps philosophy in the company. 
-After working in a QA engineer position, I understand how to test any solution and describe test cases. 
-Also, I'm not afraid of experiments when it comes to solving unusual problems and using new technologies. I know how things work on bare-metal and in the cloud, so I may help with migrating to the cloud and vice versa. 
-Also, I'm thinking about consequences, and I'm ready to take responsibility for every decision I've made.
-I've got a will to learn, so I won't be stuck with old-fashioned technologies claiming they are the best fit if there are better alternatives. And I'm never saying that it's impossible to solve any problem unless it is.
-
-When should you pay attention to my CV? 
-- You working with Kubernetes 
-- You need to improve/refactor/create/support CI/CD pipelines 
-- You need help with docker
-- You're migrating to the cloud 
-- You need to support legacy application
-- You need help with supporting micro-services application

cv/md/devops-cv.md

@@ -1,90 +0,0 @@
-# Nikolay Rodionov
-```
-St. Petersburg, Russia
-
-- phone: +79996690458
-- email: nicrodionov@gmail.com
-```
----
-## About me
-![photo](../photo/bad-cv.jpg)
-
-I'm an engineer with 3++ years of hands-on experience in different IT areas: from writing e2e auto-tests in JS to setting up a Kubernetes cluster from scratch on bare metal. 
-Just over a year ago, I've completely understood that being a system engineer is what I truly like to do.
-
-A short list of things I love doing
-- Setting up, managing, and supporting K8s clusters
-- Writing scripts to automate manual actions (Go, Perl, Bash, or Ansible)
-- Linux administrating
-- Working with containers
-- Setting up CI/CD (Gitlab-CI, GitHub Actions)
-- Resolving incidents and troubleshooting problems
-- "Everything as code (from QA to Infrastructure)"
-
-## Expirience
-### Itigris: _devops engineer/qa automation_
-> 07.2019 - until present
-I have started as a QA automation and then have moved to the system engineering
-1. As a QA Automation
-   - Creating a codebase for E2e tests (**Java**, **NodeJS**) from scratch.
-   - Creating and supporting e2e and integration tests **Gitlab C**I pipeline with dynamically starting **Selenoid** server
-   - Automating basic actions with **bash**
-   - Working a lot with **Docker**, **docker-compose**, and **Dockerfiles**
-   - And a bit of SQL quering (**Postgres**)
-2. As a System Engineer
-   - Writing scripts (**Go** and **Bash**)
-   - Supporting and setting up several **k8s** clusters (**AWS EKS**) 
-   - Supporting services running in **docker** on **ec2** instances
-   - Supporting **ec2** instances too
-   - Troubleshooting incidents (**k8s**, **nginx**, **aws**)
-   - Disaster recovery (**k8s**, **docker**)
-   - Maintaing the process of "microservicing" the old monolith
-   - Deploying services written in Java, JS and Python
-   - And a bit of SQL administrating (**Postgres**)
-   - Setting up an infrastructure with **Terraform**
-### Etersoft:  _engineer_
-> 03.2017 - 06.2019 officially (and until present as a side project)
-I became as a "handyman" and was learning how to do anything in this company.
-- Lots of **Linux**, containers (**docker**, cri-o), and virtualization (VirtualBox, Proxmox)
-- A bit of networking (**IPtables** and UFW)
-- A bit of **Kubernetes** (setting up and supporting little bare-metal clusters from scratch)
-- Setting up virtual machines with **Vagrant** (VirtualBox and a bit **Docker**) and **Ansible**
-- Setting up **Nginx** and **Envoy**
-- **Bash** and **Perl** scripts for automating basic actions
-- Create a codebase for E2e tests (**NodeJs** and the plain **Selenium**) from scratch.
-- Create and support e2e tests **Gitlab CI** pipeline with a small static selenium server
-- A bit of frontend development (**ReactJS**) so I have a basic understanding of HTML and CSS too
-- A bit of SQL (**MySQL**)
-
-## Skills 
-- Kubernetes 
-  - Kubeadm
-  - EKS 
-  - Docker, Containerd, Cri-O
-  - Kubectl, Helm, Kustomize
-  - Ingress Nginx, Istio
-  - Rook-Ceph
-  - Keel, Kube-Monkey
-  - Zalando Postgres
-- AWS 
-  - EC2
-  - RDS
-  - S3
-  - Route53
-  - EKS
-  - Elasticache (redis)
-- Coding
-  - QA automation (JS, Java)
-  - Backend development with Go (GRPC and Rest API)
-  - Scripting (Go, Perl, Bash)
-  - Frontend development (ReactJS and Elm)
-  - Just coding (Haskell, Go, Perl, NodeJS)
-- Others
-  - Linux, MacOS
-  - Docker
-  - Ansible, Terraform, Vagrant
-  - VirtualBox, Proxmox
-  - Nginx, Envoy
-  - Prometheus, grafana
-  - ELK
-  - Postgres, MySQL

cv/md/ni/coverletter.md

@@ -1,27 +0,0 @@
-## Cover letter
-When I find out that Native Instruments is looking for a DevOps Engineer, I've decided that I can't just get past it. 
-
-### About me
-Hi! 
-
-I'm a DevOps engineer with almost five years of experience in different IT areas (QA, Development, System Engineering). Currently, I'm working at Itigris in the role of DevOps/System Engineer.  
-Some of my current responsibilities:
-- Support Kubernetes clusters. (all our applications and self-hosted services are running in Kubernetes)
-- Provide "Platform as a service" for developers and QA. For example,  create and support reliable and fast CI/CD pipelines, support and administrate self-hosted services, etc.
-- Help other teams with an understanding of Docker and containerization.
-- Troubleshooting and administrating
-
-### Why am I writing you? 
-
-Not so long ago, I've started to understand that it's important for me to feel that I'm working on something important and valuable. And all the projects at my current job don't make me feel like that. And I've started to think which job may make me give this filing. 
-Because of being a musician, I've decided that I should continue my DevOps way in the musical area. Native Instruments is a great audio software developing company, and it seems impossible to me not to send my CV.
-
-### Why, I think, you should pay attention to my CV?
-- I'm a young engineer with a will to learn.
-- I'm not afraid of non-standard solutions, and I'm not tied to old-familiar technologies.
-- I always take responsibility for what I'm doing.
-- I'm sure that things must be automated when it's possible.
-
-Thank you
-
-Nikolay Rodionov

cv/md/soundcloud/coverletter.md

@@ -1,27 +0,0 @@
-## Cover letter
-When I find out that SoundCloud is looking for a Production Engineer, I've decided that I can't just get past it. 
-
-### About me
-Hi! 
-
-I'm a DevOps engineer with almost five years of experience in different IT areas (QA, Development, System Engineering). Currently, I'm working at Itigris in the role of DevOps/System Engineer.  
-Some of my current responsibilities:
-- Support Kubernetes clusters. (all our applications and self-hosted services are running in Kubernetes)
-- Provide "Platform as a service" for developers and QA. For example,  create and support reliable and fast CI/CD pipelines, support and administrate self-hosted services, etc.
-- Help other teams with an understanding of Docker and containerization.
-- Troubleshooting and administrating
-
-### Why am I writing you? 
-After reading the job description, I've had a little doubt because I'm not sure that I can make a perfect fit right now. But it seems impossible to me not to try because I think SoundCloud is a great platform, and I will be happy to become a part of the team. I'm just tired of working on projects that don't make me feel satisfied, no matter how interesting tasks are. That's why I've decided to try. 
-
-SoundCloud is a platform that I'm using every day (as a listener and as a musician), and I believe that it's a kind of project that will make me feel that I'm working on something valuable. That's why I hope you will come back with feedback even if I'm not good enough to join the team right now. To help me understand which technologies I should learn deeper.
-
-### Why, I think, you should pay attention to my CV?
-- I'm a young engineer with a will to learn.
-- I'm not afraid of non-standard solutions, and I'm not tied to old-familiar technologies.
-- I always take responsibility for what I'm doing.
-- I'm sure that things must be automated when it's possible.
-
-Thank you
-
-Nikolay Rodionov

home-k8s/storage/local-storage.yaml

@@ -1,7 +0,0 @@
----
-apiVersion: storage.k8s.io/v1
-kind: StorageClass
-metadata:
-  name: local-storage
-provisioner: kubernetes.io/no-provisioner
-volumeBindingMode: WaitForFirstConsumer

lyrics/allanger/shotgun_shag.md

@@ -11,7 +11,7 @@ It's getting absolutely hollow outside.
 (It's getting absolutely hollow outside)
 
 When the fog circle is getting closed
-Leaving me the only option to pass through the house
+Leaving me with the only option. To pass through the house
 The little shotgun shack at the world's end
 The whole neighborhood is dead
 
@@ -33,13 +33,12 @@ It’s better outside
 It’s better outside 
 It’s better outside 
 It’s better out side
-
 Please pull me back
 Someone pull me back 
 Someone put me back 
-When or where I dindn’t have to 
+Where I dindn’t have to 
 Yell yell yell yell
-Just to be heard or to break through
+Just to to break through
 Swell swell swell swelling death bloom
 Recognize me no more
 I’ve fleed
@@ -56,9 +55,40 @@ And the little cloud of dust is escorting the creaking sound.
 Suddenly my eye got caught by a rotten peace of wood
 That used to be a handmade railing, I remember how I would
 Slide down while no one could see me cause it was already staggering
-But I couldn't veil the fact when the little woden bugger 
+But I couldn't veil that fact when the little woden bugger 
-Landed right between my hand and myself. I don't remember 
+Landed right between my hand and me. I don't remember 
 What was more scary to admit that I broke a hand or railing
 
+But I was such a gambler and I put all chips on the desk
+And since then I couldn't tell the barber's pole from my ass
+Burden was all on my breast, and I just wanted to get it past
+With this kind of baggage how you'd have nothing to confess
+
+Dear God. Why you've abandoned me, I'm not that much of sinner 
+I just fucking hate my pickneys and I wanna kill em
+
+A deep crunching noise is being emitted by the shards
+From a broken transom window. So the escape route's left behind
+
  
 
+It’s better outside 
+It’s better outside 
+It’s better outside 
+It’s better out side
+Please pull me back
+Someone pull me back 
+Someone put me back 
+Where I dindn’t have to 
+Yell yell yell yell
+Just to to break through
+Swell swell swell swelling death bloom
+Recognize me no more
+I’ve fleed
+At least I’ve tried
+Something’s pulling me 
+Something’s pulling me 
+Something’s pulling me 
+Something’s pulling me 
+Someones’s pushing me 
+I am so tired

lyrics/Для Коляна/Колян.md

@@ -1,3 +0,0 @@
-```
-Неказистой походкой красавец шагал молодой 
-``` 

todo.md

@@ -14,14 +14,14 @@
 
 # 04.07.2022
 - [x] LONG: Init Badhouseplants project
-- [ ] LONG: Update SSH key everywhere
+- [x] LONG: Update SSH key everywhere
   - Add to auth_keys
   - [x] Github
   - [x] Gitlab
   - [x] Etersoft Gunther
   - [x] Hetzner host
   - Update on my machines
-  - [ ] Windows
+  - [x] Windows
   - [x] Arch
   - [x] Working Personal
 
@@ -47,8 +47,9 @@
 # 04.17.2022
 - [ ] MEDIUM: Pass 2-3 units from German book
 - [ ] MEDIUM: Read the book
-- [ ] MEDIUM: Finish Shotgun Shag lyrics
+- [x] MEDIUM: Finish Shotgun Shag lyrics
-- [ ] MEDIUM: Clean up the notes repo
+- [x] MEDIUM: Clean up the notes repo
+
 # Further
 - [ ] MEDIUM: Cleanup GitHub
 - [ ] MEDIUM: Add firewall rules to Hetzner

vscode-notes/bodach.md

@@ -1,4 +0,0 @@
-# bodach 
-
-## bodach-daemon
-

vscode-notes/cpm.md

@@ -1,4 +0,0 @@
-# Bodach
-
-## bodach-boxes
-

vscode-notes/daily.md

@@ -1,22 +0,0 @@
-When creating a project you must be able to choose from 3 options (2 when from the browser)
-
-1. Create an empty DAW project. 
-There must be an empty project owned by the droplez user which is gonna be used as a template.
-For simplifying creating there must be a database table that will store empty projects object IDs.
-
-Example:
-
-| ID  | DAW           | Object ID |
-| --- | ------------- | --------- |
-| 1   | DAW_LOGIC_PRO | $UUID     |
-| 2   | DAW_ABLETON   | $UUID     |
-
-So, when creating an empty project, `droplez-studio` should go to `empty_projects` table and get object name. Then use this object as a file first for the first version
-
-2. Create a project from template 
-
-Project can be used as a template if it has a `template` flag.
-
-3. Create an empty droplez project. (Not working from the browser)
-
-Just init droplez config file in the specified folder. This should not be triggering a backend.

vscode-notes/droplez v0.1.0.md

@@ -1,23 +0,0 @@
-# droplez v0.1.0
-
-Release MVP
-
-Main client functions: 
-
-- Studio
-  - Projects 
-    - [ ] Project initialization
-      - droplez-frontend
-        - init empty project
-        - init empty DAW project (take the default project from the repo)
-        - init project from template
-      - droplez-desktop
-        - init empty project
-        - init empty DAW project
-        - init project from template
-      - droplez-cli
-        - init project in dir (like git or init with template)
-
-  - ProjectBoard
-  - Release 
-  - Templates

vscode-notes/droplez.md

@@ -1,91 +0,0 @@
-# droplez
-
-## MVP
-
-### droplez-frontend
-- Projects (Studio)
-  - Project initialization, listing, updating, commenting
-<!-- - Stock -->
-  <!-- - Sell beats -->
-  <!-- - Sell arrangements  -->
-  <!-- - Sell sounds  -->
-  <!-- - Sell vst presets -->
-<!-- - Plugins -->
-  <!-- - Donwload plugins  -->
-  <!-- - Save plugins to collection -->
-  <!-- - Attach presets to a plugin -->
-- Personal Page -> Auth service
-  - Post creation/listing/updating
-  - Reactions
-  - Music 
-  - Highligts
-- Player
-  - Timeline comments
-  - Lyrics
-### droplez-desktop
-- Project management (studio)
-- Player
-### droplez-cli
-- Project management (studio)
-
-Tasks: 
-1. 
-
-## Logic
-
-CLI: 
-```
-- Init project in the dir, where project file exists
-$ droplez init . 
-  -n | --name - project name
-  -a | --artist - artist name
-  -c | --collection - collection name
-  -t | --tags - project tags
-  droplez init creates a yaml file witt project params
-
-$ droplez add 
-  -m | --message - add message to new version
-
-$ droplez push 
-  
-```
-
-## Milestones
----
-
-### **milestone 1**: Project Initialization
-
-#### droplez-studio
-- [x] CRUD operations
-#### droplez-frontend
-- [ ] Studio -> Projects page
-#### droplez-cli 
-- [ ] Basic CRUD client
-#### droplez-k8s
-- [ ] Create deploy for stage environment
---- 
-
-### **milestone 2:** Files uploading and project versioning
-
-#### droplez-uploader
-- [ ] Init file uploader
-#### droplez-studio
-- [ ] Add information about files
-- [ ] Add versioning logic
-#### droplez-frontend
-- [ ] Add files uploading support 
-- [ ] Add versioning on project pages
-#### droplez-cli
-- [ ] File upload support
-
----
-
-## Notes
-
-### Project creation vs Project initialization
-
-- When creating a project, the new empty project instance is created (supported in Web, Desktop and Cli)
-- When initializing a project, droplez config is added to already existing project (Desktop, Cli)
-
-On init, we have a project dir, so we can add a yaml file there, but on create we need to unzip template, add config there and zip again. It should be done the fastest way possible. 
-

vscode-notes/migrations.md

@@ -1,30 +0,0 @@
-# migrations
-
-tables 
-
-actions_log
-
-id 
-action name
-action description
-action trigger
-
-db_lock
-
-db_name
-locked
-
-
-Once started applications send grpc message with the following information 
-```
-appVersion
-databaseStructure[] 
-  maps
-```
-
-
-1. App stated and send message to migrator 
-2. Migrator registered a new version in database actions_version and checks other versions
-3. Migrator checks db structure and triggers actions (actions are version based)
-4. 
-

vscode-notes/online performance platform.md

@@ -1,2 +0,0 @@
-# online performance platform
-

vscode-notes/деньги.md

@@ -1,3 +0,0 @@
-# деньги
-
-пришло