<commit_before>You are now the proud owner of your very own Civilized Discourse Construction Kit. Congratulations! As a new forum admin, here's a quick start guide to get you going:

### Login as an Admin

You can login via the blue "Log in" button in the upper-right hand corner of Discourse.

Not an admin? If you used the [official install guide](https://github.com/discourse/discourse/blob/master/docs/INSTALL-ubuntu.md) you can use the following commands (taken from that guide) to elevate your account privileges:

    # Run these commands as the discourse user
    cd ~/discourse
    # ~/discourse or /var/www/discouse depending on where discourse is installed
    RAILS_ENV=production bundle exec rails c

    # (in rails console)
    > me = User.find_by_username_or_email('<EMAIL>')
    > me.activate #use this in case you haven't configured your mail server and therefore can't receive the activation mail.
    > me.admin = true
    > me.save

### Access the Admin Console<p>

To access the Discourse admin console, add `/admin` to the base URL, like so:

### http://discourse.example.com/admin

From here, you'll be able to access the Admin functions, all of which are very important, so do check each one out.

### Enable Twitter Logins

1. From the Administrative console above, enter **Site Settings**.
2. Scroll down to the two text fields named:

  `twitter_consumer_key`  
  `twitter_consumer_secret`  

3. Enter in your respective **key** and **secret** that is issued to you via dev.twitter.com. If you are unsure of what your key/secret is, or you have yet to obtain one, visit the Twitter Dev API FAQ on [how to obtain these keys](https://dev.twitter.com/docs/faq#7447).
4. In the Twitter settings, the callback url must use the path `/auth/twitter/callback` at your domain. e.g., `http://discuss.example.com/auth/twitter/callback`

### Enable Facebook Logins

1. From the Administrative console above, enter **Site Settings**.
2. Scroll down to the two text fields named:

  `facebook_app_id`  
  `facebook_app_secret`  

3. Enter in your respective **id** and **secret** that is issued to you via developers.facebook.com. If you are unsure of what your id/secret is, or you have yet to obtain one, visit the [Facebook Developers :: Access Tokens and Types](https://developers.facebook.com/docs/concepts/login/access-tokens-and-types/) page for more information.
4. In the Facebook App settings, you must enable "Website with Facebook Login" under "Select how your app integrates with Facebook" and set the Site URL to use the path `/auth/facebook/callback` at your site domain. e.g., `http://discuss.example.com/auth/facebook/callback`.

### Enable GitHub Logins<p>

1. From the Administrative console above, enter **Site Settings**.
2. Scroll down to the two text fields named:

  `github_client_id`  
  `github_client_secret`  

3. Enter in your respective **id** and **secret** that is issued to you via https://github.com/settings/applications/new. If you are unsure of what your id/secret is, or you have yet to obtain one, visit the [GitHub Developers :: Applications](https://github.com/settings/applications/) page for more information.
4. Be sure to set the Callback URL to use the path `/auth/github/callback` at your site domain. e.g., `http://discuss.example.com/auth/github/callback`.

### Creating New Categories<p>

You will get one new category by default, meta. [Check it out! It's important.](http://meta.discourse.org/category/meta) But you may want more.

Categories are the **colored labels** used to organize groups of topics in Discourse, and they are completely customizable:

1. Log in to Discourse via an account that has Administrative access.
2. Click the "Categories" button in the navigation along the top of the site.
3. You should now see a "Create Category" button at the top.
4. Select a name and set of colors for the category for it in the dialog that pops up.
5. Write a paragraph describing what the category is about in the first post of the Category Definition Topic associated with that category. It'll be pinned to the top of the category, and used in a bunch of places.

### File and Image Uploads

Image uploads should work fine out of the box, stored locally, though you can configure it so that images users upload go to Amazon S3 by [following this howto.](http://meta.discourse.org/t/how-to-set-up-image-uploads-to-s3/7229?u=codinghorror).<commit_msg>Update outdated instructions in Quick Guide<commit_after>You are now the proud owner of your very own Civilized Discourse Construction Kit. Congratulations! As a new forum admin, here's a quick start guide to get you going:

### Login as an Admin

You can login via the blue "Log in" button in the upper-right hand corner of Discourse.

Not an admin? If you used the [official install guide](https://github.com/discourse/discourse/blob/master/docs/INSTALL-ubuntu.md) you can use the following commands (taken from that guide) to elevate your account privileges:

    # Run these commands as the discourse user
    cd ~/discourse
    # ~/discourse or /var/www/discouse depending on where discourse is installed
    RAILS_ENV=production bundle exec rails c

    # (in rails console)
    > me = User.find_by_username_or_email('<EMAIL>')
    > me.activate #use this in case you haven't configured your mail server and therefore can't receive the activation mail.
    > me.admin = true
    > me.save

### Access the Admin Console<p>

To access the Discourse admin console, add `/admin` to the base URL, like so:

### http://discourse.example.com/admin

From here, you'll be able to access the Admin functions, all of which are very important, so do check each one out.

### Enable Twitter Logins

1. From the Admin console, visit User Settings, by clicking **Settings**, then **User**.
2. Scroll down to the two text fields named:

  `twitter_consumer_key`  
  `twitter_consumer_secret`  

3. Enter in your respective **key** and **secret** that is issued to you via dev.twitter.com. If you are unsure of what your key/secret is, or you have yet to obtain one, visit the Twitter Dev API FAQ on [how to obtain these keys](https://dev.twitter.com/docs/faq#7447).
4. In the Twitter settings, the callback url must use the path `/auth/twitter/callback` at your domain. e.g., `http://discuss.example.com/auth/twitter/callback`

### Enable Facebook Logins

1. From the Admin console, visit User Settings, by clicking **Settings**, then **User**.
2. Scroll down to the two text fields named:

  `facebook_app_id`  
  `facebook_app_secret`  

3. Enter in your respective **id** and **secret** that is issued to you via developers.facebook.com. If you are unsure of what your id/secret is, or you have yet to obtain one, visit the [Facebook Developers :: Access Tokens and Types](https://developers.facebook.com/docs/concepts/login/access-tokens-and-types/) page for more information.
4. In the Facebook App settings, you must enable "Website with Facebook Login" under "Select how your app integrates with Facebook" and set the Site URL to use the path `/auth/facebook/callback` at your site domain. e.g., `http://discuss.example.com/auth/facebook/callback`.

### Enable GitHub Logins<p>

1. From the Admin console, visit User Settings, by clicking **Settings**, then **User**.
2. Scroll down to the two text fields named:

  `github_client_id`  
  `github_client_secret`  

3. Enter in your respective **id** and **secret** that is issued to you via https://github.com/settings/applications/new. If you are unsure of what your id/secret is, or you have yet to obtain one, visit the [GitHub Developers :: Applications](https://github.com/settings/applications/) page for more information.
4. Be sure to set the Callback URL to use the path `/auth/github/callback` at your site domain. e.g., `http://discuss.example.com/auth/github/callback`.

### Creating New Categories<p>

You will get one new category by default, meta. [Check it out! It's important.](http://meta.discourse.org/category/meta) But you may want more.

Categories are the **colored labels** used to organize groups of topics in Discourse, and they are completely customizable:

1. Log in to Discourse via an account that has Administrative access.
2. Click the "Categories" button in the navigation along the top of the site.
3. You should now see a "Create Category" button at the top.
4. Select a name and set of colors for the category for it in the dialog that pops up.
5. Write a paragraph describing what the category is about in the first post of the Category Definition Topic associated with that category. It'll be pinned to the top of the category, and used in a bunch of places.

### File and Image Uploads

Image uploads should work fine out of the box, stored locally, though you can configure it so that images users upload go to Amazon S3 by [following this howto.](http://meta.discourse.org/t/how-to-set-up-image-uploads-to-s3/7229?u=codinghorror).
{'fraction_non_alphanumeric': 0.087248322147651, 'fraction_numerical': 0.006040268456375839, 'mean_word_length': 4.06859410430839, 'pattern_counts': {'":': 0, '<': 11, '<?xml version=': 0, '>': 19, 'https://': 10, 'lorem ipsum': 0, 'www.': 2, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 14, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '497692', 'n_tokens_mistral': 2515, 'n_tokens_neox': 2394, 'n_words': 1220}