Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix broken internal links #45

Merged
merged 1 commit into from
Jul 6, 2017
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion source/documentation/deploying_apps/deploying_django.md
Original file line number Diff line number Diff line change
Expand Up @@ -90,7 +90,7 @@ If you are just getting started learning CloudFoundry, you can use the sandbox s

The `memory` line tells the PaaS how much memory to allocate to the app.

1. If your app requires a database, [create a PostgreSQL backing service and bind it to your app](/#postgresql). Then see the section on [PostgreSQL setup]() below.
1. If your app requires a database, [create a PostgreSQL backing service and bind it to your app](/#using-postgresql). Then see the section on [PostgreSQL setup](/#postgresql-setup-with-django) below.

1. To push your app, do:

Expand Down
2 changes: 1 addition & 1 deletion source/documentation/deploying_apps/deploying_node_js.md
Original file line number Diff line number Diff line change
Expand Up @@ -68,7 +68,7 @@ See [Tips for Node.js Applications](https://docs.cloudfoundry.org/buildpacks/nod

If your app depends on a backing service such as PostgreSQL, it will need to parse the `VCAP_SERVICES` environment variable to get required details, such as service URLs and credentials.

You must create the service and bind it to your Node.js app as described in the [Deploy a backing service](/#deploy-a-backing-service) section.
You must create the service and bind it to your Node.js app as described in the [Deploy a backing service](/#deploy-a-backing-or-routing-service) section.

You can use the [cfenv](https://www.npmjs.com/package/cfenv) module to assist with parsing the environment variables.

Expand Down
4 changes: 2 additions & 2 deletions source/documentation/deploying_apps/deploying_rails.md
Original file line number Diff line number Diff line change
Expand Up @@ -111,8 +111,8 @@ Note that the only database service currently supported by PaaS is PostgreSQL. I
where VARIABLE is a unique name for the variable, and `value` is the value to set.


1. [Create a PostgreSQL backing service (if required) and bind it to your app](/#postgresql).
1. [Create a PostgreSQL backing service (if required) and bind it to your app](/#using-postgresql).

To enable Rails support for database migrations, you may wish to create a `Procfile` in the same directory as your `manifest.yml` and `Gemfile`. The `Procfile` is a way to specify commands to be run when deploying your app.

This is a minimal example of the `Procfile` content for *Rails 5.0*:
Expand Down
2 changes: 1 addition & 1 deletion source/documentation/deploying_services/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ Many 12-factor applications rely on backing services such as a database, an emai

In Cloud Foundry, backing and routing services are referred to as 'services' and are available through the Cloud Foundry ``cf marketplace`` command.

Currently, the only services available in the marketplace are the backing [PostgreSQL database service](/#postgresql) and [MySQL database service](/#mysql).
Currently, the only services available in the marketplace are the backing [PostgreSQL database service](/#using-postgresql) and [MySQL database service](/#using-mysql).

Each service in the marketplace can have multiple plans available. For example, there are different PostgreSQL plans which vary by availability, storage capacity and encryption.

Expand Down
2 changes: 1 addition & 1 deletion source/documentation/deploying_services/postgres.md
Original file line number Diff line number Diff line change
Expand Up @@ -160,7 +160,7 @@ Backups are taken nightly at some time between 22:00 and 06:00 UTC. Data is reta

There are two ways you can restore data to an earlier state:

1. You can restore to the latest snapshot yourself. See [Restoring a PostgreSQL service snapshot](#restoring-a-postgresql-service-snapshot) for details.
1. You can restore to the latest snapshot yourself. See [Restoring a PostgreSQL service snapshot](#restoring-a-postgresql-service-snapshot-experimental) for details.

2. We can manually restore to any point from 5 minutes to 7 days ago, with a resolution of one second. Data can be restored to a new PostgreSQL service instance running in parallel, or it can replace the existing service instance.

Expand Down
2 changes: 1 addition & 1 deletion source/documentation/deploying_services/route_services.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ Tenants can define their own Route Service instance by using a [User-Provided Se
- It must be a HTTPS endpoint with a valid certificate.
- It can be a application running in the platform itself or an external service on the Internet.
- It must be reachable from the platform (ie. not blocked by a firewall or in a private network).
- It must implement the [Route Service Protocol](/#route-service-protocol)
- It must implement the [Route Service Protocol](/#implementing-a-route-service)

This is how you define a User-Provided Route Service Instance and map it to the route of your app:

Expand Down