Below is the docker compose file just to get CouchDB up and running:

version: "3.8"

services:
  couchdb-obsidian-livesync:
    container_name: obsidian-livesync #shortened name
    image: couchdb:3.3.3
    environment:
      - PUID=99
      - PGID=100
      - UMASK=0022
      - TZ=Asia/Ho_Chi_Minh
      - COUCHDB_USER=obsidian_user # optionally change me
      - COUCHDB_PASSWORD=obsidian_password # definitely change me
    volumes:
      - ./data:/opt/couchdb/data
      - ./etc/local.d:/opt/couchdb/etc/local.d
      - ./log:/opt/couchdb/var/log/couchdb # Added log volume
    ports:
      - "5984:5984"
    restart: unless-stopped
    labels:
      - net.unraid.docker.webui=http://[IP]:[PORT:5984]/_utils # This might need to be manually adjusted for the web UI
      - net.unraid.docker.icon=https://couchdb.apache.org/image/couch@2x.png
      - net.unraid.docker.shell=bash
    healthcheck:
      test: ["CMD", "curl", "-f", "http://localhost:5984/_up"] # Healthcheck for CouchDB
      interval: 30s
      timeout: 10s
      retries: 3
      start_period: 5s

CouchDB – Initial Configuration

1. Go to the CouchDB admin page by going here: http://10.10.10.13:5984/_utils make sure to use your server’s IP address.

2. Login using the credentials you set in the Docker compose file.

3. Click on the <-> icon on the top left, it will expand the menu from simple icons to icons with text which will make following this guide easier.

4. Click on Setup on the left menu.

5. Click on Configure as Single Node and enter the same credentials from the Docker compose file into the Specify your Admin credentials fields.

6. Leave everything else the same and click Configure Node.

CouchDB – Verify Installation

1. Let’s verify the CouchDB installation by clicking Verify on the left menu.

2. Click Verify Installation and if everything is good, a popup banner should popup saying Success! Your CouchDB installation is working. Time to Relax. along with 6 check marks next to each item in the table.

CouchDB – Create Database

1. Click on the Databases on the left menu.

2. Click on Create Database on the top right.

3. Under Database Name enter obsidiandb, or whatever you like. Advice: if you intend to use this setup for multiple users, each user will need their own database, so I recommend naming the database to include the user’s first name like: obsidiandb_john or obsidiandb_jane just to make it easier in the future.

4. Under Partitioning select Non-partitioned - recommended for most workloads. Once the database is created, you should be redirected to the new database’s config page. You don’t have to do anything here.

CouchDB – Configuration

1. Click on Configuration on the left main menu. The following 9 config entries are what the script was intended to do automatically but I wanted to do it manually. Click on + Add Option on the top right for each entry:

2. Section: chttpd Name: require_valid_user Value: true

3. Section: chttpd_auth Name: require_valid_user Value: true

4. Section: httpd Name: WWW-Authenticate Value: Basic realm="couchdb"

5. Section: httpd Name: enable_cors Value: true

6. Section: chttpd Name: enable_cors Value: true

7. Section: chttpd Name: max_http_request_size Value: 4294967296

8. Section: couchdb Name: max_document_size Value: 50000000

9. Section: cors Name: credentials Value: true

10. Section: cors Name: origins Value: `app://obsidian.md,capacitor://localhost,http://localhost

Obsidian – Windows 11 Client

1. Download and install the Windows 11 Obsidian client from here.

2. Once installed, open Obsidian.

3. Next to Create new vault click the Create button next.

4. In the Vault name field, name your Vault whatever you like, I simply named mine Vault. You can think of a vault as a "master folder" that contains all your folders and notes. Some users have different vaults for different aspects of their lives, such as Work or Personal but I keep everything under one vault for ease of use.

5. Next setting is Location, click Browse. This is where your vault will be locally saved. I created an Obsidian folder in the Documents folder but you can put it anywhere you like.

6. Click Create and Obsidian should open up to your newly created vault with 3 window panes. Next step is to setup the LiveSync plugin.

Obsidian – LiveSync Plugin

1. Click on options button (sprocket icon) on the bottom left area.

2. Click Community plugins and click on the Turn on community plugins button after reading the risk disclosure.

3. Next to Community plugins click on the Browse button.

4. Search for Self-hosted LiveSync.

5. Only 1 plugin should show up and that’s the one by voratamoroz, click on it.

6. Click the Install button and let it install.

7. Click the Enable button.

8. Click Open setting dialog button.

9. Click Options button.

10. Under Settings for Self-hosted LiveSync. you should see a row of 8 buttons, click on the 4th button with the satellite icon.

11. This is where we will enter the self-hosted CouchDB details. Next to Remote Type make sure CouchDB is selected from the drop down menu.

12. In the URI field type http://10.10.10.13:5984 make sure to change to your server IP and port. (Open the container online with HAProxy)

13. In the Username field type osidian_user or whatever you used in the docker compose.

14. Same for Password field.

15. In the Database name field type obsidiandb or whatever you named your database earlier in CouchDB.

16. Click the Test button to test the connection to the CouchDB database. Assuming everything is working properly a text popup should say Connected to obsidiandb successfully.

17. Click the Check button to confirm the database was configured properly, there should be a purple checkmark next to each line item. If not, there should be a Fix button next to the item that you can click for it to either create or correct for you, but I prefer to manually do it myself.

18. Assuming everything is good up to this point, click the Apply button next to Apply Settings.

19. Optional but recommended: scroll down to the End-to-end encryption and toggle it on and set a passphrase. Please remember this passphrase as all your other devices must have matching passphrases for it to be able to decrypt your notes. Click the red button Just apply.

20. On the top menu, under Settings for Self-hosted LiveSync. you should see a row of 8 buttons, click on the 5th button with the refresh icon.

21. Next to Sync mode select LiveSync from the drop down menu.

22. You can close the settings windows out, on the top right of the notes you should see Sync: zZz which means everything is working properly and the sync is in standby mode until you start typing something.

23. Repeat the above instructions for all other devices.

Reverse Proxy

I highly recommend putting this behind at least a reverse proxy, I use Nginx Proxy Manager in conjunction with Cloudflare Tunnels. You will definitely need to if you plan on using mobile devices as they require HTTPS.

Why choose PeerTube?

1. Decentralisation

PeerTube is based on a decentralised architecture, which means that videos are hosted on several independent servers instead of a single centralised platform. This reduces dependency on a single entity and improves resilience and confidentiality.

2. Open Source and Free

PeerTube is entirely open source, allowing users to modify and customise the software to suit their needs. You can visit the PeerTube GitHub repository to access the source code, suggest improvements or report problems.

3. Total control

By hosting your own instance of PeerTube, you have complete control over content, privacy settings and moderation policies. This allows you to create a video sharing environment that perfectly matches your needs and values.

4. Interoperability

PeerTube allows different PeerTube servers to be interconnected via the ActivityPub protocol, enabling users to share and discover videos between different servers. This encourages a global community while allowing local autonomy.

5. Easy to install

Installing PeerTube via Docker Compose is quick and easy, allowing you to deploy a video sharing server in just a few minutes.

Installing PeerTube with Docker Compose

Installing PeerTube via Docker Compose is straightforward. Here is a step-by-step guide to setting up PeerTube on your server.

Prerequisites

Before you start, make sure that Docker and Docker Compose are installed on your server. You can install them using the following commands:

sudo apt update
sudo apt install docker.io docker-compose -y

Creating the Docker Compose file

Create a docker-compose.yml file in a directory of your choice. This file will contain the configuration needed to deploy PeerTube. Use the following code to configure PeerTube:

version: '3'

services:
  peertube:
    image: chocobozzz/peertube:latest
    container_name: peertube
    ports:
      - "9000:9000"
    volumes:
      - ./peertube_data:/var/www/peertube
    environment:
      - NODE_ENV=production
      - DATABASE_URL=postgres://peertube:peertube@db:5432/peertube
      - REDIS_URL=redis://redis:6379
    depends_on:
      - db
      - redis
    restart: always

  db:
    image: postgres:latest
    container_name: peertube-db
    volumes:
      - ./db_data:/var/lib/postgresql/data
    environment:
      - POSTGRES_USER=peertube
      - POSTGRES_PASSWORD=peertube
      - POSTGRES_DB=peertube

  redis:
    image: redis:latest
    container_name: peertube-redis
    volumes:
      - ./redis_data:/data

Explanations

• peertube:
• image: Indicates the official PeerTube Docker image.
• container_name: Name of the container for easy identification.
• ports: Map port 9000 on the container to port 9000 on the host to access the PeerTube web interface.
• volumes: Create a local directory to store persistent PeerTube data. Create the peertube_data directory in the same directory as your docker-compose.yml file.
• environment: Defines the environment variables needed to configure PeerTube.
  
• db:
• image: Indicates the official Docker image of PostgreSQL, the database used by PeerTube.
• container_name: Name of the container for easy identification.
• volumes: Create a local directory to store the database data. Create the db_data directory in the same directory as your docker-compose.yml file.
• environment: Defines the environment variables for configuring PostgreSQL.
  
• again:
• image: Indicates the official Redis Docker image, used for caching and sessions.
• container_name: Name of the container for easy identification.
• volumes: Create a local directory to store Redis data. Create the redis_data directory in the same directory as your docker-compose.yml file.
  

Launch PeerTube

Once you have created the docker-compose.yml file, launch PeerTube with the following command:

sudo docker-compose up -d

This command downloads the Docker images, creates the containers, and starts PeerTube, PostgreSQL, and Redis in the background. You can access the PeerTube web interface by opening a browser and navigating to http://:9000.

Initial configuration

When you first connect to the PeerTube interface, follow the on-screen instructions to complete the initial configuration. You will then be able to create users, customise settings and start sharing videos.

Conclusion

PeerTube is a powerful and flexible platform for creating and managing a decentralised video-sharing network. With its easy installation via Docker Compose and extensive customisation capabilities, PeerTube is an excellent choice for those looking to manage their own video-sharing platform while respecting decentralisation and privacy.

Useful links

• PeerTube official website
• PeerTube GitHub repository
• Official PeerTube documentation
  

Share your experiences with PeerTube and ask your questions in the comments section!

Why choose Plex?

1. Centralised organisation

Plex lets you centralise all your media – whether films, TV series, music or photos – in a single library that can be accessed from any device. You can easily organise and categorise your content for quick and intuitive access.

2. Streaming on All Devices

Plex supports the streaming of your media to a variety of devices, including smartphones, tablets, computers, and smart TVs. Whether you’re at home or on the move, you can access your media wherever you are.

3. Elegant and intuitive interface

The Plex interface is modern and easy to navigate. It offers detailed information about your media, such as film posters, series summaries and information about music artists, enhancing your viewing experience.

4. Advanced features

Plex offers advanced features such as offline synchronisation, metadata management and the ability to share your library with other users. The Plex Pass version offers even more features, such as live streaming and TV recording.

5. Ease of installation

Installing Plex via Docker Compose is quick and easy, allowing you to quickly configure your personal media server.

Installing Plex with Docker Compose

Installing Plex via Docker Compose is a straightforward process. Here’s a step-by-step guide to configuring Plex on your server.

Prerequisites

Before you start, make sure that Docker and Docker Compose are installed on your server. You can install them using the following commands:

sudo apt update
sudo apt install docker.io docker-compose -y

Creating the Docker Compose file

Create a docker-compose.yml file in a directory of your choice. This file will contain the configuration needed to deploy Plex. Use the following code to configure Plex:

version: '3'

services:
  plex:
    image: plexinc/pms-docker:latest
    container_name: plex
    ports:
      - "32400:32400"
    volumes:
      - ./config:/config
      - ./data:/data
    restart: always
    environment:
      - PLEX_CLAIM=your_plex_claim_token
      - ADVERTISE_IP=http://<your-server-ip>:32400/
      - PLEX_UID=1000
      - PLEX_GID=1000

Explanations

• image: Indicates the official Plex Docker image.
• container_name: Name of the container for easy identification.
• ports: Maps port 32400 on the container to port 32400 on the host to access the Plex web interface.
• volumes: Set up local directories to store Plex configurations and data. Create the config and data directories in the same directory as your docker-compose.yml file.
• environment: Sets the environment variables required for Plex. Replace your_plex_claim_token with your Plex claim token. You can obtain a token from Plex Claim.
  

Launch Plex

Once you have created the docker-compose.yml file, run Plex with the following command:

sudo docker-compose up -d

This command downloads the Docker image, creates the container and starts Plex in the background. You can access the Plex web interface by opening a browser and navigating to http://:32400/web.

Initial configuration

When you first connect to the Plex interface, you’ll need to follow the on-screen instructions to complete the initial configuration. You will be able to add your media libraries, configure your server settings, and invite users to share your content.

Conclusion

Plex is a complete solution for managing and distributing your personal media. Easy to install via Docker Compose and packed with features, it transforms the way you access your media content. Using Plex, you can create a personal media centre that meets all your entertainment needs.

Useful links

• Official Plex website
• Plex GitHub repository
• Official Plex documentation
  

Share your experiences with Plex and ask your questions in the comments section!

Why choose Portainer?

1. User-friendly graphical interface

Portainer offers an easy-to-use graphical interface for managing your Docker containers. You can view, deploy and manage your services, volumes and networks from a centralised dashboard.

2. Multi-host management

Portainer allows you to manage multiple Docker hosts from a single interface. This is particularly useful for production environments or clustered deployments, where you can monitor and control several Docker servers at the same time.

3. Image and container management

With Portainer, you can easily pull, delete and manage Docker images. It also makes it easy to deploy new containers and manage those already running.

4. Ease of installation

Installing Portainer is quick and easy, especially when using Docker Compose. You can configure and start up Portainer in just a few minutes.

5. Security and User Management

Portainer allows you to manage users and permissions, giving you granular control over access and authorised operations in your Docker environment.

Installing Portainer with Docker Compose

Installing Portainer via Docker Compose is a simple process. Here’s a step-by-step guide to help you set up Portainer on your server.

Prerequisites

Before you start, make sure that Docker and Docker Compose are installed on your server. You can install them using the following commands:

sudo apt update
sudo apt install docker.io docker-compose -y

Creating the Docker Compose file

Create a docker-compose.yml file in a directory of your choice. This file will contain the configuration required to deploy Portainer. Use the following code to configure Portainer:

version: '3'

services:
  portainer:
    image: portainer/portainer-ce:latest
    container_name: portainer
    ports:
      - "9000:9000"
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - portainer_data:/data
    restart: always

volumes:
  portainer_data:

Explanations

• image: Indicates the official Portainer Docker image.
• container_name: Name of the container for easy identification.
• ports: Maps port 9000 on the container to port 9000 on the host to access the web interface.
• volumes: Mounts the Docker socket and a volume for storing persistent Portainer data.
• restart: Configures the container to restart automatically in the event of a problem.
  

Launch Portainer

Once you have created the docker-compose.yml file, run Portainer with the following command:

sudo docker-compose up -d

This command downloads the Docker image, creates the container and starts Portainer in the background. You can access the Portainer web interface by opening a browser and navigating to http://:9000.

Initial configuration

When you first connect to the Portainer interface, you will need to create an administrator user and configure access to your Docker hosts. Follow the on-screen instructions to complete the initial configuration.

Conclusion

Portainer is an essential tool for anyone working with Docker. With its user-friendly graphical interface and powerful features, it makes it easy to manage Docker containers and hosts. Installation with Docker Compose is quick and easy, allowing you to deploy Portainer in no time.

Useful links

• Official Portainer website
• Portainer GitHub repository
• Official Portainer documentation
  

Share your experiences with Portainer and ask your questions in the comments section!

Why choose Uptime Kuma?

1. Open Source and Free

Uptime Kuma is an open source tool, which means that you can access the source code free of charge, modify it and adapt it to your needs. This approach guarantees transparency and flexibility. You can consult the Uptime Kuma GitHub repository to access the code, report bugs or contribute to development.

2. Ease of installation and use

Uptime Kuma is designed to be easy to install and use. Its official documentation guides users through the configuration steps. The user interface is intuitive, enabling rapid management of monitors and simplified configuration of alerts.

3. Multimodal surveillance

Uptime Kuma offers comprehensive monitoring using multiple protocols such as HTTP(s), TCP, and ICMP. This makes it possible to monitor various types of services and quickly detect problems before they affect users.

4. Alerts and Notifications

You can set up alerts to let you know if there are any problems with your services. Uptime Kuma supports a variety of notification channels, including email and Slack, ensuring that you stay informed of interruptions or failures in real time.

5. Alternative to Paid Services

Uptime Kuma is a free alternative to paid monitoring tools such as Uptime Robot and Pingdom. It offers similar functionality at no cost, making it an attractive option for users looking to monitor their services at no extra cost.

Installing Uptime Kuma with Docker Compose

Installing Uptime Kuma via Docker Compose is quick and easy. Here’s a step-by-step guide to configuring this tool on your server.

Prerequisites

Before installing Uptime Kuma, make sure that Docker and Docker Compose are installed on your server. You can install them using the following commands:

sudo apt update
sudo apt install docker.io docker-compose -y

Creating the Docker Compose file

Create a docker-compose.yml file in a directory of your choice. This file will contain the configuration needed to deploy Uptime Kuma. Use the following code to configure Uptime Kuma:

version: '3'

services:
  uptime-kuma:
    image: louislam/uptime-kuma:latest
    container_name: uptime-kuma
    ports:
      - "80:80"
      - "443:443"
    volumes:
      - ./data:/app/data
    restart: always

Explanations

• image: Indicates the official Uptime Kuma Docker image.
• container_name: Name of the container for easy identification.
• ports: Maps container ports to host ports. Ports 80 and 443 are exposed for HTTP and HTTPS.
• volumes: Create a local volume to store persistent data. Create the data directory in the same directory as your docker-compose.yml file.
• restart: Configures the container to restart automatically in the event of a problem.
  

Lancer Uptime Kuma

Once you have created the docker-compose.yml file, run Uptime Kuma with the following command:

sudo docker-compose up -d

This command downloads the Docker image, creates the container and starts Uptime Kuma in the background. You can access the Uptime Kuma web interface by opening a browser and navigating to http://.

Initial configuration

After accessing the Uptime Kuma interface, follow the on-screen instructions to complete the initial configuration. You’ll be able to add services to be monitored, set up alerts and customise settings to suit your needs.

Conclusion

Uptime Kuma is an open source monitoring solution that offers a free and effective alternative to paid monitoring tools. With its extensive functionality and user-friendly interface, it’s ideal for monitoring your online services. Using Docker Compose for installation, you can easily deploy Uptime Kuma on your server.

Useful links

• Uptime Kuma official website
• Uptime Kuma GitHub repository
• Official Uptime Kuma documentation
  

Share your impressions and ask your questions in the comments section!

Introduction to Docker

What is Docker?

Docker is an open source platform that automates the deployment of applications in software containers. These containers are lightweight, fast and portable, and contain everything an application needs to run: code, runtime, system libraries, etc.

Why use Docker?

Here are some of the main advantages of Docker :

1. Portability: Docker containers can be run anywhere – on your local machine, in the cloud, or on on-premise servers – without having to worry about differences in system configuration.
2. Isolation: Each container operates in isolation, which means that applications do not overlap or cause conflicts.
3. Resource efficiency: Unlike virtual machines, containers share the same system kernel and don’t need a complete OS, which significantly reduces resource usage.
4. Ease of management: Docker simplifies the process of updating and deploying applications, thanks to tools like Docker Compose.
   

Quick installation of Docker

Installing Docker

To install Docker on a Debian-based distribution such as Ubuntu, run the following command:

sudo apt update && sudo apt install docker.io apparmor -y

Installing Docker Compose

Docker Compose is a tool that lets you define and manage multi-container applications. To install it, use the following commands:

sudo curl -L "https://github.com/docker/compose/releases/download/v2.19.1/docker-compose-$(uname -s)-$(uname -m)" -o /usr/local/bin/docker-compose
sudo chmod +x /usr/local/bin/docker-compose

Checking the installation

To check that Docker Compose has been correctly installed, run :

docker-compose --version

Useful commands for Docker

Creating and launching containers with Docker Compose

To create and launch containers defined in a docker-compose.yml file, use :

sudo docker-compose up --build --remove-orphans -d

Deleting containers with Docker Compose

To stop and delete containers, networks and volumes defined in the docker-compose.yml file :

sudo docker-compose down

Updating a container

To update a container, follow these steps:

1. Stop containers :
   
2. List Docker images :
   
3. Delete the image of the container to be updated:
   
4. Recreate and relaunch containers :
   

Accessing a container via SSH

To access a running container via SSH :

sudo docker exec -it container-name /bin/bash

Note: Use /bin/sh if /bin/bash is not available.

sudo docker exec -it container-name /bin/sh

View container logs

To monitor a container’s logs in real time :

sudo docker logs -f container-name

Conclusion

Docker offers a powerful and flexible solution for deploying and managing applications. Whether you’re a developer, system administrator or just curious, Docker can transform the way you work with software. Feel free to try out the commands above and explore further the possibilities offered by this revolutionary technology.

If you have any questions or comments, leave them below! Don’t forget to share this article if you found it useful.

—

Note: The controls and instructions mentioned in this article are based on a typical configuration and may need to be adjusted to suit your specific environment.