They suddenly mention nginx in the self hosting docs - why?!
I don't understand open source projects that required you to fiddle around with scripts, environment files, reverse proxies etc to try the platform out! docker compose up should "just work" ™.
Your Plane instance isn't ready yet Ask your Instance Admin to complete set-up first.
With nothing in the docs about this.
No, it doesn't mention it:
> NGINX_PORT - This is default set to 80. Make sure the port you choose to use is not preoccupied. (e.g NGINX_PORT=8080)
The docs [1] are clear and concise. You just have to actually read it.
If the goal is just to test the application functionality, a demo site that's already set up and publicly accessible would be much easier than having to deploy a Docker container.
In terms of Nginx, using it to handle web server functionality, and especially encryption, while acting as a gateway into your containerized apps is a pretty bog-standard approach, and makes for good separation of concerns. I don't see much value in having that stuff implemented separately within each application and creating more config complexity for sysadmin work.
Mind, I don't think Plane's one of these. The open-source release seems comprehensive and the doc just seems not very good because the people who wrote it are experienced operators. But the claim being made isn't one that's easily put to rest except through the company in question committing to enthusiastic and comprehensive support that dispels doubts. (And, well--they chose that life!)
They even wrote a setup script that saves you from the mind-boggling complexity of docker, giving you a simple menu where you only have to read the items and press a key. If you don't know which key to press, the readme [1] is very helpful. The only place where you will have to "fiddle" with the environment files is to change the default port from 80 to another. And if you're not ready for that, or not skilled enough to understand what that means and why you might need to do it - you're not ready for self-hosting and should take a step back and learn the basics of OS administration.
Oh, and they mention nginx because this software uses nginx inside a container. Hope that answers your question.
On their webpage it says that you can get started in 30 seconds with their hosted instance. Would be nice if it was as simple to get started with a locally hosted instance.
I think it’s reasonable to provide as close to a one-line / one-action initial install, even for people who are experienced admins. (Those experienced folks can edit/tweak as they like, but having a basic “push this and something sensible happens” goes a long, long way to getting people to succeed in trying the product.)
I don't want a new project, I want to try self-hosting the software. If I am using it and liking it then certainly I would put time and effort into it. If it takes some time fiddling around with docker even to use, well, I have other projects to fiddle.
That goes for all self-hosted, but especially so for a project management tool. I'd be trialing it because I have projects I already need help managing. Adding one more is friction that would likely turn me away.
Where did you get this from? You do not need to fiddle around with anything to have it working. The only thing that _probably_ requires "fiddling" is the nginx port - and you need to change it only if the default port is already in use. Is it really that difficult nowadays???
Not everything needs to be enterprise whizbang out the gate.