forked from mozilla/BrowserQuest
-
Notifications
You must be signed in to change notification settings - Fork 220
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Revamp Heroku support and add support for Redis URLs
- Loading branch information
Showing
5 changed files
with
24 additions
and
28 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -54,7 +54,7 @@ Then install the Node.js dependencies by running: | |
|
||
$ npm config set registry http://registry.npmjs.org/ | ||
$ npm install -d | ||
|
||
Before starting the BrowserQuest server, you must start Redis. In Windows, you can simply run `redis-server.exe` in your `redis\bin\release` directory. | ||
|
||
Then start the server by running: | ||
|
@@ -178,11 +178,11 @@ Currently, BrowserQuest can run on the following PAAS (Platform as a Service) pr | |
$ git remote add github https://github.com/browserquest/BrowserQuest.git | ||
$ git fetch github | ||
$ git reset --hard github/master | ||
|
||
5. Copy the BrowserQuest config file with the following command: | ||
|
||
$ cp server/config.json server/config_local.json | ||
|
||
6. Open `server/config_local.json` in a text editor such as Gedit (Linux), TextEdit (OS X), or Vim. | ||
On the line that reads `"production": "heroku",`, change `"heroku"` to `"openshift"`. | ||
|
||
|
@@ -203,43 +203,37 @@ Congratulations! You have now deployed BrowserQuest to Openshift! You can see th | |
Visit the url shown by the above command to see BrowserQuest running. You will need to add ":8000" to the end. Use the url below as a guide: | ||
|
||
http://your_openshift_browserquest_url.rhcloud.com:8000/ | ||
|
||
### Instructions for Heroku ### | ||
|
||
1. Install the Heroku toolbelt from [here](https://toolbelt.herokuapp.com/). | ||
|
||
2. Create a new application by running the following command: | ||
|
||
$ heroku create [NAME] | ||
|
||
Where [NAME] is an optional name for your application (Heroku will automatically create one otherwise). | ||
|
||
3. Sign up for a Redis provider, such as [Redis To Go](https://redistogo.com), or host a Redis instance yourself. | ||
3. Add heroku-redis add-on: | ||
|
||
heroku addons:create heroku-redis:hobby-dev | ||
|
||
4. Run the following commands to allow BrowserQuest to run on Heroku: | ||
|
||
$ heroku config:add HEROKU=true | ||
$ heroku config:add HEROKU_REDIS_HOST=[REDIS_HOST] | ||
$ heroku config:add HEROKU_REDIS_PORT=[REDIS_PORT] | ||
$ heroku config:add HEROKU_REDIS_PASSWORD=[REDIS_PASSWORD] | ||
|
||
Where [REDIS_HOST], [REDIS_PORT], and [REDIS_PASSOWRD] are your Redis hostname, port, and password, respectively. | ||
If you Redis instance is configued without a password, omit the last command. | ||
|
||
Note: If you use RedisToGo, you will be provided with a URL that looks something like this: | ||
If you need to use a different Redis provider than `heroku-redis`, set a `REDIS_URL`: | ||
|
||
redis://redistogo:[email protected]:9023/ | ||
|
||
In this case, your REDIS_HOST is `something.redistogo.com`, your REDIS_PORT is `9023`, and your REDIS_PASSWORD is `12345678901234567890`. | ||
$ heroku config:add REDIS_URL=[REDIS_URL] | ||
|
||
5. Deploy to Heroku by running the following command: | ||
|
||
$ git push heroku master | ||
|
||
6. Enable the Heroku WebSockets lab (needed for communication between the browser and the BrowserQuest server) with the following command: | ||
|
||
$ heroku labs:enable websockets | ||
|
||
|
||
Congratulations! You have now deployed BrowserQuest to Heroku! To open BrowserQuest in your browser, run `heroku open`. | ||
|
||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters