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.

  • paulcdb@lemmy.worldEnglish
    0·
    2 months ago

    Hmm, am I missing something or does it not work on tablets?

    Demo looks kinda cool but can’t seem to add anything to the existing projects. 😞

    • expyth0n@lemmy.worldOPEnglish
      1·
      2 months ago

      You’re not missing anything 🙂

      Ideon isn’t fully tablet-compatible yet, and mobile portrait is even more limited at the moment.

      Touch support is something I’ve been actively working on for a while. Some interactions, like right-click equivalents, need proper tactile handling, and that requires rethinking parts of the UX rather than just patching it.

      A dedicated mobile mode for smaller screens is also planned. The challenge is making keyboard/mouse and touch experiences coexist cleanly without breaking workflows on either side, so it’s taking time to do it properly.

      Sorry for the frustration on your side. I completely understand it. It’s definitely on my roadmap, even if it will require a bit more work before it feels right…