Personal gallery application with online photo management, supporting Live/Motion Photos, and explore map.
License: MIT. Built with: Vue, TypeScript, CSS, Dockerfile, JavaScript. Website: https://chronoframe.bh8.ga/. Source: https://github.com/HoshinoSuzumi/chronoframe.
### Pull Image Use the published image on GitHub Container Registry and Docker Hub. Choose the source that works best for your network: #### [GitHub Container Registry (GHCR)](https://github.com/HoshinoSuzumi/chronoframe/pkgs/container/chronoframe) ```bash docker pull ghcr.io/hoshinosuzumi/chronoframe:latest ``` #### [Docker Hub](https://hub.docker.com/r/hoshinosuzumi/chronoframe) ```bash docker pull hoshinosuzumi/chronoframe:latest ``` ### Docker Run with customized environment variables: ```bash docker run -d --name chronoframe -p 3000:3000 -v $(pwd)/data:/app/data --env-file .env ghcr.io/hoshinosuzumi/chronoframe:latest ``` ### Docker Compose Create docker-compose.yml: ```yaml services: chronoframe: image: ghcr.io/hoshinosuzumi/chronoframe:latest container_name: chronoframe restart: unless-stopped ports: - '3000:3000' volumes: - ./data:/app/data env_file: - .env
Self-hosting gives you three things SaaS can’t: data ownership (the files live on disks you control), cost predictability (a one-time setup vs. recurring per-seat fees that grow with your household or team), and longevity (open-source means the app keeps working even if the maintainers move on, since you can pin a working version). The trade-off is that you take on the operational work of running a server, applying updates, and handling backups.
Most self-hosted apps run comfortably on modest hardware — a Raspberry Pi 4, a mini PC, a NAS with Docker support, or a small VPS is usually enough for personal or family use. CPU and RAM requirements scale with how many simultaneous users or how much data you push through ChronoFrame. Storage requirements depend on the kind of data you keep; check the README for guidance on data retention.
Last verified: 2026-05-21