5 ms·

Okay it's open source but self-hosting it is not straightforward. The repo's self-hosting doc link returns a 404. Then after manually finding https://docs.plane

Okay it's open source but self-hosting it is not straightforward. The repo's self-hosting doc link returns a 404. Then after manually finding https://docs.plane.so/self-hosting/self-hosting https://docs.plane.so/self-hosting/self-hosting, I am warned that there is a dizzying array of 4 env files. I suppose they are in a tricky situation, in that while they want to stand out as open source, actually having people easily self-host it, is perhaps, not a goal that is currently in their interest! Correction: removed wrong Docker-Compose command interpretation, as I have been schooled!

yencabulator 3y ago
Is it even really open source? Looked more like open core earlier: https://github.com/makeplane/plane/issues/1171 https://github.com/makeplane/plane/issues/1171
volderette 3y ago
Docker integrated docker-compose a while ago, so the command is correct.
vlugorilla 3y ago
`docker-compose` is the old version of docker compose. The modern command is `docker compose` since it is part of docker: https://docs.docker.com/engine/reference/commandline/compose/ https://docs.docker.com/engine/reference/commandline/compose...
brinox 3y ago
`docker-compose` is the old style of doing it. Newer versions of Docker have Compose available as a CLI plugin, so the command `docker compose` with space is correct.
deleted 3y ago
[deleted]
EspadaV9 3y ago
`docker compose` is correct for the newer (still pretty old) plugin based version of docker compose. `docker-compose` is the older standalone version. https://docs.docker.com/compose/reference/ https://docs.docker.com/compose/reference/
- luke-stanley 3y ago
  Thanks to you and others who swiftly correct me!
dabeeeenster 3y ago
Spent 10 minutes trying to get it running locally, couldn't. 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" ™.
- allarm 3y ago
  If you just follow the documentation [1], it "just works". I just installed it on my machine, everything was up and running within 3-5 minutes. 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. [1] https://docs.plane.so/self-hosting/docker-compose https://docs.plane.so/self-hosting/docker-compose
- dabeeeenster 3y ago
  Ugh - ok finally got it working (it runs on port 80 by default but the docs mention 8080) and then browsing to the homepage gets me: Your Plane instance isn't ready yet Ask your Instance Admin to complete set-up first. With nothing in the docs about this.
  - allarm 3y ago
    > it runs on port 80 by default but the docs mention 8080 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. [1] https://docs.plane.so/self-hosting/docker-compose https://docs.plane.so/self-hosting/docker-compose
bachmeier 3y ago
It's been a long time since I fell for the marketing slogan about a product like this being open source. I wasted a lot of hours learning that lesson. If a company has a financial incentive for something to not work, it's not that hard to make sure it doesn't.
lnxg33k1 3y ago
If you want to self-host the only sanity-aware path is redmine, imho
Alex3917 3y ago
I haven't look at this particular project, but having to type the same information into multiple env files is unfortunately pretty unavoidable. Making a Docker / Django project instantiable via template and then runnable locally and deployable in production unfortunately involves 5+ different variable templating systems, which each require their variables to be declared in different files and formats.
- zoobab 3y ago
  "instantiable via template" A simple bash template via envsubst?
  - Alex3917 3y ago
    I meant a Django template, e.g.: https://www.valentinog.com/blog/django-project/ https://www.valentinog.com/blog/django-project/
DrBazza 3y ago
Software installation, even for simple trials reminds me of this Stephen Hawking quote: "Someone told me that each equation I included in the book would halve the sales. I therefore resolved not to have any equations at all. In the end, however, I did put in one equation, Einstein's famous equation, E = mc squared. I hope that this will not scare off half of my potential readers." It just feels like that law can be adapted to: for every step and pre-requisite in your setup, you lose half your potential customers. Of course, it's not precisely that, but it feels the same.
- runnerup 3y ago
  This is great wisdom for software. I’ll definitely carry this parable with me.
- whazor 3y ago
  Some of these self hosted projects need five containers: frontend, backend, database, redis, and elasticsearch. Way too many if you ask me. My preferred self hosted projects only need one container and has a embedded sqlite database. With the option to configure a external database.
  - GauntletWizard 3y ago
    Building an app that scales to enterprise size is hard. Building an app that does so while also scaling down to single-team size is hard. Every feature you build two backends for is one more thing to go wrong. Writing a sqlite backend for your redis usage, your search, etc... it's not insane, and it's a sign of good Faith, but it's not something that should be expected, either.
