You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/platforms/bluemix.md
+17-17Lines changed: 17 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,12 +1,12 @@
1
1
---
2
2
layout: default
3
-
title: Running on IBM Bluemix
3
+
title: Running on IBM Cloud
4
4
---
5
5
6
-
Node-RED is available on the IBM Bluemix platform as one of the [boilerplate applications](#boilerplate-application)
6
+
Node-RED is available on the IBM Cloud platform as one of the [boilerplate applications](#boilerplate-application)
7
7
in the catalog.
8
8
9
-
We also provide a '[Deploy To Bluemix](#deploy-to-bluemix)' enabled repository.
9
+
We also provide a '[Deploy To IBM Cloud](#deploy-to-ibm-cloud)' enabled repository.
10
10
11
11
---
12
12
@@ -37,14 +37,14 @@ A couple of minutes later, you'll be able to access your instance of Node-RED at
37
37
38
38
#### Customising your Node-RED application
39
39
40
-
To start customising your instance of Node-RED, you can either download the application locally or you can enable the Continuous Delivery integration option via your application's Bluemix dashboard page. That will create a git repository on either GitHub or IBM DevOps services, from where you can customize your Node-RED, save the changes and automatically update the application in Bluemix.
40
+
To start customising your instance of Node-RED, you can either download the application locally or you can enable the Continuous Delivery integration option via your application's IBM Cloud dashboard page. That will create a git repository on either GitHub or IBM DevOps services, from where you can customize your Node-RED, save the changes and automatically update the application in IBM Cloud.
41
41
42
42
##### Securing the editor
43
43
44
-
When you first ran the Node-RED instance you were presented with some options to secure the editor.
45
-
To change those options, you can set some environment variables from either the Bluemix console or the cf command-line
44
+
When you first ran the Node-RED instance you were presented with some options to secure the editor.
45
+
To change those options, you can set some environment variables from either the IBM Cloud console or the cf command-line
46
46
47
-
1. In the Bluemix dashboard, select the 'Environment Variables' page for your application
47
+
1. In the IBM Cloud dashboard, select the 'Environment Variables' page for your application
48
48
2. Add the required user-defined variables:
49
49
-`NODE_RED_USERNAME` - the username to secure the editor with
50
50
-`NODE_RED_PASSWORD` - the password to secure the editor with
@@ -65,11 +65,11 @@ add the required node modules in the `dependencies` section. The format is:
65
65
The application's package.json is setup to grab the latest stable release of Node-RED.
66
66
To trigger an upgrade following a new release being made available:
67
67
68
-
1. Per default [IBM Bluemix maintains a cache directory](https://console.bluemix.net/docs/runtimes/nodejs/configurationOptions.html#cache_behavior) per node application, to store resolved dependencies so they are not downloaded and installed every time. For updates this cache should be disabled. Set the NODE_MODULES_CACHE environment variable to false. You can either do this on your application's Bluemix console page (Runtime -> Environment Variables), or by using the cf command-line:
68
+
1. Per default [IBM Cloud maintains a cache directory](https://console.bluemix.net/docs/runtimes/nodejs/configurationOptions.html#cache_behavior) per node application, to store resolved dependencies so they are not downloaded and installed every time. For updates this cache should be disabled. Set the NODE_MODULES_CACHE environment variable to false. You can either do this on your application's IBM Cloud console page (Runtime -> Environment Variables), or by using the cf command-line:
2. Trigger a restage of your application. This cannot be done using the Bluemix console, so the cf command-line should be used:
72
+
2. Trigger a restage of your application. This cannot be done using the IBM Cloud console, so the cf command-line should be used:
73
73
74
74
cf restage [APPLICATION_NAME]
75
75
@@ -82,9 +82,9 @@ If you deployed your instance **before November 2016** you will need to take som
82
82
83
83
84
84
In order to edit the file, you must enable the Continuous Delivery integration
85
-
option via your application's Bluemix dashboard page. That will create a git repository
85
+
option via your application's IBM Cloud dashboard page. That will create a git repository
86
86
on either GitHub or IBM DevOps services, from where you can edit the file, save the
87
-
changes and automatically update the application in Bluemix.
87
+
changes and automatically update the application in IBM Cloud.
88
88
89
89
90
90
##### Changing the static web content
@@ -97,17 +97,17 @@ root path, delete the `httpStatic` and `httpAdminRoot` entries in the `bluemix-s
97
97
98
98
---
99
99
100
-
### Deploy To Bluemix
100
+
### Deploy To IBM Cloud
101
101
102
102
The [Deploy To Bluemix enabled repository](https://github.com/node-red/node-red-bluemix-starter)
103
103
lets you create your own customised Node-RED application that can then
104
-
be deployed to Bluemix with a couple clicks.
104
+
be deployed to IBM Cloud with a couple clicks.
105
105
106
106
You can try it out now by clicking here:
107
107
108
-
[](https://bluemix.net/deploy?repository=https://github.com/node-red/node-red-bluemix-starter.git)
108
+
[](https://bluemix.net/deploy?repository=https://github.com/node-red/node-red-bluemix-starter.git)
109
109
110
-
When you click the button, you are taken to Bluemix where you get a pick a name
110
+
When you click the button, you are taken to IBM Cloud where you get a pick a name
111
111
for your application at which point the platform takes over, grabs the code from
112
112
this repository and deploys it.
113
113
@@ -122,7 +122,7 @@ Node-RED runs.
122
122
#### Customising your Node-RED repository
123
123
124
124
The repository is there to be cloned, modified and re-used to allow anyone to create
125
-
their own Node-RED based application that can be quickly deployed to Bluemix.
125
+
their own Node-RED based application that can be quickly deployed to IBM Cloud.
126
126
127
127
The default flows are stored in the `defaults` directory in the file called `flow.json`.
128
128
@@ -133,7 +133,7 @@ Additional nodes can be added to the `package.json` file and all other Node-RED
133
133
configuration settings can be set in `bluemix-settings.js`.
134
134
135
135
If you do clone the repository, make sure you update the `README.md` file to point
136
-
the `Deploy to Bluemix` button at your repository.
136
+
the `Deploy to IBM Cloud` button at your repository.
137
137
138
138
If you want to change the name of the Cloudant instance that gets created, the memory
139
139
allocated to the application or other deploy-time options, have a look in `manifest.yml`.
0 commit comments