Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Set up discourse #53

Closed
bromagosa opened this issue Aug 6, 2016 · 6 comments
Closed

Set up discourse #53

bromagosa opened this issue Aug 6, 2016 · 6 comments

Comments

@bromagosa
Copy link
Owner

No description provided.

@bromagosa bromagosa added this to the Official Launch! milestone Aug 6, 2016
@bromagosa
Copy link
Owner Author

@cycomachead
Copy link

Awesome, are you planning to build the SSO features for Discourse?

I setup one for Snap! recently using SparkPost and it wasn't too bad.

http://snapforum.cs10.org - I can add you but not much has gone on yet.

@bromagosa
Copy link
Owner Author

bromagosa commented Aug 17, 2016

Yep, that was the idea!

Do you think you could help here? I worked on this yesterday and couldn't manage. Problem is we're using that same server for the BeetleCloud, and Discourse seems to want port 80 all for itself. I disabled the BeetleCloud for a while just to get the installation process going, hoping to be able to redirect it to some other port when done, but the thing is Discourse and the BeetleCloud also share the same PostgreSQL database, which I suspect is what made the install script complain and abort...

Maybe the smartest thing would be to use a separate server for Discourse?

p.s. Please do add me! :)

@bromagosa
Copy link
Owner Author

(related: #58)

@cycomachead
Copy link

I used DigitalOcean to setup Discourse, since we needed some external host.

It seems like you'll definitely want to use a subdomain for discourse - so I think you can use the same machine, though you'll probably need to some configuration do that both Discourse and BeetleCloud don't use the same DB file.

What I might try is the Docker version of discourse, which should just be able to run as a self-contained container (is that redundant??), and won't touch any of the BeetleCloud stuff.

I haven't done too much with Docker, though. But I think once you get the container running you could use the main nginx config to expose that port as a subdomain.

Some stuff I looked at that might help:

https://www.digitalocean.com/community/tutorials/how-to-install-discourse-behind-nginx-on-ubuntu-14-04
https://www.digitalocean.com/community/tutorials/how-to-set-up-nginx-virtual-hosts-server-blocks-on-ubuntu-12-04-lts--3
https://github.com/jwilder/nginx-proxy

@cycomachead
Copy link

Oh and of course, this one:

https://github.com/discourse/discourse_docker

The "advanced" section has a multisite configuration document too that seems helpful.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants