Replacing Obsidian Sync with a Self-Hosted LiveSync Stack

Sat, 11 Apr 2026 02:26:09 +0900

🧋 Introduction

My Journey with Note-Taking Apps

I use Obsidian as my persoanl knoweldge base instead of Notion. The reason is simple:

Notion feels too heavy
It comes with too many features I do not really need
The loading speed can feel slow at times

Obsidian, on the other hand, feels lightweight, fast, and much closer to the kind of workflow I want for managing my notes

Sync options for Obsidian

There are many possible options, and I spend quite a bit of time looking through them.

Official options
- Obsidian Sync
  - It’s polished and reliable, but it is a paid service.
- iCloud
  - This can be a solid choice if you are fully in the Apple ecosystem.
  - However, it becomes less practical when you also use non-Apple devices. (I use NixOS btw)
Unofficial options
- Git & GitHub
  - I tried this before, but the mobile experience was not great, expecially when the repository became larger.
  - On iPhone, using apps like Working Copy for pull and push operations did not feel very reliable.
- Syncthing
  - Peer-to-peer sync is a very practical approach, expecially when combined with a WireGuard-based VPN like Tailscale.
  - The main problem for me was the lack of official support on iPhone.
- ⭐ Self-hosted livesync(with CouchDB)
  - The option stood out the most to me.

Why I Chose Self-Hosted LiveSync

In the end, I decided to go with self-hosted LiveSync, backed by CouchDB, for a few reasons:

I already have my own home server running on Proxmox
The LiveSync plugin has a strong community and over 10k GitHub start
It looked fun to build and self-host

In this post, I will walk through how I set up my Obsidian sync stack using CouchDB + Caddy + Tailscale inside a Proxmox LXC container.

🏗️ Provisioning an LXC Container

First, We will provision an LXC Container in a Proxmox Cluster.
I use the Terraform provider bgp/proxmox, to manage resources declaratively.

Downloading Debian 13 LXC Image

Although we are using Terraform, the proxmox_download_file resource currently downloads the LXC image repeatedly, because of a checksum verification issue.
So for now, I will download manually instead.

First, connect to your proxmox cluster:

1

ssh <your-proxmox-cluster>

Then, list officially supported LXC images:

1

pveam available

Download the Debian13 image:

1

pveam download local debian-13-standard_13.1-2_amd64.tar.zst

Terraform Module

We will create a module to make the code reusable.

 1
 2
 3
 4
 5
 6
 7
 8
 9
 10
 11
 12
 13
 14
 15
 16
 17
 18
 19
 20
 21
 22
 23
 24
 25
 26
 27
 28
 29
 30
 31
 32
 33
 34
 35
 36
 37
 38
 39
 40
 41
 42
 43
 44
 45
 46
 47
 48
 49
 50
 51
 52
 53
 54
 55
 56
 57
 58
 59
 60
 61
 62
 63
 64
 65
 66
 67
 68
 69
 70
 71
 72
 73
 74
 75
 76
 77
 78
 79
 80
 81
 82
 83
 84
 85
 86
 87
 88
 89
 90
 91
 92
 93
 94
 95
 96
 97
 98
 99
100
101
102
103
104
105
106
107
108
109
110
111


# ./modules/lxc_container/main.tf
terraform {
 required_providers {
 proxmox = {
 source = "bpg/proxmox"
 version = "0.101.0"
 }
 }
}

resource "proxmox_virtual_environment_container" "container" {
 description = var.description

 node_name = var.node_name
 vm_id = var.vm_id

 unprivileged = true
 # If true, it cannot be destoryed.
 protection = var.protection

 features {
 nesting = true
 }

 # Required to turn on tailscaled on LXC container.
 device_passthrough {
 path = "/dev/net/tun"
 }

 # If you want you can make resource quotas to variables.
 cpu {
 cores = 2
 limit = 2
 units = 1024
 }

 memory {
 dedicated = 2048
 swap = 512
 }

 initialization {
 hostname = var.hostname

 ip_config {
 ipv4 {
 address = "dhcp"
 }
 }

 user_account {
 keys = var.ssh_keys
 password = random_password.container.result
 }
 }

 wait_for_ip {
 ipv4 = true
 }

 network_interface {
 name = var.network_interface
 }

 disk {
 datastore_id = var.datastore_id
 size = var.disk_size
 }

 operating_system {
 template_file_id = var.template_file_id
 type = var.os_type
 }

 startup {
 order = "3"
 up_delay = "60"
 down_delay = "60"
 }

 dynamic "mount_point" {
 for_each = var.mount_points

 content {
 path = mount_point.value.path
 volume = mount_point.value.volume

 size = try(mount_point.value.size, null)
 read_only = try(mount_point.value.read_only, null)
 backup = try(mount_point.value.backup, null)
 replicate = try(mount_point.value.replicate, null)
 shared = try(mount_point.value.shared, null)
 quota = try(mount_point.value.quota, null)
 acl = try(mount_point.value.acl, null)
 mount_options = try(mount_point.value.mount_options, null)
 }
 }

 tags = var.tags
}

resource "random_password" "container" {
 length = 16
 override_special = "_%@"
 special = true
}

output "container_password" {
 value = random_password.container.result
 sensitive = true
}

Here’s the module’s variables.tf.

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91


# ./module/lxc_container/variables.tf

variable "description" {
 type = string
 description = "LXC description"
}

variable "node_name" {
 type = string
 description = "Proxmox node name"
}

variable "vm_id" {
 type = number
 description = "LXC VM ID"
}

variable "protection" {
 type = bool
 description = "Whether to prevent data"
}

variable "hostname" {
 type = string
 description = "Container hostname"
}

variable "ssh_keys" {
 type = list(string)
 description = "SSH public keys for root account"
 default = []
}

variable "network_interface" {
 type = string
 description = "Container network interface name"
}

variable "datastore_id" {
 type = string
 description = "Datastore ID for root disk"
}

variable "disk_size" {
 type = number
 description = "Root disk size in GB"
}

variable "template_file_id" {
 type = string
 description = "OS template file ID"
}

variable "os_type" {
 type = string
 description = "Container OS type"

 validation {
 condition = contains([
 "alpine",
 "centos",
 "debian",
 "fedora",
 "ubuntu",
 "unmanaged"
 ], var.os_type)
 error_message = "os_type must be one of the supported Proxmox LXC OS types."
 }
}

variable "mount_points" {
 description = "Additional mount points for the container"
 type = list(object({
 path = string
 volume = string
 size = optional(string)
 read_only = optional(bool)
 backup = optional(bool)
 replicate = optional(bool)
 shared = optional(bool)
 quota = optional(bool)
 acl = optional(bool)
 mount_options = optional(list(string))
 }))
 default = []
}

variable "tags" {
 description = "Tags"
 type = list(string)
}

If we expose the IPv4 address as an output, we can connect to the LXC container more easily:

1
2
3
4


# ./modules/lxc_container/outputs.tf
output "ipv4" {
 value = proxmox_virtual_environment_container.container.ipv4
}

`provider.tf`

To passthrough a device, you need to access Proxmox using an administrator account (root@pam) with a password:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20


terraform {
 required_providers {
 proxmox = {
 source = "bpg/proxmox"
 version = "0.101.0"
 }
 }
}

provider "proxmox" {
 endpoint = <your_endpoint>
 username = var.proxmox_username
 password = var.proxmox_password
 insecure = true

 ssh {
 agent = true
 username = "root"
 }
}

`main.tf`

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31


# main.tf
locals {
 # Import your SSH public keys here
 ssh_keys = [
 ]
}

module "couchdb" {
 source = "./modules/lxc_container"
 node_name = <your-node-name>
 description = "CouchDB LXC"
 datastore_id = <your-datastore-id>
 protection = true # Recommended

 vm_id = 500 # You can change if you want
 network_interface = <your-network-interface>
 disk_size = 32 # You can change if you want
 hostname = "couchdb" # You can change if you want

 # File ID format: `datasotre_id:type/<image>`
 template_file_id = "local:vztmpl/debian-13-standard_13.1-2_amd64.tar.zst"
 os_type = "debian"
 ssh_keys = local.ssh_keys

 # Example tags
 tags = ["debian", "couchdb", "obsidian"]
}

output "couchdb_ipv4" {
 value = module.couchdb.ipv4
}

`variables.tf`

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12


# varialbes.tf
# `terraform.tfvars` should be ignored by Git.
# or, you can use environment variable: `export TF_VAR_<variable_name>`
variable "proxmox_username" {
 type = string
 default = "root@pam"
}

variable "proxmox_password" {
 type = string
 sensitive = true
}

Applying & Accessing

Now, you can create the LXC Container!

1
2
3
4
5


terraform init

terraform plan

terraform apply -auto-approve

After applying, You can access container now:

1

ssh root@<your-container-ip>

🪏 Settingup CouchDB + LiveSync

Install CouchDB

First, update the package manager and upgrade installed packages.
Then, install the dependencies required to follow the CouchDB installation instructions:

1
2
3


apt update
apt upgrade -y
apt install -y gpg curl sudo

Next, follow the official CouchDB installation guide here.

During installation, a TUI prompt will appear to configure CouchDB.
You can use the following options:

type: standalone
bind address: 127.0.0.1
Erlang magic cookie: <your-random-long-string>
admin password: <your-admin-password>

Store the informations somewhere private and secure.

To verify that CouchDB is running, check its service status:

1

systemctl status couchdb

Install Obsidian LiveSync

Replace the placeholders and run the script below:

1

curl -s https://raw.githubusercontent.com/vrtmrz/obsidian-livesync/main/utils/couchdb/couchdb-init.sh | hostname=http://<YOUR SERVER IP>:5984 username=<INSERT USERNAME HERE> password=<INSERT PASSWORD HERE> bash

You can also refer to the latest instructions here.

If the output looks like this:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12


-- Configuring CouchDB by REST APIs... -->
{"ok":true}
""
""
""
""
""
""
""
""
""
<-- Configuring CouchDB by REST APIs Done!

then the database has been initialized successfully.

🔒 Setting up Tailscale

Tailscale is a peer-to-peer VPN built on the top of WireGuard, so it lets you securely connect you devices from anywhere.

Install Tailscale on Your devices

The dashboard already provides clear installation instructions for each platform, so you can simply follow them.
You have to install Tailscale in all the devices you want to use Obsidian.

Once Tailscale is installed and connected, you can also verify it from inside your LXC container.
A new network interface should appear:

Set Up MagicDNS

Tailscale also supports internal DNS and HTTPS certificates support issued by Let’s Encrypt. \

In Dashboard -> DNS, enable MagicDNS and HTTPS Certificates.

👮 Setup Caddy

Caddy is a simple web server that can also act as a reverse-proxy.
It integrates especially well with Tailscale, which makes it a great fit fot this setup

You can install Caddy here.

In /etc/caddy/Caddyfile, configure the reverse proxy:

1
2
3
4
5
6
7
8
9


# /etc/caddy/Caddyfile
# Match your tailnet MagicDNS FQDN
https://<hostname>.<your-tailnet>.ts.net {
 reverse_proxy 127.0.0.1:5984 {
 header_up Host {host}
 header_up X-Forwarded-For {remote_host}
 header_up X-Forwarded-Proto {scheme}
 }
}

In /opt/couchdb/etc/local.ini, configure the CORS options.

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11


[chttpd]
bind_address = 127.0.0.1
port = 5984
enable_cors = true

[cors]
credentials = true
origins = app://obsidian.md, capacitor://localhost, http://localhost
headers = accept, authorization, content-type, origin, referer
methods = GET, PUT, POST, HEAD, DELETE, OPTIONS
max_age = 3600

In /etc/default/tailscaled, make sure the caddy user can access Tailscale in order to manage HTTPS certificates.

1

TS_PERMIT_CERT_UID=caddy

Then, restart the services

1
2
3


systemctl restart tailscaled
systemctl restart caddy
systemctl restart couchdb

🍰 Client usage

Almost done!
The only things left are migrating your existing vault and connecting your client devices.

Generate a Setup URI

The commands below do not need to be run inside the LXC container.
You can run them on your own laptop instead.

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12


export hostname=<your-hostname>
export database=obsidiannotes # Change this if you want
export passphrase=<random-passphrase>
export username=<username>
export password=<password>

deno run -A https://raw.githubusercontent.com/vrtmrz/obsidian-livesync/main/utils/flyio/generate_setupuri.ts

# Generated Passphrase & Link:
Your passphrase of Setup-URI is: <passphrase>
This passphrase is never shown again, so please note it in a safe place.
obsidian://setuplivesync?settings=....

Migrate Your Existing Vault

Follow these steps:

Install the Self-hosted LiveSync plugin in Obsidian.
Enable the plugin
For Device Setup Method, select Use a Setup URI.
- Enter your passphrase and URI(obsidian://setuplivesync?settings=...)
Select “I am setting up a new server for the first time / I want to reset my existing server.”
Follow the remaining steps.
Reload the app once without saving.

Register your other devices

I created a new valut in my phone, and followed these steps:

Install the Self-hosted LiveSync plugin in Obsidian.
Enable the Plugin
For Device Setup Method, select a Setup URI. (QR code didn’t work for me)
- Enter with your passphrase and URI(obsidian://setuplivesync?settings=...)
Select “My remote server is already set up. I want to join this device”
Select “This Vault is empty, or contains only new files that are not on the server”
Follow the remaining setup steps.
Reload the app once without saving.

Settings

I am using LiveSync presets, for immediate syncing.
In most case, the sync latency is under one second.

☁️ Off-Site Backup

Because the database can become a single point of failure, you should be prepared for outages or storage failures.
With an off-site backup, you can restore your data more safely.

Git & GitHub

It may feel a little awkward to keep using Git here, but it is still a practical option for a secondary backup because it is lightweight enough for frequent pushes.
You don’t need to install it on every device.
Instead, you can install a Git plugin on your main desktop or laptop and push changes continuously.
Auto-push is also supported by Git plugins.
In this setup, the .git folder is automatically ignored when syncing via LiveSync, so you don’t need to worry about sync conflicts or Git history growth affecting LiveSync.

Cloud Object Storage

Object storage services such as Cloudflare R2 or AWS S3 are highly reliable, and their lifecycle policies are very useful.
Periodically backing up your data to object storage can be a good option.
You can also automate backups using cron and the AWS CLI.

Homelab on Riveroverflow