Plantly Docs

Plantly Docs

  • Docs
  • API
  • Help
  • Blog

componentDescription

Component description

Backend scheme

Disclaimer: done on the lecture material, so the component diagram follows the example given in https://olegpahhomov.gitlab.io/iti0203-2020/iti0203-2020-project/

The application is composed on two parts: front and back-end. Both of them are stored in gitlab in different repositories. For both a gitlab runner in aws instance is applied. For the backend, if in the repo a push is made then code is sent through gitlab runner to aws instance where it is built and tested. if merging to main branch is chosen in gitlab, code, sent with gitlab runner is built, tested and deployed for serving. Backend is served in aws by docker-compose using external configuration set in external.yml. For monitoring Spring Boot Actuator can be viewed at port 9000.

Front end follows the similar approach however in this case each push to the repository ends with the code to be built and deployed in the aws instance. The deployed version of the frontend is served through the nginx server to the user.

The application is monitored by Zabbix situated on separate server at http://13.53.140.245/ (access: username: admin; password: zabbix)

Updated: 21.11.2020

Plantly Docs
Docs
Getting Started (or other categories)Guides (or other categories)API Reference (or other categories)
Community
User ShowcaseStack OverflowProject ChatTwitter
More
BlogBuilt by GitLab PagesDocusaurus on GitHubStar
Facebook Open Source
Copyright © 2021 GitLab