|
|
@ -1,19 +1,20 @@ |
|
|
|
**service-updater** - Script for upgrading java/play application from git |
|
|
|
**java-app-updater** - Script for upgrading java/play application from git repository |
|
|
|
|
|
|
|
|
|
|
|
## Description |
|
|
|
# Description |
|
|
|
|
|
|
|
|
|
|
|
Scenario upgrade java/play application in production directory |
|
|
|
This script upgrades java/play application. |
|
|
|
|
|
|
|
|
|
|
|
## Requirements |
|
|
|
**NB:** I would now consider this scenario as an example of the implementation |
|
|
|
|
|
|
|
of a software update process, but in practice I would use configuration |
|
|
|
|
|
|
|
management systems and deployment tools. |
|
|
|
|
|
|
|
|
|
|
|
CentOS: yum -y install python-pip |
|
|
|
# License |
|
|
|
Debian: apt-get install python-pip |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
pip install configparser |
|
|
|
[GNU General Public License v3.](https://www.gnu.org/licenses/gpl-3.0.html) |
|
|
|
|
|
|
|
|
|
|
|
## Usage |
|
|
|
# Usage |
|
|
|
|
|
|
|
|
|
|
|
service.py [service] <start|stop|restart|build|update|upgrade> |
|
|
|
service.py [service] <start|stop|restart|build|update|upgrade> |
|
|
|
|
|
|
|
|
|
|
|
start - Start service |
|
|
|
start - Start service |
|
|
|
stop - Stop service |
|
|
|
stop - Stop service |
|
|
@ -22,6 +23,7 @@ service.py [service] <start|stop|restart|build|update|upgrade> |
|
|
|
update - Update current service from repository |
|
|
|
update - Update current service from repository |
|
|
|
upgrade - Update developing service from repository |
|
|
|
upgrade - Update developing service from repository |
|
|
|
|
|
|
|
|
|
|
|
To build a specific service you need to pass a parameter [service]: |
|
|
|
To build the specific service you need to pass a parameter [service]: |
|
|
|
./service.py application build all |
|
|
|
|
|
|
|
|
|
|
|
$ service.py application build all |
|
|
|
|
|
|
|
|
|
|
|