Hi selfhosters ๐
After the feedback I received from self-hosters here and elsewhere, I focused this update on things that matter specifically when you run everything on your own infrastructure.
This update adds:
- ๐ Generate public shareable links for your projects
- ๐ Organize everything using folders
- ๐ผ Export a full project as a single image
But more importantly for this community:
- ๐ Connect to GitHub, GitLab, Gitea, and Forgejo
- ๐ Use it with self-hosted Git servers
- ๐ Provide a personal access token to work with private repositories
Several people mentioned the need to work with private repos and internal Git instances without relying on external services. You can now point Ideon to your own server and use your own token. No third-party dependency required.
Installation is still designed to stay simple. One curl command:
- Downloads the docker-compose.yml
- Downloads the env.example
- Generates all required secrets securely
- Prompts you for SMTP, app URL, port, etc.
- Starts the containers
No repo cloning. No manual secret generation. No external SaaS. Everything runs in two containers: app and database.
GitHub: https://github.com/3xpyth0n/ideon
Docs: https://www.theideon.com/docs
As always, Iโm open to feedback. If you self-host it and hit friction anywhere, I want to know.
How are "public shareable links" handled? Are you just saying links generate nicely when your version is exposed on the www or is there some kind of centralized back door for public access?
Public shareable links function as interactive read-only snapshots.
When a link is generated, a unique cryptographic token is mapped to the project's current state in the database. The route serves this data to a canvas where all mutation logic and API write-access are disabled.
Key facts:
This is similar to how tools like Lufi or PrivateBin handle public access to specific resources without requiring authentication. And NoSQL/centralized backdoors ๐