Closed SanjulaGanepola closed 2 months ago
I see right now this script runs on workflow_dispatch
. Can we make it so the new server is deployed to OSSBUILD and started whenever we merge into the main branch?
I see right now this script runs on
workflow_dispatch
. Can we make it so the new server is deployed to OSSBUILD and started whenever we merge into the main branch?
I had the same thought. We could (should?) deploy the releases to the default port and main branch onto a separate port and install dir.
I would normally write a separate action for that, but how hard is it to condition this one? Probably not worth the trouble....
Good idea. I put it in both workflows since it was the quickest solution. Can look into moving it into one later on. Here is the updated strategy:
/opt/download/release
/opt/mapepire/release
mapepire (Mapepire Server)
on port 8076
/opt/download/dev
/opt/mapepire/dev
mapepired (Mapepire Development Server)
on port 8075
Zip dist CI
from creating a zip of a zip as the build artifact
Changes
Automatically deploy mapepire server to
OSSBUILD
on release. This will help ensure that our client test workflows are running against the latest release.@ThePrez @worksofliam I don't have access to the settings, so can you add the following environment secrets:
OSSBUILD
environmentIBMI_HOST
IBMI_USER
IBMI_PASSWORD
IBMI_SSH_PORT