Why self hosting

[stenw]

From reading the documentation it was not really clear to me why I would want to host organice myself. Many things run on the device visiting the page and no info is stored on the server. So what would be the advantage?

[aharish]

Hi @stenw!

Here are some reasons why you might want to:

• If you work at a company that prefers the tools they use to be on-premises - either because of a data regulation policy, or otherwise, especially if the company often handles sensitive data
• If you use a WebDAV server, but cannot for whatever reason enable CORS, then you can host Organice on the same domain (or subdomain) as your WebDAV host and connect it to Organice that way
• If you self-host a WebDAV like Nextcloud on your homelab, and don't want to expose your WebDAV to the public internet, then self-hosting Organice would enable you to use this on your local network (or something like on a Tailscale or Nebula or similar VPN network)
• If you have a set of patches or custom code that has not yet been merged to master, or you have other modifications that is not on the self hosted app. For example, if you use this in a team sharing scenario, then you can modify the frontpage of the web app to give more clear instructions to team members on how to sign in and use Oragnice
• And finally, simply because you can. Because you like to run a homelab, and love tinkering with stuff. :)

Honestly, I have never felt the need to self-host Organice, but I do have containers on my homelab from when I had spun up Organice to see how it works. I just use the official app hosted by 200ok.ch :)