Update from Obsidian

Author: demetrebadzaradze

.obsidian/workspace.json

@@ -4,24 +4,59 @@
     "type": "split",
     "children": [
       {
-        "id": "d4265ee8c9b67859",
+        "id": "5472ed7d5f54e7a1",
         "type": "tabs",
         "children": [
           {
-            "id": "16962415b3d73cc1",
+            "id": "db7581b044eb37e3",
             "type": "leaf",
             "state": {
               "type": "markdown",
               "state": {
-                "file": "New Server Setup (Debian).md",
+                "file": "Disk image backups.md",
                 "mode": "source",
-                "source": false
+                "source": true
               },
               "icon": "lucide-file",
-              "title": "New Server Setup (Debian)"
+              "title": "Disk image backups"
             }
           }
         ]
+      },
+      {
+        "id": "08b43c6270dddbb6",
+        "type": "tabs",
+        "children": [
+          {
+            "id": "a3aea08b505d1cdb",
+            "type": "leaf",
+            "state": {
+              "type": "markdown",
+              "state": {
+                "file": "Disk image backups.md",
+                "mode": "preview",
+                "source": false
+              },
+              "icon": "lucide-file",
+              "title": "Disk image backups"
+            }
+          },
+          {
+            "id": "fb4fc36cb03ca014",
+            "type": "leaf",
+            "state": {
+              "type": "markdown",
+              "state": {
+                "file": "New Terraria server.md",
+                "mode": "preview",
+                "source": false
+              },
+              "icon": "lucide-file",
+              "title": "New Terraria server"
+            }
+          }
+        ],
+        "currentTab": 1
       }
     ],
     "direction": "vertical"
@@ -164,20 +199,23 @@
       "command-palette:Open command palette": false
     }
   },