- bayindirh 3y ago
  I, for one, am not afraid of manually building a stack to self-host an application. I'd prefer it over Docker in fact, because it makes everything exposed, and as an admin, I love to know what I'm tinkering with. However, the docs should be good. No hidden layers, no skimped over steps, no "insert some magic here". It's your app, you know it by heart, but I'm just getting to know it. If you do this as an established application or a developer which also sell your product as a SaaS, I assume that you're doing it in bad faith, and move on.

yencabulator 3y ago

Is it even really open source? Looked more like open core earlier: https://github.com/makeplane/plane/issues/1171 https://github.com/makeplane/plane/issues/1171

volderette 3y ago

Docker integrated docker-compose a while ago, so the command is correct.

vlugorilla 3y ago

`docker-compose` is the old version of docker compose. The modern command is `docker compose` since it is part of docker: https://docs.docker.com/engine/reference/commandline/compose/ https://docs.docker.com/engine/reference/commandline/compose...

brinox 3y ago

`docker-compose` is the old style of doing it. Newer versions of Docker have Compose available as a CLI plugin, so the command `docker compose` with space is correct.

deleted 3y ago

[deleted]

EspadaV9 3y ago

`docker compose` is correct for the newer (still pretty old) plugin based version of docker compose. `docker-compose` is the older standalone version. https://docs.docker.com/compose/reference/ https://docs.docker.com/compose/reference/

luke-stanley 3y ago
Thanks to you and others who swiftly correct me!

dabeeeenster 3y ago

Spent 10 minutes trying to get it running locally, couldn't. 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" ™.

allarm 3y ago
If you just follow the documentation [1], it "just works". I just installed it on my machine, everything was up and running within 3-5 minutes. 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. [1] https://docs.plane.so/self-hosting/docker-compose https://docs.plane.so/self-hosting/docker-compose
dabeeeenster 3y ago
Ugh - ok finally got it working (it runs on port 80 by default but the docs mention 8080) and then browsing to the homepage gets me: Your Plane instance isn't ready yet Ask your Instance Admin to complete set-up first. With nothing in the docs about this.
- allarm 3y ago
  > it runs on port 80 by default but the docs mention 8080 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. [1] https://docs.plane.so/self-hosting/docker-compose https://docs.plane.so/self-hosting/docker-compose

bachmeier 3y ago

It's been a long time since I fell for the marketing slogan about a product like this being open source. I wasted a lot of hours learning that lesson. If a company has a financial incentive for something to not work, it's not that hard to make sure it doesn't.

lnxg33k1 3y ago

If you want to self-host the only sanity-aware path is redmine, imho

Alex3917 3y ago

I haven't look at this particular project, but having to type the same information into multiple env files is unfortunately pretty unavoidable. Making a Docker / Django project instantiable via template and then runnable locally and deployable in production unfortunately involves 5+ different variable templating systems, which each require their variables to be declared in different files and formats.

zoobab 3y ago
"instantiable via template" A simple bash template via envsubst?
- Alex3917 3y ago
  I meant a Django template, e.g.: https://www.valentinog.com/blog/django-project/ https://www.valentinog.com/blog/django-project/

DrBazza 3y ago

Software installation, even for simple trials reminds me of this Stephen Hawking quote: "Someone told me that each equation I included in the book would halve the sales. I therefore resolved not to have any equations at all. In the end, however, I did put in one equation, Einstein's famous equation, E = mc squared. I hope that this will not scare off half of my potential readers." It just feels like that law can be adapted to: for every step and pre-requisite in your setup, you lose half your potential customers. Of course, it's not precisely that, but it feels the same.

runnerup 3y ago
This is great wisdom for software. I’ll definitely carry this parable with me.
whazor 3y ago
Some of these self hosted projects need five containers: frontend, backend, database, redis, and elasticsearch. Way too many if you ask me. My preferred self hosted projects only need one container and has a embedded sqlite database. With the option to configure a external database.
- GauntletWizard 3y ago
  Building an app that scales to enterprise size is hard. Building an app that does so while also scaling down to single-team size is hard. Every feature you build two backends for is one more thing to go wrong. Writing a sqlite backend for your redis usage, your search, etc... it's not insane, and it's a sign of good Faith, but it's not something that should be expected, either.
bayindirh 3y ago
I, for one, am not afraid of manually building a stack to self-host an application. I'd prefer it over Docker in fact, because it makes everything exposed, and as an admin, I love to know what I'm tinkering with. However, the docs should be good. No hidden layers, no skimped over steps, no "insert some magic here". It's your app, you know it by heart, but I'm just getting to know it. If you do this as an established application or a developer which also sell your product as a SaaS, I assume that you're doing it in bad faith, and move on.