Erlend Sogge Heggen wrote:

Continuing the discussion from All the options to deploy Discourse with their relative pros and cons:

I suggest running an openly editable Jekyll wiki, probably on GitHub, with editing support via prose.io. You could enable plugins the simple way or the advanced way. Then you could use @trident's awesome Jekyll integration plugin to create discussions-per-page.

Posts: 12

Participants: 6

Read full topic

Sam Saffron wrote:

New Relic support

Author: Sam Saffron

Support for http://newrelic.com

plugins/newrelic/plugin.rb

# name: enable New Relic rpm
# about: New Relic support
# version: 0.1
# authors: Sam Saffron

ENV["NRCONFIG"] = File.expand_path('../newrelic.yml', __FILE__)
gem "newrelic_rpm", "3.6.7.152"

NewRelic::Control.instance.init_plugin :config => Rails.configuration

after_initialize do
  ForumsController.newrelic_ignore :only => [:status]
end

plugins/newrelic/newrelic.yml

The file you got from newrelic

TODO: move this to git

Posts: 1

Participants: 1

Read full topic

Watchman Monitoring wrote:

I'm trying to setup two new discourse instances, and in both cases I've forked the discourse repo.

Where along the way will I tell the Docker setup to use our repo URL, vs the one here at github.com/discourse/discourse ?

Posts: 6

Participants: 3

Read full topic

Ahmad Khayyat wrote:

What is the recommended workflow for translating Discourse?

There are two parts to this issue:

1. How to add a new language?

   • What new files need to be created?

   • What existing files need to be changed?

2. How can a translator contribute to a language translation?

   • The Internationalization / localization discussion suggests that translations are managed through GitHub pull requests. Is this an explicit choice, or is it just how things are happening? Pull requests are not translator-friendly.

   • Is there an adopted/recommended translation platform? E.g. Transifex, Crowdin.net, Pootle (needs hosting), ... etc. And which ones support the translation file format used by Discourse?
     Also, are the strings stable enough by now to upload them to a translation platform? or are they still rapidly changing?

I think a documented workflow is useful for contributors, translators, and project maintainers.

Posts: 15

Participants: 10

Read full topic

Kuba wrote:

I am trying to set up a production installation of Discourse, it's hosted on Digital Ocean and I am having a very simple issue that GMail marks all emails sent from Discourse as spam. Gmail says It's similar to messages that were detected by our spam filters. Other mail providers seem to be fine, at least the ones I tried.

I know this probably does not belong here, because it's not a problem of Discourse, but an issue of my server/hosting/mail configuration. But I'd still like to know if anyone else is having the same problem, or if anyone can point me to things to check or to a solution.

I do have SFP records and DKIM keys set up, and the email headers say:

Received-SPF: pass (google.com: domain of ... designates 198.199... as permitted sender) client-ip=198.199....;
Authentication-Results: mx.google.com;
   spf=pass (google.com: domain of ... designates 198.199... as permitted sender) smtp.mail=...;
   dkim=pass header.i=@...

Reverse DNS, full hostname on the server, all done.

I have experimented with it a little and found out: When I remove all links from the email, suddently it's not marked as spam. When I insert any link, such as a link to google.com, it is marked as spam!

I am running a Czech version of Discourse, but even when I switch back to English, it's still the same. Anyway, I really have no idea how to even dig into this and get any info about what's wrong. How do I troubleshoot this spam problem? What should I check?

Posts: 16

Participants: 7

Read full topic

Sam Saffron wrote:

Login using vkontakte

Author: @sam

plugins/vk/plugin.rb

# name: vk.com
# about: Authenticate with discourse with vk.com, see more at: https://vk.com/developers.php?id=-1_37230422&s=1
# version: 0.1.0
# author: Sam Saffron

gem 'omniauth-vkontakte', '1.2.0'


class VkAuthenticator < ::Auth::Authenticator

  CLIENT_ID = '1111111'
  CLIENT_SECRET = 'AUSTRALIASNAKESALAD'

  def name
    'vkontakte'
  end

  def after_authenticate(auth_token)
    result = Auth::Result.new

    # grap the info we need from omni auth
    data = auth_token[:info]
    raw_info = auth_token["extra"]["raw_info"]
    name = data["name"]
    vk_uid = auth_token["uid"]

    # plugin specific data storage
    current_info = ::PluginStore.get("vk", "vk_uid_#{vk_uid}")

    result.user =
      if current_info
        User.where(id: current_info[:user_id]).first
      end

    result.name = name
    result.extra_data = { vk_uid: vk_uid }

    result
  end

  def after_create_account(user, auth)
    data = auth[:extra_data]
    ::PluginStore.set("vk", "vk_uid_#{data[:vk_uid]}", {user_id: user.id })
  end

  def register_middleware(omniauth)
    omniauth.provider :vkontakte,
     CLIENT_ID,
     CLIENT_SECRET
  end
end


auth_provider :title => 'with VKontakte',
    :message => 'Log in via VKontakte (Make sure pop up blockers are not enabled).',
    :frame_width => 920,
    :frame_height => 800,
    :authenticator => VkAuthenticator.new


# We ship with zocial, it may have an icon you like http://zocial.smcllns.com/sample.html
#  in our current case we have an icon for vk
register_css <<CSS

.btn-social.vkontakte {
  background: #46698f;
}

.btn-social.vkontakte:before {
  content: "N";
}

CSS

65ded214d5e200d4.png727x400

TODO: move to git
TODO: move settings to site settings

Posts: 1

Participants: 1

Read full topic

Alejandro Petroff wrote:

Vkontakte is widespead social network in Russia as facebook is US. It provides ability to auth with it.

Vkontakte Open API Documentation page:
http://vk.com/pages?oid=-1&p=Open_API

Posts: 8

Participants: 6

Read full topic

Neckbeard wrote:

I followed the instructions and set up a second database for a second domain.

I have since reconsidered and would like to go back to having only one database (production) for both domains.
I did the naive thing and just commented out everything in multisite.yml, and restarted discourse but this only had the effect of discourse not working (nginx error message) for both domains.

The domain I want to disable has nothing in its database that I care about. Any tips would be appreciated.

Posts: 1

Participants: 1

Read full topic

printec wrote:

Most forum software don't need any where as much RAM as this. I was wondering what Discourse uses this RAM for? Is it doing a powerful amount of caching or what?

Posts: 14

Participants: 10

Read full topic

Arpit Jalan wrote:

The Discourse Docker Image makes it easy to set up Discourse on a cloud server. In this guide I'll assume that you are using Digital Ocean, although these steps will work on other similar services.

The below guide assumes that you have no knowledge of Ruby/Rails or Linux shell, so it will be detailed. Feel free to skip steps you are comfortable with.

Create New Digital Ocean Droplet

Discourse recommends a minimum of 1 GB RAM. We'll use "discourse" as the Hostname.

digital-ocean-droplet-name-size.png902x621 49.4 KB

Install Discourse on Ubuntu 12.04.3 LTS x64. We always recommend using the current LTS distribution.

digital-ocean-ubuntu.png867x600 45.8 KB

You will receive a mail from Digital Ocean with the root password to your Droplet. (However, if you use SSH keys, you may not need a password to log in.)

Access Your Droplet

Connect to your Droplet via SSH:

ssh root@192.168.1.1

(Alternately, use Putty on Windows)

Replace 192.168.1.1 with the IP address of your Droplet.

It will ask your permission to connect, type yes, then it will ask for the root password, which is in the email Digital Ocean sent you when the Droplet was set up. Enter it.

Install Git

sudo apt-get install git

Generate SSH Key

We highly recommend setting a SSH key, because you may need to access the Rails console for debugging purposes. This is only possible if you have SSH access preconfigured. This cannot be done after bootstrapping the app.

ssh-keygen -t rsa -C "your_email@example.com"

