Alperen Doc

basic_git_conf

Mon, 01 Jan 0001 00:00:00 +0000

Git username & git email conf

git config --add --global user.name "github_username_here"
git config --add --global user.email "email@example.com"

Git github default branc

git config --global init.defaultBranch main

CLI ile login ol

gh auth login

docker-kurulum-hardening-debian

Mon, 01 Jan 0001 00:00:00 +0000

Debian 13 İçin Güvenli Docker ve Docker Compose Kurulum Dokümantasyonu#

1. Sistem Hazırlığı ve Bağımlılıklar#

Kuruluma başlamadan önce sistemin güncel olduğundan ve paketleri HTTPS üzerinden alabilmek için gerekli araçların yüklendiğinden emin oluyoruz.

sudo apt update && sudo apt upgrade -y
sudo apt install -y ca-certificates curl gnupg

2. Resmi Docker Deposu ve GPG Anahtarının Eklenmesi#

Paketlerin bütünlüğünü doğrulamak için Docker’ın resmi GPG anahtarını eklemek güvenlik açısından zorunludur.

GPG anahtarını indirip yapılandırıyoruz:

sudo install -m 0755 -d /etc/apt/keyrings
sudo rm -f /etc/apt/keyrings/docker.gpg
curl -fsSL https://download.docker.com/linux/debian/gpg | sudo gpg --dearmor -o /etc/apt/keyrings/docker.gpg
sudo chmod a+r /etc/apt/keyrings/docker.gpg

rm -f satırını ekledik çünkü anahtar daha önce indirilmişse gpg --dearmor -o komutu “File exists” hatası verir. Bu sayede komut güvenle tekrar çalıştırılabilir.

basic_git_knowledge

Mon, 01 Jan 0001 00:00:00 +0000

Simplified Git Commands Guide#

Initialize a Git Repository#

Navigate to the directory you want to track.
Run the following command:

git init

Adding Files or Directories#

To add files or directories to the staging area, use:

git add <file_or_directory_name>

git add

Checking the Current State#

To see the current state of your repository:

git status

git status

Committing Changes#

To save changes to the repository:

git commit -m "Your commit message"

git commit

Branch Management#

Creating and Switching to a New Branch#

Use the following command to create and switch to a new branch:

git switch -c my_new_branch

This is easier than using git branch followed by git switch. git branch

manage-docker-as-non-root-user

Mon, 01 Jan 0001 00:00:00 +0000

Manage Docker as a non-root user #

The Docker daemon binds to a Unix socket, not a TCP port. By default it’s the root user that owns the Unix socket, and other users can only access it using sudo. The Docker daemon always runs as the root user.

If you don’t want to preface the docker command with sudo, create a Unix group called docker and add users to it. When the Docker daemon starts, it creates a Unix socket accessible by members of the docker group. On some Linux distributions, the system automatically creates this group when installing Docker Engine using a package manager. In that case, there is no need for you to manually create the group.

docker-containers-images

Mon, 01 Jan 0001 00:00:00 +0000

Containers#

A container is a standard unit of software that packages up code and all its dependencies so the application runs quickly and reliably from one computing environment to another.

– Docker

Containers, on the other hand, gives us 90% of the benefits of virtual machines, but are super lightweight. Containers boot up in seconds, while virtual machines can take minutes.

Virtual Machine Architecture#

Container (Docker) Architectures#

github_workflow

Mon, 01 Jan 0001 00:00:00 +0000

001 - continuous_integration 002 - continuous_deployment

Hugo-Book Teması ve GitHub Actions(workflow) ile VPS’e CD#

Hugo,Markdown dosyalarını statik bir siteye dönüştüren bir araç. Bu yazıda, suan bulundugunuz siteyi nasil hugo-book temasını kullanırken aynı zamanda GitHub Workflow kullanarak her değişikliği debian tabanli uzak sunucuma nasıl otomatik olarak deploy edeceğimi anlatmak istedim.

