Open syphax-bouazzouni opened 1 year ago
Documentation from https://github.com/ncbo/bioportal_web_ui/blob/08f4ce636893e32dc3435042f28ad293bf5aed11/.github/workflows/deploy.yml
# Workflow to deploy OntoPortal UI to stage/prod systems
#
# Required github secrets:
#
# CONFIG_REPO - github repo containing config and customizations for UI. Format 'author/private_config_repo'
# it is used for getting capistrano deployment configuration for stages on the github actions runner and
# PRIVATE_CONFIG_REPO env var is constructed from it which is used by capistrano on the UI hosts for pulling configs.
#
# GH_PAT - github Personal Access Token for accessing private config repo
#
# SSH_JUMPHOST - ssh jump/proxy host though which deployments have to though if UI nodes live on private network.
#
# DEPLOY_ENC_KEY - key for decrypting deploymnet ssh key residing in config/
# this SSH key is used for accessing jump host, UI nodes, and private github repo.
Context
Currently, we are using our own scripts to do our deployments, the source code can be found here https://gite.lirmm.fr/jonquetlab/ontoportal_deploy_scripts.
Why do we don't use the original scripts in the appliance? the problem was that they were working only if we use the source code of NCBO and use the configuration files that are inside the appliance.
In September 2022, Alex from Stanford did pull requests to add GitHub actions to deploy our code each time we push code to GitHub.
Requirements
stage
and configure the action to deploy to Stageportaldevelopment
to Testportalmaster
to SIFR Bioportal and Agroportal