(We want the default settings, so when asked to enter a file in which to save the key, just press enter. Via GitHub's SSH guide.)

Install Docker

sudo apt-get update
sudo apt-get install linux-image-generic-lts-raring linux-headers-generic-lts-raring

Reboot the server:

sudo reboot

This will log you out from your SSH session, so SSH in again:

ssh root@192.168.1.1

Replace 192.168.1.1 with the IP address you got from Digital Ocean.

Finish installing Docker:

sudo wget -qO- https://get.docker.io/ | sh

Install Discourse

Create a /var/docker folder where all the Docker related stuff will reside:

mkdir /var/docker

Clone the Official Discourse Docker Image into this /var/docker folder:

git clone https://github.com/SamSaffron/discourse_docker.git /var/docker

Switch to your Docker directory:

cd /var/docker

Copy the samples/standalone.yml file into the containers folder as app.yml, so the path becomes containers/app.yml:

cp samples/standalone.yml containers/app.yml

Modify this newly copied app.yml:

nano containers/app.yml

(We recommend Nano because it works like a typical GUI text editor, just use your arrow keys. Hit CtrlO then Enter to save and CtrlX to exit. However, feel free to choose whatever text editor you like. In the below screenshot we use Vim.)

Modify the file as desired, but at minimum you should set DISCOURSE_DEVELOPER_EMAILS and DISCOURSE_HOSTNAME.

I renamed DISCOURSE_HOSTNAME to discourse.techapj.com, this means that I want to host my instance of Discourse on http://discourse.techapj.com/. You'll need to modify your DNS records to reflect the IP address and preferred domain name of your server.

Mail Setup

Email is critical to Discourse. We strongly recommend configuring mail settings before bootstrapping.

• If you already have a mail server, put your existing mail server credentials in the app.yml file.

• Otherwise, create a free account on Mandrill (or Mailgun, or Mailjet), and put your mail credentials (available via the Mandrill dashboard) in the app.yml file. The settings you want to change are DISCOURSE_SMTP_ADDRESS, DISCOURSE_SMTP_PORT, DISCOURSE_SMTP_USER_NAME, DISCOURSE_SMTP_PASSWORD.

Add Your SSH Key

If you successfully generated the SSH key as described earlier, get it:

cat ~/.ssh/id_rsa.pub

Copy the entire output and paste it into the ssh_key setting in the app.yml file.

Bootstrap Discourse

Be sure to save the app.yml file, and begin bootstrapping Discourse:

sudo ./launcher bootstrap app

This command may take some time, so be prepared to wait. It is automagically configuring your Discourse environment.

After that completes, start Discourse:

sudo ./launcher start app

Congratulations! You now have your own instance of Discourse, accessible via the domain name you entered in app.yml earlier.

Pasted image1136x341 56.8 KB

You can also access it by visiting the server IP address directly, e.g. http://192.168.1.1.

Log In and Become Admin

Sign into your Discourse instance. If you configured DISCOURSE_DEVELOPER_EMAILS and your email matches, your account will be made Admin by default.

If your account was not made admin, try SSH'ing into your container (assuming you entered your SSH key in the app.yml file):

./launcher ssh my_container
sudo -iu discourse
cd /var/www/discourse
RAILS_ENV=production bundle exec rails c
u = User.last
u.admin = true
u.save

This will manually make the first user an admin.

If anything needs to be improved in this guide, feel free to ask on meta.discourse.org, or even better, submit a pull request.

Posts: 78

Participants: 19

Read full topic

KajMagnus wrote:

Hi,

There was a Clear Pin button at the end of the topic "Welcome to meta.discourse.org" ( https://meta.discourse.org/t/welcome-to-meta-discourse-org/1 ) and I was wondering "What kind of access denied message will they show when I click it?"

So I clicked it. But apparently this really did un-pin the topic "Welcome to meta.discourse.org". At least that topic is no longer listed at the top of meta.discourse.org. That wasn't my intention, sorry about that — but perhaps a bug has been found?

Best regards, KajMagnus

Posts: 3

Participants: 3

Read full topic

Tom Spilman wrote:

We have a Discourse site which includes lots of public discussion, but we also have some categories where we discuss private NDA'd materials.

The category itself seems fine... people trying to access it without permission are rejected.

The issue is that the group we use to secure that category is visible to everyone. People outside that group can not only see that the group exisits, but also see the members of the group.

It seems to me that groups need as much privacy as categories do.

Posts: 6

Participants: 4

Read full topic

Codetricity wrote:

I'm a bit of the odd man here since I'm a marketer. I've been using Discourse here and at Ubuntu to gain experience with the features. I am quite excited that this is open source as it should leave the door open for more cool features for marketers in the future.

Is there a central document or place with information that would be of interest to marketers?

Many of the topics have been addressed, but it's dispersed:

• google analytics and other analytics integration. Is this the strategy to provide web analytics?
• SEO analytics
• usage analytics, per topic, per person, per time, different slices of the data
• referral traffic to other sites
• incoming referral traffic
• auto highlighting of hot topic of the week, most active person
• marketing box highlight for top "thing" such as a cool hardware hack that a member submitted
• survey, voting plugins
• social media distribution plugins

In the past year, the community groups have been placed under digital marketing at many corporations. This is a superset of social media, community relations, and digital.

Another source of budget to fund community development appears to be the product marketing groups.

An interesting twist is that since product marketing at tech companies is becoming more technical, the product marketing groups are starting to report into engineering, which is often closer to product development.

Well, my main point is that it would be great to have a stream of input from corporate marketers about the feature set so that it can be taken into consideration in the early development of Discourse.

If this type of central document for marketers doesn't exist, maybe we can use this forum to create one? It would help me to get more practice with the software.

Posts: 1

Participants: 1

Read full topic

Adriaan Putter wrote:

Will Google be able to crawl all the forum posts? Would like to know how it works if pages are loaded just-in-time.

Posts: 23

Participants: 11

Read full topic

Jeff Atwood wrote:

There's an interesting bit of drama going on in the Ubuntu Discourse forums. There's a bit of tension between the vBulletin community and the new Discourse community. It's fascinating to watch the dynamics between AskUbuntu (StackExchange), Ubuntu Forum (vBulletin) and Ubuntu Discourse (the place for more sprawling discussions). I'm also trying to get a handle on why Discourse serve a tech support function as well.

There's a bunch of exciting things happening right now with community software.

Also, thanks for the link to Jorge Castro's post about the watercooler. I hadn't see that before. I notice that his blog is using Octopress. I've been experimenting with that a bit, but we decided to launch our corporate blog with just straight Jekyll.

Posts: 10

Participants: 5

Read full topic

eriko wrote:

For ugly reasons due to a 15 years old bad decision we have usernames reused for some small portion of users after they leave our school because of the generation algorithm and length constraints. I have written a rake task that imports students into discourse based on a good data source. I also stash a truly unique id (not a SS#) when I do so. If at a latter date if I note that a username does not have a matching unique id the user is disabled and the username released "$#{login_id.reverse}" so that a new user with the correct true unique id can be created.

Currently I do the following (on separate lines while debuging)
@user.update_attribute :approved ,false
@user.update_attribute :active ,false
@user.update_attribute :username ,"$#{login_id.reverse}"
@user.update_attribute :email ,"#{login_id.reverse}@noreply.com"
What if anything else should I do to shut down the account. Bearing in mind that I can not travel back in time to kick the team that made the initial decision.

Any thoughts?

Posts: 3

Participants: 2

Read full topic

Timo wrote:

Hi,

Not sure if support is the right category, but close enough I hope. Deployed discourse on a VPS and I like what I see so far. Due to the open REST API approach of the backend I was toying with the idea of using it for account management & forum solution for my upcoming weekend project app.

Due to that a few questions:

1. Tried to look for some docs on the REST api, but couldn't find much. Are there any?
2. I've seen posts about the API going through some major rebuilding in near future. Will this affect the API itself or just the inner workings of it?

Timo

Posts: 12

Participants: 7

Read full topic

Sebastienstettler wrote:

Use case

user searches google for some information, opens a discourse forum topic link. this topic is not very fleshed out and another topic exists with more information, and is a better thread in general. it would be great if the user doesnt have to read the entire thread to find out a better one exists

visually im not sure how to display this but perhaps a little notification would work.

full benifit will only be acquired when the forum has a large user base.Continuing the discussion from Searching for existing topics before posting:

Continuing the discussion from Searching for existing topics before posting:

Posts: 6

Participants: 3

Read full topic

Grif Peterson wrote:

Is it possible to extend the "your topic is similar to" popup box to include hyperlinks that community members have already posted? If, for instance, I post a link here, it would be very useful for me to be notified of other instances community members have posted the same link. Could be a good way to merge conversations and decrease redundancy, especially when using Discourse for an online course community where users are always re-posting the same resources.

Posts: 3

Participants: 2

Read full topic

Grif Peterson wrote:

We are using Discourse as the primary discussion tool for MIT's Learning Creative Learning online course, which launches March 18. It seems like the only way to view other user's profiles is by clicking on their avatar in the discussion forums. We were wondering if there is any way for non-administrators to be able to view the "about me's" of all community members, like Peer to Peer University does with their Class Photo. It seems like being able to scroll through the profiles of community members, possibly even filtering by relevant details, would be a useful feature.

Posts: 3

Participants: 2

Read full topic