Skip to content

catduckgnaf/hope-trust

Folders and files

NameName
Last commit message
Last commit date

Latest commit

Nov 21, 2023
5dd086c Β· Nov 21, 2023

History

1 Commit
Nov 21, 2023
Nov 21, 2023
Nov 21, 2023
Nov 21, 2023
Nov 21, 2023

Repository files navigation

Coverage

Codacy Badge

Production Client

buddy pipeline

Production Server

buddy pipeline

HopePortalServices

  • Clone the repository
  • Login to Serverless service serverless login

Deployments

Environments: Development, Staging, Production

sls = serverless // shorthand command

β€”-force // force an action to occur

Usage:

sls remove --stage dev --force sls client remove --stage dev --force

Deployment commands

sls deploy // deploy full service for default stage

sls deploy β€”-stage ${stage_name} // deploy full service of a specific stage

sls client deploy // deploy full client of default stage (default: development)

sls client deploy --stage ${stage_name} // deploy full client of a specific stage

Removal commands

sls remove // remove full service for default stage (default: development)

sls remove β€”-stage ${stage_name} // remove full service of a specific stage

sls client remove // remove full client of default stage (default: development)

sls client remove β€”-stage ${stage_name} // remove full client of a specific stage

Usage:

Deploy API to the development S3 Bucket and Serverless environment

sls deploy --stage development

Deploy Client to the development S3 Bucket and Serverless environment

sls client deploy --stage development

Remove development Client S3 Bucket and Serverless environment from Northern Virginia Region

sls client remove --stage development --region us-east-1

Remove development Server S3 Bucket and Serverless environment

sls remove --stage development

Development Flow

  1. Local Branch
  2. Feature or Hot Fix Branch (ie: features/hope-101 or hot-fix/hope-97)
  3. πŸ’» Development
  4. βœ… Review & Approve
  5. πŸ”Ž Staging
  6. βœ… Review & Approve
  7. :shipit: Production

Slack Commands:

Running any pipeline will trigger its subsequent pipelines and approval process

For example running the Development Client will trigger the Staging approval process, etc..

Run Development Client Deployment Pipeline

/client-development

Run Production Client Deployment Pipeline

/client-production

Run Staging Client Deployment Pipeline

/client-staging

Run Development Server Deployment Pipeline

/server-development

Run Production Server Deployment Pipeline

/server-production

Run Staging Server Deployment Pipeline

/server-staging

Run Development Client Deployment Pipeline for Github branch features/hope-210

/client-development run features/hope-210

Run Development Server Deployment Pipeline for Github branch hot-fix/hope-333

/server-development run hot-fix/hope-333

Working:

git checkout -b features/hope-42 development // checkout new feature branch off of development branch
git add ${file or folder path | . to stage all branch changes}
git commit -m "A new feature for the frontend" // Add commit message
git push -u origin features/hope-42 // push new branch to remote

Pull request to development Branch

Pull requests should have:
  • Title hope-22 - Add new button to specific widget
  • Description Should contain bullet points of work completed
  • Label Frontend, Junior, CSS, Javascript
  • Reviewers Be assigned to a competent engineer for review

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages