Feedback on use case and brainstorming

[Aeosium]

I am happy to start the round of discussions :)

First of all thanks a lot for this development, it has very high potential and is a game changer for those dreaming of obsidian as on prem web app. I made it run on my Synology NAS very easily and it's already an excellent base. Here are a few bullets on present observations and what would be a dream set-up for me

• What I would miss to use this in production
  • Having the possibility to use obsidian-livesync (extensions in general of course, I couldn't install any so far but didn't try too much). I wonder whether this could be extended further for self hosted collaborative tool (e.g. by spinning several instances, each of them configured with obsidian livesync for individual users, or using Relay but this one is paid service although there is a limited self hosted offer)
  • Having the possibility to insert images from clipboard, file upload (maybe via dedicated extension for the UI)
• Bonus
  • Progressive web app (I don't know if the minimize/maximize/close button on top right can easily be removed)
  • Some auth solution (for this I am lucky my organization provides an openshift cluster with auth that can be added on top with sso/oidc)
  • Multiple vaults (for now changing vault is not possible, but can also be easily mitigated by running one instance per vault)
  • Access to obsidian cli (ok now I am going over the top 😄 )

I understand this repo is proof of concept but the base and potential is so good that I am sure it will attract attention. I can imagine there will be some level of convergence on needs, or maybe trigger the obsidian dev to re-consider offering such a solution in their roadmap?

Anyway, this made my day so thanks again!

[Aeosium]

In case it can be useful to anybody, a few steps I took to deploy on my Synology NAS

git clone https://github.com/MusiCode1/obsidian-web.git obsidian-web

In obsidian-web

FROM node:20-alpine

WORKDIR /app

# Copy project files
COPY . .

# Download Obsidian renderer
RUN node scripts/update-obsidian.js

# Install server dependencies
WORKDIR /app/server
RUN npm install

# Expose the default port
EXPOSE 3000

# Set environment variables (you can override these at runtime)
ENV HOST=0.0.0.0
ENV PORT=3000
ENV VAULT_PATH=/app/vault

# Start the server
CMD ["npm", "start"]

In the parent folder to obsidian-web

version: '3.8'

services:
  obsidian-web:
    build:
      context: ./obsidian-web  # Path to Dockerfile relative to compose.yaml
      dockerfile: Dockerfile
    container_name: obsidian-web
    ports:
      - "3000:3000"  # e.g. "4123:3000"  to change port
    environment:
      - HOST=0.0.0.0
      - PORT=3000
      - VAULT_PATH=/app/vault
    volumes:
      # Maps a folder on your host machine to the vault inside the container
      - /base/docker/obsidian:/app/vault
    restart: unless-stopped

The structure looks like this (Dr. Frankenstein layout)

/base/docker/
│
├── obsidian/                              # Your actual vault data lives here
│   └── (Your markdown notes...)
│
└── projects/
    └── obsidian-compose/                  # Your main project folder
        │
        ├── compose.yaml                   # Your Docker Compose configuration
        │
        └── obsidian-web/                  # The cloned GitHub repository
            │
            ├── Dockerfile                 # The Dockerfile you created here
            │
            └── (other repo files obtained with git clone) # scripts, server, client, etc.

Then running via the container manager + reverse proxy from within Synology DSM

[MusiCode1]

I really want to try to integrate LiveSync into the demo, so that basically anyone who has a LiveSync instance can connect to their instance.

I'm also thinking about maybe making a binary that anyone can download and run on their computer, and then access it from anywhere.

Anyway, I'm currently trying to move from Obsidian Desktop to Obsidian Mobile, where there's a lot of abstraction that makes it really easy to create polyfills for all the built-in interfaces that are supposed to support Obsidian Mobile.

[GitTom]

Regarding your LifeSync idea ... yes, making the backend more flexible would be great. I personally think it would be good to have a PostgreSQL + S3 backend, while others might want it to use a GitHub repo as the vault (though that would be harder I think).