@@ -12,7 +12,6 @@ If not set, the functions run in "local" mode, otherwise they run in "cloud"
1212mode.
1313
1414
15-
1615quick start
1716================================================================================
1817
@@ -31,7 +30,6 @@ This code snippet above will get the port, binding host, and full URL to your HT
3130server and use them to bind the server and print the server URL when starting.
3231
3332
34-
3533running in Cloud Foundry vs locally
3634================================================================================
3735
@@ -48,14 +46,12 @@ it will provide useful values when you're running in Cloud Foundry AND
4846when you're running locally.
4947
5048
51-
5249api
5350================================================================================
5451
5552The ` cfenv ` package exports the following function:
5653
5754
58-
5955` getAppEnv(options) `
6056--------------------------------------------------------------------------------
6157
@@ -126,6 +122,8 @@ is running locally, and `https:` otherwise; you can
126122force a particular protocol by using the ` protocol ` property
127123on the ` options ` parameter.
128124
125+ When running in Cloud Foundry, the ` url ` and ` urls ` values will have
126+ ` localhost ` as their hostname, if the actual hostnames cannot be determined.
129127
130128
131129AppEnv methods
@@ -303,39 +301,14 @@ Next, push the app with `cf push`.
303301When you visit the site, you'll see the output of various cfenv calls.
304302
305303
306-
307- hacking
304+ changes
308305================================================================================
309306
310- If you want to modify the source to play with it, you'll also want to have the
311- ` jbuild ` program installed.
312-
313- To install ` jbuild ` on Windows, use the command
314-
315- npm -g install jbuild
316-
317- To install ` jbuild ` on Mac or Linux, use the command
307+ ** 1.0.3** - 2014/10/02
318308
319- sudo npm -g install jbuild
309+ - fixes for compatibility with Diego - [ issue # 11 ] [ ]
320310
321- The ` jbuild ` command runs tasks defined in the ` jbuild.coffee ` file. The
322- task you will most likely use is ` watch ` , which you can run with the
323- command:
324-
325- jbuild watch
326-
327- When you run this command, the application will be built from source, the server
328- started, and tests run. When you subsequently edit and then save one of the
329- source files, the application will be re-built, the server re-started, and the
330- tests re-run. For ever. Use Ctrl-C to exit the ` jbuild watch ` loop.
331-
332- You can run those build, server, and test tasks separately. Run ` jbuild `
333- with no arguments to see what tasks are available, along with a short
334- description of them.
335-
336-
337- changes
338- ================================================================================
311+ [ issue #11 ] : https://github.com/cloudfoundry-community/node-cfenv/issues/11
339312
340313** 1.0.2** - 2014/09/29
341314
@@ -344,15 +317,18 @@ changes
344317
345318** 1.0.1** - 2014/09/29
346319
347- - remove node_modules from .cfignore - [ issue #8 ] ( https://github.com/cloudfoundry-community/node-cfenv/issues/8 )
320+ - remove node_modules from .cfignore - [ issue #8 ] [ ]
348321- updated package dependencies
349322- changed README.md to correct sample service to cf-env-test
350323- files in lib/ recompiled due to coffee-script update
351324
325+ [ issue #8 ] : https://github.com/cloudfoundry-community/node-cfenv/issues/8
326+
352327** 1.0.0** - 2014/09/03
353328
354329- initial 1.0.0 release
355330
331+
356332license
357333================================================================================
358334
0 commit comments