Permalink
Browse files

Merge pull request #508 from amazeeio/docs

Fixing small things on the documentation
  • Loading branch information...
dasrecht committed Jul 17, 2018
2 parents 68375fa + 36974e3 commit 8e7d5cb095969477818de2d1fc9fb47a536f96aa
Showing with 3 additions and 2 deletions.
  1. +1 −1 docs/index.md
  2. +1 −1 docs/using_lagoon/backups.md
  3. +1 −0 mkdocs.yml
View
@@ -15,7 +15,7 @@ Lagoon solves what developers are dreaming about: A system that allows developer
## Help?
Questions? Ideas? Meet the maintainers and contributors: `#lagoon` in amazee.io RocketChat [https://amazeeio.rocket.chat]()
Questions? Ideas? Meet the maintainers and contributors: `#lagoon` in amazee.io RocketChat [https://amazeeio.rocket.chat](https://amazeeio.rocket.chat)
## A couple of things about Lagoon
1. Lagoon is based on microservices. A whole deployment and build workflow is very complex; not only do we have multiple sources (like Github, Bitbucket, Gitlab, etc.), multiple OpenShift servers and multiple notification systems (Slack, Rocketchat, etc.), but each deployment is unique and can take from seconds to hours. So it's built with flexibility and robustness in mind. Having microservices that all communicate through a messaging system (RabbitMQ) allows us to scale individual services up and down, survive down times of individual services and also to try out new parts of Lagoon in production without affecting others.
@@ -1,6 +1,6 @@
# Backups
Lagoon differentiates between three backup solutions: Short-, Mid- and Long-Term Backups.
Lagoon differentiates between three backup categories: Short-, Mid- and Long-Term Backups.
## Short-Term Backups
View
@@ -18,6 +18,7 @@ pages:
- Workflows: using_lagoon/workflows.md
- Backups: using_lagoon/backups.md
- Logging: using_lagoon/logging.md
- Remote Shell: using_lagoon/remote_shell.md
- GraphQL API: using_lagoon/graphql_api.md
- Drupal:
- Lagoonize: using_lagoon/drupal/lagoonize.md

0 comments on commit 8e7d5cb

Please sign in to comment.