Skip to content

Latest commit

 

History

History
109 lines (70 loc) · 1.84 KB

README.md

File metadata and controls

109 lines (70 loc) · 1.84 KB

The API part of the ZooProcess project.

Install

npm run deps && npm i

Run

npm start

docker

build

docker build -t zooprocess-back .

run

docker run -p 8081:8081 --name zooprocess-back zooprocess-back

DB

need mongo:5.0.26-focal the better way is to use docker-compose for this purpose.

Deployement

Deployment Steps Create a deployment package:

deploy.sh:

# Create a deployment directory
mkdir -p deploy

# Copy necessary files
cp -r dist deploy/
cp app.js deploy/
cp package.json package-lock.json deploy/
cp zooprocess.openapi.yaml deploy/

# Create a production .env file (don't copy your development one directly)
cp .sample.env deploy/.env
# Edit the .env file with production values

Transfer to your web server using SCP, SFTP, or your preferred method:

scp -r deploy/* user@your-server:/path/to/application/

On the server:

cd /path/to/application
npm install --production  # Installs only dependencies, not devDependencies
node app.js  # Or use a process manager like PM2

Using a Process Manager (Recommended) For production deployments, I recommend using a process manager like PM2:

Install PM2 globally on your server

npm install -g pm2

Start your application

pm2 start app.js --name "zooprocess-api"

Make PM2 startup on server reboot

pm2 startup
pm2 save

Docker Deployment (Alternative)

Since you have a Dockerfile, you could also build and deploy as a Docker container:

Build the Docker image

docker build -t zooprocess-api .

Run the container

docker run -d -p 8081:8081 --env-file .env --name zooprocess-api zooprocess-api

This approach is cleaner as it packages everything together and ensures consistent environments.

Would you like more specific instructions for any of these deployment methods?