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.

Sign up for GitHub

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

Jump to bottom

#809 - add monitoring_urls to docs #812

Merged
merged 2 commits into from
Jan 14, 2019
Merged

#809 - add monitoring_urls to docs #812

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d3ef1c6
#809 - add monitoring_urls to docs
twardnw Dec 16, 2018
14b6ff8
Merge branch 'master' into 809-monitoring_urls-docs
twardnw Dec 18, 2018
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
6 changes: 6 additions & 0 deletions docs/using_lagoon/lagoon_yml.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,6 +40,9 @@ routes:

environments:
master:
monitoring_urls:
- "www.example.com"
- "www.example.com/special_page"
routes:
- nginx:
- example.com
Expand Down Expand Up @@ -190,6 +193,9 @@ environments:
mariadb: statefulset
```

#### `environments.[name].monitoring_urls`
At the end of a deplpoy, Lagoon will check this field for any URLs which you specify to add to the API for the purpose of monitoring. The default value for this field is the first route for a project. It is useful for adding specific paths of a project to the API, for consumption by a monitoring service. Please note, Lagoon does not provide any direct integration to a monitoring service, this just adds the URLs to the API. On amazee.io, we take the monitoring_urls and add them to our Statuscake account.

## Polysite

In Lagoon, the same git repository can be added to multiple projects, creating what is called a Polysite. This allows you to run the same codebase but allow for different, isolated, databases and persistent files. In `.lagoon.yml` we currently only support specifying custom routes for a polysite project. The key difference from a standard project is that the `environments` becomes the second-level element, and the project name the top level.
Expand Down