node-syte | js port of the popular syte

There are a few steps in order to get Syte configured, but don't worry they are pretty easy. Note I recommend you branching your fork and not checking in sensitive settings to GitHub! Warning Do not place OAuth keys and tokens in a public repository.
Syte uses Tumblr or Wordpress for blogging. If you have a Tumblr blog you will need to get the api_key needed to call their APIs. In order to do that register your site with them by going to http://www.tumblr.com/oauth/register, fill in the information about your site, there is no need to enter a default callback url or an icon. Once you are done your website will be listed under http://www.tumblr.com/oauth/apps, save the OAuth Consumer Key value that's the api_key we need for Syte. Once you have the api_key from Tumblr you have to enter it in syte_settings.py located in syte > syte_settings.py. Once you open that file enter the key under TUMBLR_API_KEY, also please enter your Tumblr url under TUMBLR_BLOG_URL see the example on how it should be formatted. For now Syte only support wordpress blogs that are build using wordpress.com. Open syte > syte_settings.py and under WORDPRESS_BLOG_URL enter ther url of your wordpress.com blog, also under BLOG_PLATFORM set it to "wordpress". Comments are available through Disqus in order to get yours setup, make sure to signup through their website. Once you are done you will be given a Disqus shortname. Grab the shortname and enter it in syte_settings.py under DISQUS_SHORTNAME, also make sure to have DISQUS_INTEGRATION_ENABLED set to True in order to work.
Twitter has another level of security, therefore we need more information instead of just an api_key like Tumblr. To get started create a new application on Twitter for your website by going to https://dev.twitter.com/apps/new. Once you are done creating your application you will be taken to your application page on Twitter, there you already have two pieces of the puzzle, the Consumer key and the Consumer secret make sure you save those. Next you will need your access tokens, on the bottom of that page there is a link called Create my access token click on that. Once you are done you will be given the other two pieces of the puzzle, the Access token and the Access token secret make sure you save those as well.
Consumer key string you saved under TWITTER_CONSUMER_KEY
Consumer secret string you saved under TWITTER_CONSUMER_SECRET
Access token string you saved under TWITTER_USER_KEY
Access token secret string you saved under TWITTER_USER_SECRET
GitHub has the same level of security as Twitter, but they don't provide a button that makes it easy to get the access token, so instead we have to get the access token ourselves. To get started sign in to GitHub and go to https://github.com/settings/applications/new to register your application. Enter the Application Name, Main URL and Callback URL. For the Callback URL enter http://127.0.0.1:8000/github/auth for now since we will get the access token while running it locally. Once you are done registering your application you will be given the Client ID and Client Secret.
Client ID under GITHUB_CLIENT_ID
Client Secret under GITHUB_CLIENT_SECRET
You don't have to do anything to setup the Dribbble integration. If you want to turn off this feature just set DRIBBBLE_INTEGRATION_ENABLED setting to False in syte_settings.py.
Instagram has the same level of security as GitHub and similar steps on getting the access token ourselves. To get started go to http://instagram.com/developer/, sign in and crate a new client by clicking on the Manage Clients link on the top right side. Enter the Application Name, Description, Website and OAuth redirect_Uri. For the OAuth redirect_uri enter http://127.0.0.1:8000/instagram/auth/ for now since we will get the access token while running it locally. The trailing slash is required for Instagram not to complain that the redirect_Uri is wrong. Once you are done registering your client you will be given the Client ID and Client Secret.
Client ID under INSTAGRAM_CLIENT_ID
Client Secret under INSTAGRAM_CLIENT_SECRET
Access Token under INSTAGRAM_ACCESS_TOKEN
User ID under INSTAGRAM_USER_ID
Foursquare has the same level of security as Instagram and similar steps on getting the access token ourselves. To get started go to https://foursquare.com/oauth/register, sign in and register a new consumer. Enter the Application Name, Application Website and Callback URL. For the callback url enter http://127.0.0.1:8000/foursquare/auth for now since we will get the access token while running it locally. Once you are done registering your consumer you will be given the Client ID and Client Secret.
Client ID under FOURSQUARE_CLIENT_ID
Client Secret under FOURSQUARE_CLIENT_SECRET
Access Token under FOURSQUARE_ACCESS_TOKEN
The Last.fm integration does not make any authenticated calls so setting it up only requires that you register an application with Last.fm and get an API key. To get an API key simply follow the Getting started instructions. You can then view your API Key from your api account page.
API_KEY under LASTFM_API_KEY
USERNAME under LASTFM_USERNAME
In order to setup the SoundCloud integration you first need to create a SoundCloud application by going to http://soundcloud.com/you/apps. Once you have the CLIENT_ID from SoundCloud open the syte_settings.py file and enter it under the SOUNDCLOUD_CLIENT_ID setting. Inside syte_settings.py there are two other options to configure how your SoundCloud tracks will be shown. If you want to turn off SoundCloud integration just set SOUNDCLOUD_INTEGRATION_ENABLED to False.
SOUNDCLOUD_SHOW_ARTWORK (Boolean) set this option to true if you want to show your track artwork on page.
SOUNDCLOUD_PLAYER_COLOR you can set your widget theme color here. Use Hex values only without #
The Bitbucket integration does not make any authenticated calls nor does it require a registered API key. If you want to turn off Bitbucket integration just set BITBUCKET_INTEGRATION_ENABLED to False. To display the fork count on repositories set BITBUCKET_SHOW_FORKS to True. The Bitbucket API require one call for each repository to get fork count, which is disabled by default. The Bitbucket API throttles the user resource to 100 calls every 30 minutes.
The Tent.io integration does not make any authenticated calls nor does it require a registered API key. If you want to turn off Tent.io integration just set TENT_INTEGRATION_ENABLED to False. Inside syte_settings.py there are two other options to configure your Tent.io entity.
Your Entity-URI under TENT_ENTITY_URI
URL to a Feed or Tent-Status under TENT_FEED_URL
In order to setup Steam integration you first need to create a Steam Web API key by going to http://steamcommunity.com/dev/apikey. Once you have the STEAM WEB API KEY from Steam open the syte_settings.py file and enter it under the STEAM_API_KEY setting. If you want to turn off Steam integration just set STEAM_INTEGRATION_ENABLED to False.
The StackOverflow integration does not make any authenticated calls nor does it require a registered API key. If you want to turn off StackOverflow integration just set STACKOVERFLOW_INTEGRATION_ENABLED to False.