The current docs talk about installing node etc, it's all unnecessary - we should push folks to use Docker for ease of updating and deployment.
@tommoor I've actually got this up and running in a pretty simple way on Cyberpanel (uses openlitespeed).
I had to manually install nodejs 12 LTS/yarn + install and configure postgres. Once that was done it was just editing .env running the few commands and it was working.
Once I had it working via the pm2 command it was just a case of adding a context to my website:
`context / {
type appserver
location /home/
binPath /bin/node
appType node
startupFile index.js
appserverEnv 1
maxConns 100
env process.env.NODE_ENV=production
env NODE_TLS_REJECT_UNAUTHORIZED=0
rewrite {
}
addDefaultCharset off
}`
And it was then running the same as any PHP website, but actually faster! The push to docker is probably going to cut off some users, who'd likely want to use it in a shared hosting environment (which should be possible) and with more users it'd bring into play revenue streams for paid/subscription addons (which I'd welcome as the product is good). Happy to doc out my steps if it helps keep the none docker version alive!
From Cyberpanel steps:
If you do decide to keep the docs for self hosting outside docker I'll do more detailed instructions!
It might be good to offer Docker images for people who’d like to use that, but please also offer manual installation (without needing AWS or Google or Slack). Also an Ansible Playbook might be a nice addition …
@fooness this is a complete manual install, but you'll still need Google or Slack for authentication. It doesn't use docker, just nodejs + postgres + Openlitespeed. Cyberpanel just makes things a little easier.
But why is Google or Slack necessary? What about username/password, what about SSO/SAML/LDAP …
If Outline demands Google or Slack for authentication, we cannot use Outline in our education institution.
I like this style of authentication because it allows the developer to focus on features and performance rather than authentication (which can be a complete time sink).
It'd be nice to see more options provided in the future (O365 etc.)
It is an opensource product and therefore the code could be modified to support another style of login.
This would be amazing to have and is stopping me from switching to Outline.
I'd like to deploy Outline to AWS or GCP and I prefer doing so in the simplest way possible. The current instructions are quite involved.
Is there a simpler guide anywhere that has a Dockerized way of deploying Outline to production?
Yes, the official docket image is here:
https://hub.docker.com/r/outlinewiki/outline
On Wed, Oct 14, 2020 at 14:07 Aamir Mansoor notifications@github.com
wrote:
This would be amazing to have and is stopping me from switching to Outline.
I'd like to deploy Outline to AWS or GCP and I prefer doing so in the
simplest way possible. The current instructions are quite involved.Is there a simpler guide anywhere that has a Dockerized way of deploying
Outline to production?—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/outline/outline/issues/1491#issuecomment-708660205,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAC474XYYEYBDXJJFFJLEUDSKYHHPANCNFSM4QK2GULA
.
Most helpful comment
But why is Google or Slack necessary? What about username/password, what about SSO/SAML/LDAP …
If Outline demands Google or Slack for authentication, we cannot use Outline in our education institution.