Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/cgenin/tomcat-deploy-web
An webapp for deploying war on tomcat server.
https://github.com/cgenin/tomcat-deploy-web
deploy in js tomcat tool war
Last synced: 4 days ago
JSON representation
An webapp for deploying war on tomcat server.
- Host: GitHub
- URL: https://github.com/cgenin/tomcat-deploy-web
- Owner: cgenin
- Created: 2016-01-25T13:01:07.000Z (almost 9 years ago)
- Default Branch: master
- Last Pushed: 2020-04-29T15:47:06.000Z (over 4 years ago)
- Last Synced: 2024-04-16T10:30:54.511Z (7 months ago)
- Topics: deploy, in, js, tomcat, tool, war
- Language: JavaScript
- Homepage:
- Size: 9.61 MB
- Stars: 1
- Watchers: 1
- Forks: 1
- Open Issues: 12
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Tomcat-web-deploy
This project's purpose is to deploy multiple wars at once on a tomcat webserver instance.
![Main Screen](./public/images/help/Tomcat-Web-Deploy-Main.png)
# Why ?
This product was designed for deploying .war on Tomcat servers.
Why create an tool for this ?
On a mission, my team and me were designated microservices.
The majority of these services were Java web application.
The project had to be continuous delivery for users during the developpement of the main software.No infrastructure was built for test or dev environnement.
A delivery implies multiples .war files.
The current process used by other team was to download all wars,
connect on the server,
stop the server,
copy on the machine the wars and restart...
This was very painfull for one update and all new developpers
must know all the machines and the procedure to do this.One first solution was to use jenkins console to deploy.
One of our problematic was that the continous delivery
doesn't fit to the process for the user's test
(falsy bugs when an artifact deployment was in progress).
The use of the manual jenkins console was grueling to go an item page to another.The creation of this tool was the response of that problematic.
# How ?
# Build and launch the product
``
npm install
````
npm start
````
npm run run-server
``# The libraries
patch : ``npm i -g patch``