1. VPS ve Kullanıcı Yapılandırması#

İlk başta sistemi --system parametresiyle kurmayı düşünmüştüm. Sistem kullanıcısı oluşturmak mantıklı çünkü bu kullanıcının varsayılan olarak bir şifresi ve interaktif bir shell oturumu olmaz (tabi belirli komutlarla yapilabilir). Bu da sunucunun guvenligini arttirir.

continuous_integration

Mon, 01 Jan 0001 00:00:00 +0000

Continuous Integration#

Continuous Integration (CI) is where developers regularly push code changes into a central repository, and by doing so, automated builds and tests are automatically run.

Those tests can include unit tests, integration tests, styling checks, linting checks, security checks or any other type of automated test. If any of the tests fail, the build is considered “broken” and the developer is notified so they can fix it.

I was forked boot.dev cli for testing CI at Boot.dev Cli#

Here at Boot.dev CI tests that run each time a new pull request is opened. The reviewer doesn’t need to manually check for formatting issues or run tests locally before approving the changes. It automates part of the code review process.

docker-volumes

Mon, 01 Jan 0001 00:00:00 +0000

Volumes#

By default, Docker containers don’t retain any state from past containers. For example, if I:

Start a container from an image
Make some changes to the filesystem (like installing a new package) in that container
Stop the container
Start a new container from the same image
The new container does not have the changes I made in step 2.

However, if I restart the stopped container, it will have the changes I made. This is only worth mentioning because sometimes developers think that killing an old container and starting a new one is the same as restarting a process - but that’s not true… it’s more like resetting the state of the entire machine to the original image.

continuous_deployment

Mon, 01 Jan 0001 00:00:00 +0000

Continuous Deployment (CD) is the process of automatically deploying code changes to a production environment after the code has been built and tested. Let’s set up CD for Notely!

We’ll be using GitHub Actions again, but we’ll create a new workflow for CD: cd.yml

How to create cd#

Create a new workflow .github/workflows/cd.yml
It should trigger on push into the main branch.

on:
 push:
 branches: [main]

It should have a single job called Deploy
It should checkout the code
It should set up the Go toolchain
It should build the app using the scripts/buildprod.sh script

To be clear, the ci workflow runs when a pull request is opened, but the cd workflow runs when a pull request is merged (or when code is pushed directly to the main branch).

docker-build

Mon, 01 Jan 0001 00:00:00 +0000

Dockerfiles#

Docker isn’t only useful for running other people’s software (as we’ve been doing so far). It’s also a great way to build and package our own software.

I’ve used Docker both ways. As a DevOps/platform engineer I’m usually using other’s images, but as a backend developer I was usually building images for our own servers.

Docker images are built from Dockerfiles. A Dockerfile is just a text file that contains all the commands needed to assemble an image. It’s essentially the “Infrastructure as Code” (IaC) for an image. It runs commands from top to bottom, kind of like a shell script.

optimize-container-images-with-multi-stage-builds

Mon, 01 Jan 0001 00:00:00 +0000

The problem with single-stage builds#

When you use the golang image to compile and run a Go application in the same stage, the final image inherits the entire Go compiler toolchain - over 800MB of packages and hundreds of CVEs that you don’t need at runtime.

Note: Single-stage Go builds keep the full compiler toolchain (~800MB+) in the final image even though only the compiled binary is needed at runtime.

docker-network

Mon, 01 Jan 0001 00:00:00 +0000

Docker-Network#

Offline#

Now, let’s force a container into offline mode!

You might be thinking, “why would I want to turn off networking?!?” Well, usually it’s for security reasons. You might want to remove the network connection from a container in one of these scenarios:

You’re running 3rd party code that you don’t trust, and it shouldn’t need network access
You’re building an e-learning site, and you’re allowing students to execute code on your machines
You know a container has a virus that’s sending malicious requests over the internet, and you want to do an audit

Network None#

The docker run command has a --network none flag that makes it so that the container can’t network with the outside world, which is super useful for isolating containers.

