<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Gizem Pesen on Medium]]></title>
        <description><![CDATA[Stories by Gizem Pesen on Medium]]></description>
        <link>https://medium.com/@pesengizem?source=rss-3bd1d26c68fc------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*8IUXtT_SgOqQOKBDGVAN7g.jpeg</url>
            <title>Stories by Gizem Pesen on Medium</title>
            <link>https://medium.com/@pesengizem?source=rss-3bd1d26c68fc------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 08:04:54 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@pesengizem/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Docker Multi-Stage Build?]]></title>
            <link>https://medium.com/@pesengizem/what-is-docker-multi-stage-build-825c4ca9e54e?source=rss-3bd1d26c68fc------2</link>
            <guid isPermaLink="false">https://medium.com/p/825c4ca9e54e</guid>
            <category><![CDATA[multi-stage-builds]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[devops-practice]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[dockerfiles]]></category>
            <dc:creator><![CDATA[Gizem Pesen]]></dc:creator>
            <pubDate>Tue, 22 Apr 2025 20:45:11 GMT</pubDate>
            <atom:updated>2025-04-22T20:46:26.928Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aqK2FVx7dA9_NNkjfCxdHw.png" /></figure><p>Docker Multi-Stage Build is a powerful feature that allows you to <strong>use multiple </strong><strong>FROM statements</strong> in your Dockerfile, copying artifacts from one stage to another. This enables you to separate build and runtime environments, which results in <strong>smaller, more secure, and efficient images</strong>.</p><h3>🧠 <strong>Why Use Multi-Stage Builds?</strong></h3><ul><li>✅ <strong>Smaller Image Size</strong>: Only include necessary runtime files.</li><li>✅ <strong>Better Security</strong>: Omit build tools and sensitive data.</li><li>✅ <strong>Cleaner Dockerfiles</strong>: No need for external scripts to clean up.</li><li>✅ <strong>Improved Performance</strong>: Lighter containers run faster.</li></ul><h3>🚀 <strong>How It Works</strong></h3><p>A Multi-Stage Dockerfile is composed of <strong>multiple stages</strong> (each starting with a FROM) and uses the COPY --from=&lt;stage&gt; command to transfer files between them.</p><p>You can <strong>name stages</strong> for clarity or refer to them by their index (0, 1, 2…)</p><p><strong>🧪 Example: Node.js App with NGINX</strong></p><p>Let’s say we have a React app built with Node.js and served with NGINX.</p><pre># Stage 1: Build the React app<br>FROM node:18 AS builder<br><br>WORKDIR /app<br>COPY package*.json ./<br>RUN npm install<br>COPY . .<br>RUN npm run build<br><br># Stage 2: Serve with NGINX<br>FROM nginx:stable-alpine<br><br>COPY --from=builder /app/build /usr/share/nginx/html<br><br>EXPOSE 80<br>CMD [&quot;nginx&quot;, &quot;-g&quot;, &quot;daemon off;&quot;]</pre><h4>What Happens Here?</h4><ol><li><strong>Builder Stage:</strong></li></ol><ul><li>Uses Node.js to install dependencies and build the app.</li><li>Contains all dev tools (Node, npm, source code).</li></ul><p>2. <strong>Final Stage</strong>:</p><ul><li>Based on lightweight nginx.</li><li>Copies only the production-ready build directory.</li><li>No Node.js, no source code.</li></ul><p><strong>⚙️ Best Practices</strong></p><ul><li><strong>Always use named stages</strong> (AS build, AS base) for readability.</li><li><strong>Split dependencies</strong> logically: e.g., base, builder, final.</li><li><strong>Use </strong><strong>.dockerignore</strong> to exclude unnecessary files.</li><li><strong>Don’t copy whole project</strong> if not needed (optimize COPY).</li><li><strong>Pin versions</strong> of base images for reproducibility.</li></ul><p>📉 Image Size Comparison</p><p>Traditional Method : ~800MB</p><p>Multi-Stage Method: ~100MB</p><p>✅ That’s an <strong>87.5% reduction</strong> just by not including build dependencies!</p><h3>🧰 Bonus: Advanced Multi-Stage Tips</h3><ul><li><strong>Caching dependencies</strong>: Split install commands to leverage Docker cache.</li><li><strong>Multiple copies</strong>: Use COPY --from=build1, --from=build2, etc.</li><li><strong>Conditionally copy assets</strong>: Use environment variables with ARG.</li></ul><h3>📚 Conclusion</h3><p>Docker Multi-Stage Builds are a <strong>best-practice solution</strong> for modern container development. By separating build and runtime logic, you get <strong>leaner, safer, and faster containers</strong> — perfect for CI/CD pipelines and production environments.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=825c4ca9e54e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Set Up Highly-available PostgreSQL Replication Cluster on Ubuntu 20.04]]></title>
            <link>https://medium.com/@pesengizem/set-up-highly-available-postgresql-replication-cluster-on-ubuntu-20-04-d3295eb2cd08?source=rss-3bd1d26c68fc------2</link>
            <guid isPermaLink="false">https://medium.com/p/d3295eb2cd08</guid>
            <category><![CDATA[ubuntu]]></category>
            <category><![CDATA[ubuntu-20-04]]></category>
            <category><![CDATA[postgresql]]></category>
            <category><![CDATA[postgres]]></category>
            <category><![CDATA[cluster]]></category>
            <dc:creator><![CDATA[Gizem Pesen]]></dc:creator>
            <pubDate>Tue, 19 Dec 2023 14:39:34 GMT</pubDate>
            <atom:updated>2023-12-19T14:39:34.678Z</atom:updated>
            <content:encoded><![CDATA[<p>Here are the general steps for setting up a PostgreSQL cluster for high availability on Ubuntu 20.04 using PostgreSQL</p><h4>Prerequisites</h4><ul><li>server-1: Master 10.106.0.1</li><li>server-2: Replica-1 10.106.0.2</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FNKCFW5T064aPBbFemC6tQ.png" /></figure><h4>Start by installing PostgreSQL on your servers:</h4><pre>sudo apt update<br>sudo apt install postgresql postgresql-contrib</pre><h4>2. Configure the Master Node:</h4><p>Log in to the PostgreSQL database server as postgres user. This is the default super-user account</p><pre> $  sudo -u postgres psql</pre><p>Enter the password for the postgres user and press ENTER to proceed. Next, issue the CREATE ROLE command below to set up a dedicated repl_user account with REPLICATION privileges. Replace EXAMPLE_PASSWORD with a strong value. Later, your replica node will use the credentials of the repl_user to connect to the master node to fetch replication data.</p><pre> postgres-# CREATE ROLE repl_user WITH REPLICATION LOGIN PASSWORD &#39;EXAMPLE_PASSWORD&#39;;</pre><p>Output.</p><p>CREATE ROLE</p><p>Log out from the PostgreSQL database.</p><pre> postgres-# \q</pre><p>Next, use nano to open the default PostgreSQL configuration file.</p><pre> $ sudo nano /etc/postgresql/12/main/postgresql.conf</pre><p>With the above file open, locate the listen_addresses directive. This setting allows you to specify the interface under which the server listens for connections. For this setup, you want the database server to listen on the private IP address interface.</p><pre> ...<br><br> #listen_addresses = &#39;localhost&#39; ... # what IP address(es) to listen on;<br><br> ...</pre><p>Uncomment the line above by removing the pound # symbol at the beginning. Then replace localhost with your master server&#39;s private IP address(For example, 10.106.0.1).</p><pre> listen_addresses = &#39;10.106.0.1&#39;</pre><p>Next locate wal_level. This setting determines how much information is written to the Write Ahead Log(WAL) file.</p><pre> ...<br><br> #wal_level = replica ... # minimal, replica, or logical<br><br> ...</pre><p>Uncomment the line and change the value from replica to logical. This enables PostgreSQL streaming replication.</p><pre> ...<br><br> wal_level = logical<br><br> ...</pre><p>Next, find the wal_log_hints directive. By default, this value is off.</p><pre> ...<br><br> #wal_log_hints = off ... # also do full page writes of non-critical updates<br><br> ...</pre><p>Enable the wal_log_hints setting by removing the # symbol and changing its value to on. This allows the PostgreSQL server to write the entire content of each disk page to the WAL file. This helps in the recovery process in case the standby node goes out of sync with the master server.</p><pre> ...<br><br> wal_log_hints = on<br><br> ...</pre><p>Save and close the /etc/postgresql/12/main/postgresql.conf file when you&#39;re through with editing.</p><p>Next, you’ll make a few changes to the /etc/postgresql/12/main/pg_hba.conf file still under the master node. In this file, you will include the IP address of the replica node so that it can connect to the master node. Open the /etc/postgresql/12/main/pg_hba.conf file using nano for editing purposes.</p><pre> $ sudo nano /etc/postgresql/12/main/pg_hba.conf</pre><p>Next, append the entries below at the bottom of the file to allow your replica node(10.106.0.2) to connect to the master under the repl_user account.</p><pre> host    replication     repl_user       10.106.0.2/32           md5</pre><p>Save and close the /etc/postgresql/12/main/pg_hba.conf file. Then, restart the PostgreSQL server on the master node to apply the new changes.</p><pre>sudo systemctl restart postgresql</pre><p>You’ve now set up your master server and you can now connect a standby server to start replicating data in real-time.</p><h4>2. Configure the Replica Node:</h4><p>The replica server(10.106.0.2) needs to start somewhere before it can start replicating data from the master. The best way to initialize or bootstrap the replica server is by copying over the master server&#39;s data files using the pg_basebackup utility. SSH to the replica server and follow the process below to create a base copy of the master server&#39;s data.</p><p>Ensure the PostgreSQL server is not running on the replica server by stopping the postgresql service.</p><pre> $ sudo systemctl stop postgresql</pre><p>Still on the replica server, use the Linux rm command to remove all the files in the PostgreSQL data directory /var/lib/postgresql/12/main/</p><pre> $ sudo rm -rv /var/lib/postgresql/12/main/</pre><p>Next, run the pg_basebackup on the replica server to copy data from the master server using the following options.</p><pre> $ sudo pg_basebackup -h 10.106.0.1 -U repl_user -X stream -C -S replica_1 -v -R -W -D /var/lib/postgresql/12/main/</pre><p>The pg_basebackup options explained:</p><ul><li>-h: You’re using this option to specify the host. In this case, this is the private IP address of the master node(10.106.0.1) where you want to fetch the backup data from.</li><li>-U: This option allows you to specify the replication user account(repl_user) which you created on the master node.</li><li>-D: This option allows you to include the directory under which you want to export the backup files. In this case, you’re placing the data under the /var/lib/postgresql/12/main/ in the replica node.</li><li>-X: This option together with a value of stream allows you to instruct the pg_basebackup utility to stream and include the WAL files in the backup.</li><li>-C: This allows you to create a replication slot before starting the backup. You’ve named the slot replica_1 by including it after the -S option which specifies the replication slot name.</li><li>-v: This enables verbose mode in order to output the progress of the backup process.</li><li>-R: This allows you to create a recovery configuration file and a master node connection settings file under the data directory. You’ll find these files named standby.signal and postgresql.auto.conf.</li><li>-W: This option prompts you to enter a password for the repl_user user.</li></ul><p>Once you’ve pulled the database files from the master server using the pg_basebackup utility, you should get the following output.</p><pre>pg_basebackup: initiating base backup, waiting for checkpoint to complete<br> pg_basebackup: checkpoint completed<br> pg_basebackup: write-ahead log start point: 0/2000028 on timeline 1<br> pg_basebackup: starting background WAL receiver<br> pg_basebackup: created replication slot &quot;replica_1&quot;<br> pg_basebackup: write-ahead log end point: 0/2000100<br> pg_basebackup: waiting for background process to finish streaming ...<br> pg_basebackup: syncing data to disk ...<br> pg_basebackup: base backup completed</pre><p>Next, run the following command on your replica node to ensure, the data files are correctly owned by the postgres user.</p><pre>$ sudo chown postgres -R /var/lib/postgresql/12/main/</pre><p>You now have the correct data files in your replica node, you can now bring it up as a hot standby node.</p><pre>$ sudo systemctl start postgresql</pre><h4>4. Test the PostgreSQL Replication</h4><p>In this step, you’ll connect to the PostgreSQL database server on the master node, create a database, a table, and insert some records. Then, you’ll connect to the replica node to check whether the database will be replicated. Use different SSH sessions for the master and replica in this step to avoid confusion.</p><p>Log in to the PostgreSQL server on the master node.</p><pre> $ sudo -u postgres psql</pre><p>Enter your postgres password and press ENTER to proceed. Next, create a test_db by running the following command.</p><pre> postgres=# CREATE DATABASE test_db;</pre><p>Then, switch to the new database.</p><pre> postgres=# \c test_db;</pre><p>Output.You are now conneted to database &quot;test_db&quot; as user &quot;postgres&quot;.</p><pre>You are now connected to database &quot;test_db&quot; as user &quot;postgres&quot;.</pre><p>Create a new products table under the test_db database.</p><pre>test_db-# CREATE TABLE products (<br>               product_id SERIAL PRIMARY KEY,<br>               product_name VARCHAR (50)<br>           );</pre><p>Output.</p><pre>CREATE TABLE</pre><p>Next, INSERT three records in the products table.</p><pre>test_db=# INSERT INTO products(product_name) VALUES (&#39;LEATHER JACKET&#39;);<br>           INSERT INTO products(product_name) VALUES (&#39;WINTER HOODIE&#39;);<br>           INSERT INTO products(product_name) VALUES (&#39;BROWN WALLET&#39;);</pre><p>Output.</p><pre>INSERT 0 1<br> ...</pre><p>Now in a new SSH terminal window, connect to the PostgreSQL server on the replica node as postgres.</p><pre>$ sudo -u postgres psql</pre><p>Enter the password for the postgres user and press ENTER to proceed. Next, attempt switching to the test_db.</p><pre>postgres=# \c test_db;</pre><p>You’ll get the following confirmation message.</p><pre>You are now connected to database &quot;test_db&quot; as user &quot;postgres&quot;.</pre><p>Still on the replica node, query the products table.</p><pre>test_db=# SELECT <br>               product_id,<br>               product_name<br>           FROM products;</pre><p>You should now get the records that you inserted in the products table via the master node.</p><pre>product_id |  product_name<br> ------------+----------------<br>           1 | LEATHER JACKET<br>           2 | WINTER HOODIE<br>           3 | BROWN WALLET<br> (3 rows)</pre><p>Your replica node is running in hot standby mode and can only accept read-only operations. You may attempt to submit the following INSERT statement in the replica node to check this behavior.</p><pre>test_db=# INSERT INTO products(product_name) VALUES (&#39;RED TSHIRT&#39;);</pre><p>Since the replica node can not accept write operations, you should get the following error. However, the same command will succeed in the master node.</p><pre>ERROR:  cannot execute INSERT in a read-only transaction</pre><p>Your PostgreSQL replication setup is now working as expected.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d3295eb2cd08" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Docker Compose offline set up that does not have internet Ubuntu 20.04]]></title>
            <link>https://medium.com/@pesengizem/docker-compose-offile-set-up-that-does-not-have-internet-676e997b323b?source=rss-3bd1d26c68fc------2</link>
            <guid isPermaLink="false">https://medium.com/p/676e997b323b</guid>
            <category><![CDATA[offline]]></category>
            <category><![CDATA[docker-compose]]></category>
            <category><![CDATA[ubuntu-20-04]]></category>
            <dc:creator><![CDATA[Gizem Pesen]]></dc:creator>
            <pubDate>Wed, 19 Jul 2023 12:00:41 GMT</pubDate>
            <atom:updated>2023-12-20T14:03:33.399Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RBIQhTrezjrlKcqtDQ6vDg.png" /></figure><p>First, let’s pull the docker-compose package on a computer with internet and send it to our system that does not have internet.</p><pre>wget https://github.com/docker/compose/releases/download/v2.19.1/docker-compose-linux-x86_64</pre><p>Let’s rename it to docker-compose</p><pre>mv docker-compose-Linux-x86_64 docker-compose</pre><p>Move it to /usr/local/bin and make executable</p><pre>sudo mv docker-compose /usr/local/bin/<br>sudo chmod +x /usr/local/bin/docker-compose</pre><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=676e997b323b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Rancher K3s Set Up]]></title>
            <link>https://medium.com/@pesengizem/rancher-k3s-set-up-8f06707f0c72?source=rss-3bd1d26c68fc------2</link>
            <guid isPermaLink="false">https://medium.com/p/8f06707f0c72</guid>
            <dc:creator><![CDATA[Gizem Pesen]]></dc:creator>
            <pubDate>Mon, 12 Jun 2023 12:39:55 GMT</pubDate>
            <atom:updated>2023-07-19T11:44:29.095Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/264/1*yB8E0QbfNAucrisZHPm7yg.png" /></figure><p>Requirements:</p><ul><li>Docker Vm</li><li>Master Vm</li><li>Worker01 Vm</li><li>Worker02 Vm</li></ul><p>Docker Vm:</p><pre>curl https://releases.rancher.com/install-docker/20.10.sh | sh</pre><p>Note:</p><pre>apt-cache madison docker-ce<br>sudo apt-get install docker-ce=$VERSION_STRING docker-ce-cli=$VERSION_STRING containerd.io docker-buildx-plugin docker-compose-plugin</pre><p>Docker Compose Rancher Set Up</p><p>Rancher UI:</p><p>Cluster Management → Clusters → Create Cluster → RKE1 → Custom</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8f06707f0c72" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Kafka ve Zookeeper Docker Compose Set Up]]></title>
            <link>https://medium.com/@pesengizem/kafka-ve-zookeeper-docker-compose-set-up-feb9bfd74a0f?source=rss-3bd1d26c68fc------2</link>
            <guid isPermaLink="false">https://medium.com/p/feb9bfd74a0f</guid>
            <category><![CDATA[kafka]]></category>
            <category><![CDATA[docker-compose]]></category>
            <category><![CDATA[zookeeper]]></category>
            <dc:creator><![CDATA[Gizem Pesen]]></dc:creator>
            <pubDate>Mon, 12 Jun 2023 12:11:24 GMT</pubDate>
            <atom:updated>2023-12-26T13:27:36.893Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/363/1*8ZoktoOkpTNHmQ2Zx2hfGw.png" /></figure><p>In this configuration, we have two services defined: zookeeper and kafka. The zookeeper service uses the confluentinc/cp-zookeeper Docker image, and the kafka service uses the confluentinc/cp-kafka Docker image.</p><pre>version: &#39;3&#39;<br>services:<br>  zookeeper:<br>    image: confluentinc/cp-zookeeper:6.0.0<br>    container_name: zookeeper<br>    ports:<br>      - &quot;2181:2181&quot;<br>    environment:<br>      - ZOOKEEPER_CLIENT_PORT=2181<br>      - ZOOKEEPER_TICK_TIME=2000<br><br>  kafka:<br>    image: confluentinc/cp-kafka:6.0.0<br>    container_name: kafka<br>    ports:<br>      - &quot;9092:9092&quot;<br>    environment:<br>      - KAFKA_BROKER_ID=1<br>      - KAFKA_ZOOKEEPER_CONNECT=zookeeper:2181<br>      - KAFKA_ADVERTISED_LISTENERS=PLAINTEXT://kafka:9092<br>      - KAFKA_OFFSETS_TOPIC_REPLICATION_FACTOR=1<br>    depends_on:<br>      - zookeeper</pre><p>The zookeeper service exposes port 2181, which is the default port for ZooKeeper. The kafka service exposes port 9092, which is the default port for Kafka.</p><p>The environment variables set for the zookeeper service specify the client port and tick time for ZooKeeper.</p><p>The environment variables set for the kafka service include the broker ID, the ZooKeeper connection string, the advertised listeners, and the replication factor for the offsets topic.</p><p>The kafka service depends on the zookeeper service, so ZooKeeper will be started before Kafka.</p><p>To run this Docker Compose configuration, save it to a file named docker-compose.yml, navigate to the directory containing the file in the terminal, and run the following command:</p><pre>docker-compose up -d</pre><p>This will start the Kafka and ZooKeeper containers in the background. You can then interact with Kafka using the advertised listener PLAINTEXT://localhost:9092 or PLAINTEXT://kafka:9092 if you are connecting from within another container on the same Docker network.</p><p>Remember to adjust the image versions in the image field according to your requirements. Additionally, you can modify other parameters and add more services as needed for your specific use case.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=feb9bfd74a0f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Zookeper Kurulumu Ubuntu 20.04]]></title>
            <link>https://medium.com/@pesengizem/zookeper-kurulumu-ubuntu-20-04-1e93ecb0ad3f?source=rss-3bd1d26c68fc------2</link>
            <guid isPermaLink="false">https://medium.com/p/1e93ecb0ad3f</guid>
            <category><![CDATA[ubuntu-server]]></category>
            <category><![CDATA[ubuntu]]></category>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[zookeeper]]></category>
            <dc:creator><![CDATA[Gizem Pesen]]></dc:creator>
            <pubDate>Wed, 22 Mar 2023 12:02:47 GMT</pubDate>
            <atom:updated>2023-03-22T12:02:47.095Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/318/1*lRmCV1hkyISTbcJIpzH35g.png" /></figure><p>Zookeeper, büyük ölçekli dağıtık sistemlerin yönetimini kolaylaştıran bir açık kaynaklı yazılım projesidir. Bu sistemlerde, birden fazla bilgisayar ve sunucu birlikte çalışarak belirli bir amaca hizmet ederler. Örnek olarak, bir web uygulaması birden fazla sunucu üzerinde çalışabilir veya bir veritabanı birden fazla sunucu aracılığıyla dağıtık olarak kullanılabilir.</p><p>Zookeeper, bu tür sistemlerdeki koordinasyon ve senkronizasyon görevlerini yönetmek için tasarlanmıştır. Bu görevler arasında, lider seçimi, blokaj yönetimi ve yapılandırma yönetimi gibi işlemler yer alır. Zookeeper, bu görevleri gerçekleştirmek için düğümler arasında bir hiyerarşik yapı kullanır ve bu yapı üzerinde işlemler gerçekleştirir.</p><p>Zookeeper’ın en önemli özelliklerinden biri, yüksek güvenilirlik ve dayanıklılıktır. Sistem, birincil düğümün arızalanması durumunda bile hizmet vermeye devam edebilir. Bu özellik, büyük ölçekli sistemlerin kesintisiz çalışması için kritik bir gerekliliktir.</p><p>Zookeeper, özellikle büyük ölçekli uygulamalar için kullanılan Apache Hadoop, Apache Kafka ve Apache Storm gibi açık kaynaklı projelerde yaygın olarak kullanılmaktadır. Bu projeler, birçok düğümün bir araya geldiği ve koordinasyonun önemli olduğu büyük ölçekli uygulamaları içermektedir.</p><p>Sonuç olarak, Zookeeper büyük ölçekli dağıtık sistemlerin yönetimini kolaylaştıran güçlü bir araçtır. Bu sistemlerdeki koordinasyon ve senkronizasyon görevlerini yönetmek için tasarlanmıştır ve yüksek güvenilirlik ve dayanıklılık sağlar. Bu nedenle, büyük ölçekli uygulamalar için vazgeçilmez bir araçtır.</p><p><strong>Zookeeper’ın Ubuntu 20.04 üzerinde kurulumu için şu adımları izleyebilirsiniz:</strong></p><ol><li>İlk olarak, Ubuntu 20.04 üzerinde güncelleme yapın:</li></ol><pre>sudo apt update<br>sudo apt upgrade</pre><p>2. Java yükleyin:</p><pre>sudo apt install openjdk-8-jdk</pre><p>3. Zookeeper paketini indirin:</p><pre>wget https://downloads.apache.org/zookeeper/zookeeper-3.7.0/apache-zookeeper-3.7.0-bin.tar.gz</pre><p>4. İndirilen paketi çıkarın:</p><pre>tar -xvf apache-zookeeper-3.7.0-bin.tar.gz</pre><p>5. Zookeeper’ın çalışacağı dizini oluşturun:</p><pre>sudo mkdir /var/lib/zookeeper</pre><p>6. Zookeeper yapılandırma dosyasını düzenleyin:</p><pre>cp apache-zookeeper-3.7.0-bin/conf/zoo_sample.cfg apache-zookeeper-3.7.0-bin/conf/zoo.cfg<br>sudo nano apache-zookeeper-3.7.0-bin/conf/zoo.cfg</pre><p>Bu adımda, zoo.cfg dosyasını düzenleyerek yapılandırmayı yapılandırabilirsiniz. Dosyayı açtıktan sonra, örneğin, “dataDir=/var/lib/zookeeper” satırını ekleyebilirsiniz.</p><p>7. Zookeeper’ı başlatın:</p><pre>apache-zookeeper-3.7.0-bin/bin/zkServer.sh start</pre><p>8. Durumunu kontrol edin:</p><pre>apache-zookeeper-3.7.0-bin/bin/zkServer.sh status</pre><p>Çıktıda “Mode: standalone” görmelisiniz.</p><p>Artık Zookeeper başarıyla kuruldu ve çalışıyor. Bu adımların ardından, Zookeeper’ı farklı bir düğümde veya kümede çalıştırmak isterseniz, yapılandırma dosyasını düzenleyebilirsiniz.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1e93ecb0ad3f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Zimbra Kurulumu Ubuntu 20.04]]></title>
            <link>https://medium.com/@pesengizem/zimbra-kurulumu-ubuntu-20-04-10dfd3dfd997?source=rss-3bd1d26c68fc------2</link>
            <guid isPermaLink="false">https://medium.com/p/10dfd3dfd997</guid>
            <category><![CDATA[mail-server]]></category>
            <category><![CDATA[zimbra]]></category>
            <category><![CDATA[mail]]></category>
            <dc:creator><![CDATA[Gizem Pesen]]></dc:creator>
            <pubDate>Sun, 19 Mar 2023 22:55:42 GMT</pubDate>
            <atom:updated>2023-03-19T22:55:42.687Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/732/1*-lzf4mG3QsL1yww12IAWtw.png" /></figure><p>Zimbra, özellikle işletmeler için tasarlanmış bir e-posta ve işbirliği yazılımıdır. Bu yazılım, birden çok kullanıcının, e-posta, takvim, adres defteri, dosya paylaşımı ve diğer iletişim işlevlerini tek bir platformda yönetmelerini sağlar. Bu makalede, Ubuntu 20.04 üzerine Zimbra’nın nasıl kurulacağını anlatacağım.</p><p>Ön Gereksinimler</p><ul><li>Ubuntu 20.04 sunucusu</li><li>SSH istemcisi</li><li>4 GB RAM (minimum)</li><li>10 GB boş disk alanı (minimum)</li></ul><p>Kurulum Adımları</p><ol><li>Güncellemeleri Yapın</li></ol><p>Ubuntu sunucunuzu güncelleyin ve tüm güncellemeleri yükleyin.</p><pre>sudo apt update<br>sudo apt upgrade</pre><p>2. Hostname Ayarlarını Yapın</p><p>Ubuntu sunucunuzun hostname ayarlarını doğru şekilde yapın. Örneğin, hostname “mail.example.com” olabilir. Aşağıdaki komutu kullanarak hostname ayarlarınızı kontrol edebilirsiniz:</p><pre>hostnamectl</pre><p>3. Gerekli Paketleri Yükleyin</p><p>Zimbra’nın kurulumu için gerekli olan bazı paketleri yükleyin:</p><pre>sudo apt install libaio1 pax sysstat sqlite3</pre><p>4. Zimbra Paketini İndirin</p><p>Zimbra’nın son sürümünü indirin ve /opt dizinine çıkarın:</p><pre>wget https://files.zimbra.com/downloads/8.8.15_GA/zcs-8.8.15_GA_3869.UBUNTU20_64.20200828191956.tgz<br>sudo tar xvzf zcs-8.8.15_GA_3869.UBUNTU20_64.20200828191956.tgz -C /opt/</pre><p>5. Zimbra’yı Kurun</p><p>Zimbra kurulumunu başlatmak için aşağıdaki komutu kullanın:</p><pre>cd /opt/zcs-8.8.15_GA_3869.UBUNTU20_64.20200828191956/<br>sudo ./install.sh</pre><p>Kurulum sırasında, Zimbra’nın kurulum ayarlarını yapabilirsiniz. Kurulumda seçenekler sunulacaktır, ancak varsayılan ayarları kullanmak isteyebilirsiniz.</p><p>6. Zimbra’yı Başlatın</p><p>Kurulum tamamlandıktan sonra, Zimbra’yı başlatmak için aşağıdaki komutları kullanın:</p><pre>sudo systemctl start zimbra</pre><p>7. Zimbra’yı Kontrol Edin</p><p>Zimbra’nın doğru şekilde çalıştığını kontrol etmek için aşağıdaki komutları kullanın:</p><pre>sudo su - zimbra<br>zmcontrol status</pre><p>Eğer Zimbra doğru şekilde çalışıyorsa, aşağıdaki gibi bir çıktı almalısınız:</p><pre>Host mail.example.com<br>        antispam                Running<br>        antivirus               Running</pre><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=10dfd3dfd997" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Nodejs Offline Set Up On Ubuntu 20.04]]></title>
            <link>https://medium.com/@pesengizem/nodejs-offline-set-up-on-ubuntu-20-04-31bc79d96114?source=rss-3bd1d26c68fc------2</link>
            <guid isPermaLink="false">https://medium.com/p/31bc79d96114</guid>
            <category><![CDATA[nodejs]]></category>
            <category><![CDATA[offline]]></category>
            <category><![CDATA[offlineserver]]></category>
            <category><![CDATA[ubuntu]]></category>
            <category><![CDATA[npm]]></category>
            <dc:creator><![CDATA[Gizem Pesen]]></dc:creator>
            <pubDate>Thu, 23 Feb 2023 19:29:53 GMT</pubDate>
            <atom:updated>2023-02-23T19:29:53.285Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*y5YLuOKO5XM7MOzve6XsDQ.png" /></figure><p>For some security-requiring jobs, we may need to install offline.</p><p>In this article, I will show you set up nodejs npm package on offline server.</p><p><strong>Step 1</strong></p><p>Firstly, it should be downloaded the nodejs on a machine has internet connection.</p><p>It can be download on this link;</p><p><a href="https://nodejs.org/en/download/current/">Download | Node.js</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a-sBPjV4NulHHL-36Mxb0w.png" /></figure><p>It can be download linux binaries(x64) current version.</p><p><strong>Step 2</strong></p><p>After download the tar, take it with Usb and send to the offline virtual machine .</p><pre>scp [file_name] remote_user@host:[destination_folder]<br>//example ---&gt; scp node-v14.15.5.tar.xz ubuntu@10.150.1.128:/root</pre><pre>tar -xvf &lt;your_tar&gt;<br>//example --&gt; sudo tar -xvf node-v14.15.5-linux-x64.tar.xz</pre><p><strong>Step 3</strong></p><p>Then cp the extracted tar to /usr/ folder</p><pre> sudo cp -r directory_name/{bin,include,lib,share} /usr/<br>//example ---&gt; sudo cp -r node-v14.15.5-linux-x64/{bin,include,lib,share} /usr/</pre><p><strong>Step 4</strong></p><p>Update the path</p><pre>export PATH=/usr/node_directory_name/bin:$PATH<br>//example --&gt;export PATH=/usr/node-v14.15.5-linux-x64/bin:$PATH</pre><p><strong>Step 5</strong></p><p>Check the node and npm version</p><pre>node --version<br>npm --version</pre><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=31bc79d96114" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Self-signed Certificate with Ngnix Proxy Manager]]></title>
            <link>https://medium.com/@pesengizem/self-signed-certificate-with-ngnix-proxy-manager-266a6fbd9df9?source=rss-3bd1d26c68fc------2</link>
            <guid isPermaLink="false">https://medium.com/p/266a6fbd9df9</guid>
            <category><![CDATA[https]]></category>
            <category><![CDATA[self-signed-certificate]]></category>
            <category><![CDATA[nginx-proxy]]></category>
            <category><![CDATA[nginx]]></category>
            <category><![CDATA[ssl-certificate]]></category>
            <dc:creator><![CDATA[Gizem Pesen]]></dc:creator>
            <pubDate>Sun, 18 Dec 2022 19:41:03 GMT</pubDate>
            <atom:updated>2023-02-23T18:14:54.640Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*88tOIDPe2FDBTU-1.png" /></figure><p>In this article I will show you to create a free self-signed certificate in very very easy way.</p><p>Requirements;</p><ul><li>domain ; example.com</li><li>a ubuntu server with public ip;</li></ul><p>Step-0: Connect your remote device</p><p>if you have key-pair;</p><pre>ssh -i &lt;pem file&gt; &lt;user&gt;@&lt;ip&gt; <br><br>Example: ssh -i gizem.pem ubuntu@192.168.246.1</pre><p>if you have password;</p><pre>ssh ubuntu@192.168.246.1</pre><p>Step-1 : Install Docker and Docker Compose</p><pre>sudo apt install docker.io<br>sudo apt install docker-compose</pre><p>Step-2: Create a docker-compose file</p><pre>nano docker-compose.yml</pre><pre>version: &#39;3&#39;<br>services:<br>  app: <br>    image: &#39;jc21/nginx-proxy-manager:latest&#39;<br>    container_name: nginx-proxy-manager<br>    ports:<br>      - &#39;80:80&#39;<br>      - &#39;81:81&#39;<br>      - &#39;443:443&#39;</pre><p>It listens 80, 81, and 443 ports. and pull the jc21/nginx-proxy-manager:latest docker image.</p><p>Step-3: Run docker-compose file</p><pre>sudo docker-compose up -d</pre><p>Then you can reach Ngnix Proxy server on http://&lt;your-ip&gt;:81 port</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JqoXCTAUuyMJAtRW_7VIXA.png" /></figure><p>Default Email : admin.example.com</p><p>Default Password: changeme</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1012/1*7xR_984sUWG8vHNihOy-lg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1012/1*5tJwuoksay63BHk_yqNsZg.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=266a6fbd9df9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[CI/CD Nedir?]]></title>
            <link>https://medium.com/@pesengizem/ci-cd-nedir-b640fd9b345f?source=rss-3bd1d26c68fc------2</link>
            <guid isPermaLink="false">https://medium.com/p/b640fd9b345f</guid>
            <category><![CDATA[gitlab]]></category>
            <category><![CDATA[ci-cd-pipeline]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[teamcity]]></category>
            <category><![CDATA[jenkins]]></category>
            <dc:creator><![CDATA[Gizem Pesen]]></dc:creator>
            <pubDate>Sat, 13 Aug 2022 20:34:21 GMT</pubDate>
            <atom:updated>2022-08-13T20:34:21.146Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QOtbfHQKYpTHZXm3OLgWhQ.png" /></figure><p>Sürekli entegrasyon (Continuous Integration, <strong>CI</strong>) ve sürekli teslim (Continuous Delivery, <strong>CD</strong>), uygulama geliştirme ekiplerinin kod değişikliklerini daha sık ve güvenilir bir şekilde sunmasını sağlayan bir kültürü, çalışma ilkelerini ve uygulamalar koleksiyonunu içerir.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e7WMp8JCnTG9P8dbPM7CKw.png" /></figure><p>Örneğin CI/CD ile gitteki bir projeyi otomatik olarak test edebilir ve deploy edebiliriz.</p><p><strong>En İyi CI/CD Araçları:</strong></p><ol><li><strong>Jenkins:</strong></li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/796/1*NbPpycLmksow4NAI1ki5pg.png" /></figure><p>Jenkins basit tanım ile, bir yazılım projesinde dinamik olarak gerekli olan yapısal işlemleri <strong>otomatize ederek</strong> projeyi hızlı, kolaylıkla hata raporlaması ve kolay test edilip hataların fixlenebilmesini sağlayan bir CI(Continous Integration) aracıdır.</p><p><strong>2. TeamCity:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*OOokyaU9WgViwtL_inkMdw.png" /></figure><p>TeamCity bir <strong>Jetbrains</strong> ürünü. 2006 yılında görücüye çıkan, Java tabanlı bir <em>Build Yönetimi, Continuous Integration </em>ve<em> Continuous Deployment </em><strong><em>sunucusu</em></strong>.</p><p><strong>3. GitLab:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*YAAgyQtKThx0UsgO72oXHQ.png" /></figure><p>GitLab web tabanlı bir Git depo uygulaması olarak tanımlanabilir. Bu depo servisi sürekli entegrasyon (CI), sürekli teslimat (CD), hata kayıt, kod gözden geçime ve wiki desteğiyle çalışıyor.</p><p><strong>4. CircleCI:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YiBabfoQ4osOVpWMcwzKMg.jpeg" /></figure><p><a href="https://circleci.com/">CircleCI,</a> açık kaynaklı projeler ve büyük ölçekli projeler için en iyi CI/CD araçlarından biridir.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b640fd9b345f" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>