User Tools

Site Tools


check_log_configs

Rocketry starts the bash script that calls the python script, because when calling the python script directly from rocketry, an error occurs when executing the deploy process. The deploy process removes the app folder which is what rocketry is programmed to look for. run.sh executes the script via the script path, which when executing the deploy process remains the same.

Any changes to the files that are in the app folder will be automatically updated and executed the next time rocketry runs the task. And changes performed outside the app folder should be deployed to each machine on which the check logs is running.

The manual deployment of files that are outside the app folder is done through the following steps:

1- Open the log file: nohup.out, and check the last time the check log configs was executed. By default, the application runs every 3 hours. If time permits deploy execution without stopping execution, proceed.

2- Stop the application through the PID or as you see fit. ${kill Application_PID}

3- Make the desired deployment or modification.

4- Start the application again. $ nohup python rocketry_run.py &

to activate the Pipenv virtual environment on some servers it is necessary to use the pyenv path:

$ pipenv shell –python /home/picalike/.pyenv/versions/3.10.0/bin/python3

check_log_configs.txt · Last modified: 2024/04/11 14:23 by 127.0.0.1