docker-exec-shell

Mon, 01 Jan 0001 00:00:00 +0000

Exec#

When it comes to deploying applications with Docker, you’ll usually just let the container do its thing. For example, the Ghost container we ran in the last chapter started up its own web server (based on the image configuration). We didn’t need to run any manual commands in addition to just starting the container.

That said, it is possible to run commands inside a running container! It’s kinda like the container version of sshing into a remote server and running a command.

docker-logs

Mon, 01 Jan 0001 00:00:00 +0000

Docker Logs#

When containers are running in detached mode with the -d flag, you don’t see any output in your terminal, which is nice for keeping your terminal clean, but what if something goes wrong?

Enter the docker logs command.

docker logs [OPTIONS] CONTAINER

Ornek log#

Let’s run the Linux alpine image in a new container in detached mode, and give it a simple command to run to generate some standard output:

docker run -d --name logdate alpine sh -c 'while true; do echo "LOGGING: $(date)"; sleep 1; done'

The sh -c 'while true; do echo "LOGGING: $(date)"; sleep 1; done' part is just a simple shell script to execute inside the container that prints the current date and time every second.

docker-compose-basic

Mon, 01 Jan 0001 00:00:00 +0000

docker compose ne isimize yariyor dersek, birden fazla konteyneri tek bir yaml dosyasindan yonetmemize yariyor, tek tek docker run ile ugrasmiyoruz ve ayni zamanda restart sayesinde sistem acilinca uygulamayi otomatik ayakta tutabiliyoruz

temel calisma mantigi#

proje klasorunde docker-compose.yml diye bir dosya aciyoruz, icine servisleri, networkleri ve volumeleri yazip sonra compose bunlari otomatik kurup birbirine bagliyor ve dayyum! uygulamalar ayakta oluyor, istegimize gore state’ini ayarlayabiliyoruz

ornek 1 - tier1 (docker-compose.yml)#

asagidaki ornekte bir nginx web sunucusu ve bir postgres veritabani var, en cok kullandigimiz temel seyler icinde.

git status

Mon, 01 Jan 0001 00:00:00 +0000

Status#

A file can be in one of several states in a Git repository. Here are a few important ones:

untracked: Not being tracked by Git
staged: Marked for inclusion in the next commit
committed: Saved to the repository’s history

The git status command shows you the current state of your repo. It will tell you which files are untracked, staged, and committed.

for more git branch

git add

Mon, 01 Jan 0001 00:00:00 +0000

git add#

Here’s the command:

git add <path-to-file | pattern>

For example:

git add i-use-arch.btw

var-olan-volume-uzerine-docker-compose

Mon, 01 Jan 0001 00:00:00 +0000

İlk olarak ben örnek olarak vereceğim#

kullanmak istediğim uygulama (filebrowser) kurulum yaparken admin kullanıcının yanında rastgele encrypted şifre oluşturuyor arka planda calisirken ve `docker logs` da baktigimdada parolayi goruntuleyemedigimden boyle bir yol izledim#

docker compose up -d # -d flag arka planda çalıştır demek

böyle yaptığımdan arka planda çalıştigindan parolayi olusturdu ama cikti olarak vermedi onuda olusturdugu persistent volume yazdi ama ben görmedim

docker compose up

bana şifreyi verecekti ama çoktan iş işten geçti :D şifreyi de hash’li olarak sakladığından dosyalara girsem bile fayda vermeyecekti

docker-publish

Mon, 01 Jan 0001 00:00:00 +0000

Publishing to Docker Hub#

Let’s publish the Go server we Dockerized up to Docker Hub.

Rebuild the Go binary:

GOOS=linux GOARCH=amd64 go build

Rebuild the image. You’ll need to use a name that corresponds to your namespace on Docker Hub. Swap out USERNAME for your Docker Hub username.

docker build . -t USERNAME/goserver

Run your image in a container to make sure it still works:

docker run -p 8991:8991 USERNAME/goserver

Push the image to Docker Hub:

docker push USERNAME/goserver

Delete and Pull#

Let’s delete our local copy of the image, then pull it back down from Docker Hub. Just like with GitHub, the nice thing about having images in the cloud is that if something happens to your computer, or you’re working on another machine, you can always pull down your images.

git commit

Mon, 01 Jan 0001 00:00:00 +0000

Commit#

After staging a file, we can commit it.

A commit is a snapshot of the repository at a given point in time. It’s a way to save the state of the repository, and it’s how Git keeps track of changes to the project. A commit comes with a message that describes the changes made in the commit.

Here’s how to commit all of your staged files:

git commit -m "your message here"

Change the last commit message#

git commit --amend -m "A: add contents.md"

docker-kurulum-hardening-rocky

Mon, 01 Jan 0001 00:00:00 +0000

Rocky Linux İçin Güvenli Docker ve Docker Compose Kurulum Dokümantasyonu#

1. Sistem Hazırlığı ve Bağımlılıklar#

Kuruluma başlamadan önce sistemin güncel olduğundan ve Docker deposunu yönetmemizi sağlayacak araçların yüklendiğinden emin oluyoruz.

sudo dnf update -y
sudo dnf install -y dnf-plugins-core

2. Resmi Docker Deposunun Eklenmesi#

Docker, Rocky için ayrı bir depo yayınlamıyor; RHEL türevleri için tek bir depo tutuyor ve bu depo CentOS olarak adlandırılıyor. Rocky’de de bu depoyu kullanıyoruz:

sudo dnf config-manager --add-repo https://download.docker.com/linux/centos/docker-ce.repo

Rocky 10’da paket yöneticisi dnf5’e geçti; orada komut biraz farklı: sudo dnf config-manager addrepo --from-repofile=https://download.docker.com/linux/centos/docker-ce.repo. Rocky 9’da (dnf4) yukarıdaki komut olduğu gibi çalışır.

git push

Mon, 01 Jan 0001 00:00:00 +0000

Git Push#

The git push command pushes (sends) local changes to any “remote” - in our case, GitHub. For example, to push our local main branch’s commits to the remote origin’s main branch we would run:

git push origin main

You need to be authenticated with the remote to push changes, which you should have done in the last lesson.

Alternative Options#

You can also push a local branch to a remote with a different name:

docker-distroless-container-images

Mon, 01 Jan 0001 00:00:00 +0000

Distroless Container Image’leri: İçlerinde Ne Var, Neden Kullanılır?#

1. Distroless Nedir, Neden Var?#

debian, ubuntu veya türevlerinden (node:lts, python:3 gibi) FROM ile başlayan container image’leri, genellikle dolu dolu bir Linux dağıtımıyla birlikte gelir. Gündelik işler için harikadır ama çoğu container uygulaması çalışma zamanında bu araçların ve kütüphanelerin neredeyse hiçbirine ihtiyaç duymaz. Sonuç? Teknik bir gerekçe olmaksızın daha büyük image boyutu ve yönetmesi gereken daha fazla güvenlik açığı (CVE).

Küçük, güvenli image’ler üretme isteği gayet doğal. Bunun en ekstrem yolu FROM scratch ile başlamaktır; yani boş bir base image’e sadece uygulamamızın gerçekten ihtiyaç duyduğu dosyaları eklemek. Ancak FROM scratch ile başlayan container’lar varsayılan olarak şunları içermez:

git branch

Mon, 01 Jan 0001 00:00:00 +0000

What Is a Branch?#

A Git branch allows you to keep track of different changes separately.

For example, let’s say you have a big web project and you want to experiment with changing the color scheme. Instead of changing the entire project directly (as of right now, our master branch), you can create a new branch called color_scheme and work on that branch. When you’re done, if you like the changes, you can merge the color_scheme branch back into the master branch to keep the changes. If you don’t like the changes, you can simply delete the color_scheme branch and go back to the master branch.