-  "active": "16962415b3d73cc1",
+  "active": "db7581b044eb37e3",
   "lastOpenFiles": [
+    "How to change theme for Hugo.md",
+    "Instaswarm.md",
+    "New Terraria server.md",
+    "Disk image backups.md",
     "Over-Engineering, oh man....md",
     "Remote Applications.md",
-    "Setting up PI-Hole.md",
     "New Server Setup (Debian).md",
-    "Instaswarm.md",
-    "How to change theme for Hugo.md",
     "Making SSH-Keys.md",
+    "test.md",
+    "Templates/default-hugo-post-props.md",
+    "Setting up PI-Hole.md",
     "Super-Spork.md",
     "Recovering corrupted USB drive.md",
     "Self-Hosted Mumble Voice Server with Docker, Lightweight Discord Alternative.md",
     "Rooting a TV Box via UART and Arduino.md",
-    "Templates/default-hugo-post-props.md",
     "fun git procedure.md",
     "emulationstation2.pot",
     "redit post.md",

Disk image backups.md

@@ -0,0 +1,57 @@
+---
+title: Disk images
+description: Recently I found myself working with SD cards and thumb drives more often than usual. Reformatting and data recovery and all sorts of related things. Here I will explain how I backup data from storage devices.
+date: 2026-03-06
+draft: false
+toc: true
+ShowLastmod: true
+---
+## Plan
+Here how simple **backup** works:
+- Make raw disk image containing exact bit-by-bit copy of the physical drive.
+- Compress it for better storage.
+
+When it comes to **restoring** this data I will just:
+-  Decompress the `dick image`.
+- Write it to the drive.
+
+Also, I must mention that, You should not always write to disk. instead you could mount the `disc image` as a loop device.
+
+## Make raw disk image
+this is commonly done with `dd` command on Linux.
+```bash
+sudo dd if=/dev/sdx of=random_sdcard_backup.img bs=4M status=progress
+```
+here `sdx` is the  name of the device. `lsblk` command can be used to list storage devices and their information (e.g. name). 
+
+## Compress disk image
+Usually this `.img` file takes up as much storage as the devices storage amount. So compressing it is a good Idea. 
+There are lot of compression algorithms and one you chouse may vary depending on what king of information is on the drive and what do you intend to use it for. For example if the data on the drive is already pretty compressed then using better compression algorithms like `xz` would not do a lot, other than take a lot longer.  I found that `gzip` is the  best middle of the ground option. It had been the standard for Linux for decades at this point.
+So here is how compression with `gzip` goes:
+```bash
+gzip random_sdcard_backup.img
+```
+Here we could use `-k` for the option for keeping the original file. Also `-1, --fast` to compress faster and `-9, --best` to compress better. 
+
+
+## Decompress disk image
+Decompressing is similar we just :
+```bash
+gunzip random_sdcard_backup.img.gz
+```
+`-k` can again be used to keep the input file. 
+
+This can also be  done with  `gzip` and `-d` option.
+
+## Write to disk
+Now this is the actual writing to disk part and it is done with `dd` command, like this:
+```bash
+sudo dd if=random_sdcard_backup.img of=/dev/sdX bs=4M status=progress
+```
+Make sure the device path is correct.
+
+`.img` can also be mounted as a loop device like this:
+```bash
+sudo mount -o loop random_sdcard_backup.img /mnt/sd-loop
+```
+make sure destination path exists.

New Server Setup (Debian).md

@@ -51,7 +51,7 @@ for monitoring i will be using `btop` looks nice and is displaying some useful g
 
 
 ### Nextcloud setup
-Easiest way to run Nextcloud is with container, but since I'm using `btop` i want to monitor everything separately and not as one docker program for example, so i will be installing it manually, following the [official manual](https://docs.nextcloud.com/server/stable/admin_manual/installation/source_installation.html#) witch uses [LAMP Stack]()https://www.ibm.com/think/topics/lamp-stack.
+Easiest way to run Nextcloud is with container, but since I'm using `btop` i want to monitor everything separately and not as one docker program for example, so i will be instaldling it manually, following the [official manual](https://docs.nextcloud.com/server/stable/admin_manual/installation/source_installation.html#) witch uses [LAMP Stack]()https://www.ibm.com/think/topics/lamp-stack.
 
 #### PHP Install
 Recommended PHP version, for now, is `v8.3` and in Debian repos there is only the newest version that can be installed like this:

New Terraria server.md

@@ -0,0 +1,65 @@
+---
+title: New Terraria server
+description: Updating existing Terraria server from vanilla containerized server (not even using the compose file) to more professional server using `TShock`, open source software for more control over the server.
+date: 2025-12-04
+draft: false
+toc: true
+ShowLastmod: true
+---
+## Intro
+
+I already had a [Terraria server](https://demetrebadzaradze.github.io/Second-Brain/posts/host-terraria-server-on-linux-server/) set up that I used for a while. But once I came back, I saw a lot of flaws with my previous setup, mainly performance, and not enough customization. So I searched and found this project called [TShock.](https://github.com/Pryaxis/TShock/ ) It is great, and in short, it tweaks a lot of things that are public in the Terraria source code. It also makes a lot of things much better like world saving, administration and it is structurally better than junk I had before.
+
+## Plan
+Plan is to have a **TShock** powered terraria server as a container, make it easily runnable and also migrate to it. 
+
+## Docker compose set-up
+This time i will  be using `docker compose`, since it is easy to configure one `.yml` file once and than just compose it up and down, rather than figuring out want environment variable need to be based in a docker run command, every time I start the server. Plus this way I can make server start automatically after boot.
+
+Here is what the `compose.yml` file looks like:
+```yaml
+services:
+  terraria:
+    image: ghcr.io/pryaxis/tshock:latest
+    container_name: terraria-test
+    volumes:
+      - "./tshock/:/tshock"
+      - "./worlds:/worlds"
+      - "./plugins:/plugins"
+      - "/etc/localtime:/etc/localtime:ro"
+    ports:
+      - "7777:7777"
+#    command: -world /worlds/<world name>.wld
+    restart: "no"
+    stop_grace_period: 60s
+    tty: true
+    stdin_open: true
+```
+`restart` can be set to `unless-stopped` so it starts on boot.
+> **NOTE:** `command` option is commented because initial run of the container is just needed to create the world. After that this option needs to be uncommented and world name needs to be entered appropriately (replacing `<`, `>` and content in the middle).  
+
+## Running the server
+Now this can be ran in two ways. 
+
+1.   First is the interactive way with this:
+```bash
+docker compose run terraria
+```
+>**NOTE:** Here `terraria` is the name of the service that is defined in the `.yml` file. So replace it accordingly.
+
+2. And none interactive way with:
+```bash
+docker compose up
+```
+This just gives read only logs of the container. You can also run this in detached mode with `-d` option. This way is simpler and preferred if you are not going to use any commands on not interact with the program, it is great for just running it.
+
+### First run
+Upon first boot, if you don't have the world created and entered in the  `.yml`, you will have to create the world. This is an interactive process so run with `run` command instead of `up` and follow the world configuration steps.
+
+### After first run
+After initial run world should be created in the appropriate directory (`./worlds`, on host, in this case) with the name you chouse, as a `.wld` file. Then uncomment the the `command` option in `.yml` file and configure whatever you wish. And finally run it as you wish.
+
+## Migrating from old set-up to TShock
+All we need is a `.wld` file from the old set-up. Place that into `./worlds` directory (optional, since you can just mount the old path for `/worlds` directory, but clean), uncomment `command` option in the `.yml` and  input the appropriate path to this world. 
+
+You can then follow the TShock guidance in the chat and finish the setup and then configure the server as you wish.