Discourse Setup

[brianking]

Setup OSLC Community Discourse instance.

Preference to have them live on sub-domains:
discourse.open-services.net

2 Options:

1. Self-hosting
   https://meta.discourse.org/t/running-other-websites-on-the-same-machine-as-discourse/17247

2. Paid hosting

Things to consider:

1. Cost
2. Features being offered for each, e.g. email configuration
3. Install process
4. Path to upgrades + maintenance

TODO

• Set up https

• Enable registration via Github

[brianking]

We've setup a Digital Ocean droplet and will install Discourse there.

[brianking]

I like how Feverbee integrates Discourse into their site.

1. Go to https://www.feverbee.com/
2. Select Community from the top menu, which leads you to https://experts.feverbee.com/

Note:

• Prominent Search at the top
• Popular Topics section
• A couple of other sections before it starts to list latest posts

We may not necessarily need all these, but what I like the most and think we should do is have it on a subdomain and to keep the main site navigation structure and theme colours as much as possible.

[brianking]

I have http://discourse.oslc.co setup now. It is not open for new users yet, while we set it up properly and seed it with some topics, i.e. invite only.

For email/SMTP, we are using Mailgun which has a monthly free allocation of 10,000 emails.

[berezovskyi]

Tried to sign up with GH:

[brianking]

@berezovskyi Please try again.

I made the following changes:

"Public registration is disabled, all new users must be explicitly invited by staff." - DISABLED

"Staff must approve all new user accounts before they are allowed to access the site. WARNING: enabling this for a live site will revoke access for existing non-staff users!" - ENABLED

[berezovskyi]

thanks @brianking

there is still a URI mismatch:

[brianking]

@berezovskyi Github signup should be working now. Let us know.

[berezovskyi]

Nope, still not working after shift-refresh:

I think the port number is causing this problem. Note that I am using the sign-up button, not the login.

[brianking]

FYI we are tracking this in issue #15

[berezovskyi]

My apologies

[brianking]

As this is setup and we are tracking the github issue in #15 I am closing this one.