UI services: Difference between revisions

From acumen Wiki
Jump to navigation Jump to search
(Created page with "Integral to the application is the service that renders the UI to users via the web browser - internally known as flask-app.")
 
No edit summary
Line 1: Line 1:
Integral to the application is the service that renders the UI to users via the web browser - internally known as flask-app.
Integral to the application is the service that renders the UI to users via the web browser - internally known as flask-app.
=== Checking the container status ===
* Start an ssh session to the relevant application server;
* At the prompt, type the following commands:
# <code><user>@acumen-app-server:~$ cd ~/dockerise/</code>
# <code><user>@acumen-app-server:~$ docker ps | grep "STATUS\|mysql"</code>
The program will output information about the status of the container.
=== Container logging ===
Where an issue with the database container has been observed then the Administrator should check the logs:
* Start an ssh session to the relevant application server;
* At the prompt, type the following commands:
# <code><user>@acumen-app-server:~$ cd ~/dockerise/</code>
# <code><user>@acumen-app-server:~$ docker-compose logs -f flask-app"</code>
This action will stream the logs to the terminal; observing this output for a short time should provide some indications to any potential issues.
Press [CTRL+C] to stop the logging output and return to the prompt.
=== Starting the container ===
If the container is Down - then the following commands will bring the container back up:
# <code><user>@acumen-app-server:~$ cd ~/dockerise/</code>
# <code><user>@acumen-app-server:~$ docker-compose up -d flask-app"</code>

Revision as of 12:32, 7 July 2020

Integral to the application is the service that renders the UI to users via the web browser - internally known as flask-app.

Checking the container status

  • Start an ssh session to the relevant application server;
  • At the prompt, type the following commands:
  1. <user>@acumen-app-server:~$ cd ~/dockerise/
  2. <user>@acumen-app-server:~$ docker ps | grep "STATUS\|mysql"

The program will output information about the status of the container.

Container logging

Where an issue with the database container has been observed then the Administrator should check the logs:

  • Start an ssh session to the relevant application server;
  • At the prompt, type the following commands:
  1. <user>@acumen-app-server:~$ cd ~/dockerise/
  2. <user>@acumen-app-server:~$ docker-compose logs -f flask-app"

This action will stream the logs to the terminal; observing this output for a short time should provide some indications to any potential issues.

Press [CTRL+C] to stop the logging output and return to the prompt.

Starting the container

If the container is Down - then the following commands will bring the container back up:

  1. <user>@acumen-app-server:~$ cd ~/dockerise/
  2. <user>@acumen-app-server:~$ docker-compose up -d flask-app"