Skip to content

Commit 19dd45d

Browse files
committed
CF/Docker doc improvement
1 parent 778de79 commit 19dd45d

File tree

2 files changed

+38
-24
lines changed

2 files changed

+38
-24
lines changed

deploy/cloud-foundry/README.md

+22-24
Original file line numberDiff line numberDiff line change
@@ -6,29 +6,9 @@ The quickest way to install Stratos is to deploy it as a Cloud Foundry applicati
66

77
You can do it in two ways:
88

9-
1. Deploy Stratos using the [`splatform/stratos`](https://hub.docker.com/r/splatform/stratos) docker image
10-
11-
This can be done with command `cf push -f manifest-docker.yml`:
12-
```yaml
13-
# manifest-docker.yml
14-
# https://docs.cloudfoundry.org/devguide/deploy-apps/manifest.html#docker
15-
---
16-
applications:
17-
- name: console
18-
docker:
19-
image: splatform/stratos:latest
20-
instances: 1
21-
memory: 64M
22-
disk_quota: 384M
23-
# env:
24-
# FORCE_ENDPOINT_DASHBOARD: true
25-
# services:
26-
# - console_db
27-
```
28-
29-
2. Build Stratos from the [source code](https://github.com/cloudfoundry-incubator/stratos)
9+
1. Build Stratos from the [source code](https://github.com/cloudfoundry-incubator/stratos)
3010

31-
To do so, clone the `stratos` repository, cd into the newly cloned repository and push to Cloud Foundry. This can be done with:
11+
To do so, `clone` the **stratos** repository, `cd` into the newly cloned repository and `push` to Cloud Foundry. This can be done with:
3212

3313
```
3414
git clone https://github.com/cloudfoundry-incubator/stratos
@@ -38,8 +18,26 @@ You can do it in two ways:
3818
cf push
3919
```
4020

41-
42-
>**NOTE** The console will pre-configure the host Cloud Foundry endpoint. No other CF instance can be registered unless the instructions in the section 'Enable Endpoints Dashboard to register additional Cloud Foundry endpoints' are followed.
21+
2. Deploy Stratos using the [`splatform/stratos`](https://hub.docker.com/r/splatform/stratos) docker image
22+
23+
> **NOTE:** To deploy Stratos in this way the CF Docker support have to be [enabled](https://docs.cloudfoundry.org/adminguide/docker.html#enable).
24+
25+
- download [manifest-docker.yml](../manifest-docker.yml) or create your own manifest file:
26+
```yaml
27+
applications:
28+
- name: console
29+
docker:
30+
image: splatform/stratos:stable
31+
instances: 1
32+
memory: 128M
33+
disk_quota: 384M
34+
```
35+
- now, you can simply push it to Cloud Foundry:
36+
```
37+
cf push -f manifest-docker.yml
38+
```
39+
40+
>**NOTE:** The console will pre-configure the host Cloud Foundry endpoint. No other CF instance can be registered unless the instructions in the section 'Enable Endpoints Dashboard to register additional Cloud Foundry endpoints' are followed.
4341
All other deployment methods (helm, docker-compose, docker all-in-one, etc) allow the registration of multiple CF instances by default.
4442

4543
You will then be able to open a web browser and navigate to the console URL:

manifest-docker.yml

+16
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,16 @@
1+
applications:
2+
- name: console
3+
docker:
4+
image: splatform/stratos:stable
5+
instances: 1
6+
memory: 128M
7+
disk_quota: 384M
8+
# services:
9+
# - console_db
10+
# env:
11+
## Override CF API endpoint URL inferred from VCAP_APPLICATION env
12+
# CF_API_URL: https://CLOUD_FOUNDRY_API_ENDPOINT
13+
## Force the console to use secured communication with the Cloud Foundry API endpoint
14+
# CF_API_FORCE_SECURE: true
15+
## Turn on backend debugging
16+
# LOG_LEVEL: debug

0 commit comments

Comments
 (0)