Store and share text snippets and files within your local network.
License: MIT. Built with: HTML, Go, CSS, JavaScript, Shell, Dockerfile. Source: https://github.com/Tanq16/local-content-share.
```bash docker run --name local-content-share \ -p 8080:8080 \ -v $HOME/.localcontentshare:/app/data \ tanq16/local-content-share:main ``` The application will be available at `http://localhost:8080` (or your server IP). You can also use the following compose file with container managers like Portainer and Dockge (remember to change the mounted volume): ```yaml services: contentshare: image: tanq16/local-content-share:main container_name: local-content-share volumes: - /home/tanq/lcshare:/app/data # Change as needed ports: - 8080:8080
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 Local Content Share. Storage requirements depend on the kind of data you keep; check the README for guidance on data retention.
Last verified: 2026-05-21