git pull

Mon, 01 Jan 0001 00:00:00 +0000

Pull#

Fetching is nice, but most of the time we want the actual file changes from a remote repo, not just the metadata.

Command Syntax#

git pull [<remote>/<branch>]

The [...] syntax means that the bracketed remote and branch are optional. If you execute git pull without anything specified it will pull your current branch from the remote repo.

git log

Mon, 01 Jan 0001 00:00:00 +0000

Git Log#

A Git repo is a (potentially very long) list of commits, where each commit represents the full state of the repository at a given point in time.

The git log command shows a history of the commits in a repository. This is what makes Git a version control system. You can see:

Who made a commit
When the commit was made
What was changed

A Commit Hash#

Each commit has a unique identifier called a “commit hash”. This is a long string of characters that uniquely identifies the commit. Here’s an example of mine:

git merge

Mon, 01 Jan 0001 00:00:00 +0000

Merge#

“What’s the point of having multiple branches?” you might ask. They’re most often used to safely make changes without affecting your (or your team’s) primary branch. However, once you’re happy with your changes, you’ll want to merge them back into the main branch so that they make their way into the final product.

Visual#

Let’s say you’re in a state where you have two branches, each with their own unique commits:

git rebase

Mon, 01 Jan 0001 00:00:00 +0000

Rebase#

“Rebase vs Merge” is one of the most hotly debated topics in the Git world. A lot of the discussions you’ll see online come down to the fact that many developers (yes, even professionals) don’t understand the purpose of rebase and use it incorrectly, causing a bunch of Git havoc, and then blame the rebase command.

It’s not Git’s fault, it’s a skill issue.

Visualizing Rebase#

Say we have this commit history:

git reset

Mon, 01 Jan 0001 00:00:00 +0000

Git Reset Soft#

The git reset command can be used to undo the last commit(s) or any changes in the index (staged but not committed changes) and the worktree (unstaged and not committed changes).

git reset --soft COMMITHASH

The --soft option is useful if you just want to go back to a previous commit, but keep all of your changes. Committed changes will be uncommitted and staged, while uncommitted changes will remain staged or unstaged as before.

git remote

Mon, 01 Jan 0001 00:00:00 +0000

Git Remote#

Often our frenemies (read: coworkers) make code changes that we need to begrudgingly accept into our pristine bug-free repos. /s

This is where the “distributed” in “distributed version control system” comes from. We can have “remotes”, which are just external repos with mostly the same Git history as our local repo.

When it comes to Git (the CLI tool), there really isn’t a “central” repo. GitHub is just someone else’s repo. Only by convention and convenience have we, as developers, started to use GitHub as a “source of truth” for our code.

git fetch

Mon, 01 Jan 0001 00:00:00 +0000

Fetch#

Adding a remote to our Git repo does not mean that we automagically have all the contents of the remote. First, we need to fetch the contents (but not yet!).

Command#

git fetch

This downloads copies of all the contents of the .git/objects directory (and other book-keeping information) from the remote repository into your current one.

git switch

Mon, 01 Jan 0001 00:00:00 +0000

New Branch#

You should already be on the main branch: your “default” branch. You can always check with git branch.

Two Ways to Create a Branch#

git branch my_new_branch

This creates a new branch called my_new_branch. The thing is, I rarely use this command because usually I want to create a branch and switch to it immediately. So I use this command instead:

git switch -c my_new_branch

The switch command allows you to switch branches, and the -c flag tells Git to create a new branch if it doesn’t already exist.

git config

Mon, 01 Jan 0001 00:00:00 +0000

We need to configure Git to contain your information. Whenever code changes, Git tracks who made the change. To ensure you get proper credit (or more likely, blame) for all the code you write, you need to set your name and email.

Git comes with a configuration both at the global and the repo (project) level. Most of the time, you’ll just use the global config.

Assignment#

Let’s set your identity. Check if your user.name and user.email are already set:

gitignore

Mon, 01 Jan 0001 00:00:00 +0000

Gitignore#

As you’ve seen, it’s pretty normal to use the following workflow from the top level of your repo:

git add .
git commit -m "some message here"
git push origin main

A problem arises when we want to put files in our project’s directory, but we don’t want to track them with Git. gitignore file solves this. For example, if you work with Python, you probably want to ignore automatically generated files like .pyc and __pycache__. If you are building a server, you probably want to ignore .env files that might hold private keys. If you (I’m sorry) work with JavaScript, you might want to ignore the node_modules directory.

plumping

Mon, 01 Jan 0001 00:00:00 +0000

The Plumbing#

So far we’ve been using Git in a “porcelain” manner. But to sate our insatiable curiosity, let’s take a look at some of the “plumbing”.

It’s Just Files All the Way Down#

All the data in a Git repository is stored directly in the (hidden) .git directory. That includes all the commits, branches, tags, and other objects we’ll learn about later.

Git is made up of objects that are stored in the .git/objects directory. A commit is just a type of object.

Alperen Doc

basic_git_conf

docker-kurulum-hardening-debian

Debian 13 İçin Güvenli Docker ve Docker Compose Kurulum Dokümantasyonu#

1. Sistem Hazırlığı ve Bağımlılıklar#

2. Resmi Docker Deposu ve GPG Anahtarının Eklenmesi#

basic_git_knowledge

Simplified Git Commands Guide#

Initialize a Git Repository#

Adding Files or Directories#

Checking the Current State#

Committing Changes#

Branch Management#

Creating and Switching to a New Branch#

manage-docker-as-non-root-user

Manage Docker as a non-root user#

docker-containers-images

Containers#

Virtual Machine Architecture#

Container (Docker) Architectures#

github_workflow

Hugo-Book Teması ve GitHub Actions(workflow) ile VPS’e CD#

1. VPS ve Kullanıcı Yapılandırması#

continuous_integration

Continuous Integration#

I was forked boot.dev cli for testing CI at Boot.dev Cli#

docker-volumes

Volumes#

continuous_deployment

How to create cd#

docker-build

Dockerfiles#

optimize-container-images-with-multi-stage-builds

The problem with single-stage builds#

docker-network

Docker-Network#

Offline#

Network None#

docker-exec-shell

Exec#

docker-logs

Docker Logs#

Ornek log#

docker-compose-basic

temel calisma mantigi#

ornek 1 - tier1 (docker-compose.yml)#

git status

Status#

git add

git add#

var-olan-volume-uzerine-docker-compose

İlk olarak ben örnek olarak vereceğim#

kullanmak istediğim uygulama (filebrowser) kurulum yaparken admin kullanıcının yanında rastgele encrypted şifre oluşturuyor arka planda calisirken ve docker logs da baktigimdada parolayi goruntuleyemedigimden boyle bir yol izledim#

docker-publish

Publishing to Docker Hub#

Delete and Pull#

git commit

Commit#

Change the last commit message#

docker-kurulum-hardening-rocky

Rocky Linux İçin Güvenli Docker ve Docker Compose Kurulum Dokümantasyonu#

1. Sistem Hazırlığı ve Bağımlılıklar#

2. Resmi Docker Deposunun Eklenmesi#

git push

Git Push#

Alternative Options#

docker-distroless-container-images

Distroless Container Image’leri: İçlerinde Ne Var, Neden Kullanılır?#

1. Distroless Nedir, Neden Var?#

git branch

What Is a Branch?#

git pull

Pull#

Command Syntax#

git log

Git Log#

A Commit Hash#

git merge

Merge#

Visual#

Manage Docker as a non-root user #

kullanmak istediğim uygulama (filebrowser) kurulum yaparken admin kullanıcının yanında rastgele encrypted şifre oluşturuyor arka planda calisirken ve `docker logs` da baktigimdada parolayi goruntuleyemedigimden boyle bir yol izledim#