Refactor: Reorganize services into standalone structure

optimized/standalone/ubuntu-unbound/README.md

@@ -0,0 +1,44 @@
+# Ubuntu Unbound
+
+This directory contains the `docker-compose.yml` for building and running an Ubuntu-based server with Unbound DNS.
+
+## Running with Podman Compose
+
+To run this service using `podman-compose`:
+
+1.  Navigate to this directory:
+    ```bash
+    cd optimized/standalone/ubuntu-unbound
+    ```
+2.  Build the image (if not already built by the original `build.sh`):
+    ```bash
+    podman-compose build
+    ```
+3.  Start the service:
+    ```bash
+    podman-compose up -d
+    ```
+
+## Running with Podman
+
+Due to `network_mode: host` and `privileged: true`, directly translating this `docker-compose.yml` into a single `podman run` command can be complex and may require manual setup of host network configuration.
+
+A basic `podman run` example (adapt carefully, as `network_mode: host` has specific implications):
+
+```bash
+podman run -d \
+  --name ubuntu_server \
+  --network host \
+  --privileged \
+  -e TZ=America/New_York \
+  -v ubuntu_data:/data \
+  -v ubuntu_config:/config \
+  ubuntu-server:latest # Assuming 'ubuntu-server:latest' is the built image name
+```
+
+## Notes
+
+*   Remember to replace any placeholder values (e.g., timezone) with your actual configuration.
+*   The original `build.sh` file might contain additional steps or configurations relevant to the build process.
+*   `network_mode: host` means the container shares the host's network namespace, using the host's IP address directly.
+*   `privileged: true` grants the container nearly all capabilities of the host machine, which should be used with extreme caution.