CodeYourFuture / CodeYourFuture/Module-Cloud
[TECH ED] GitHub Actions for Backend
- Lenguaje dominante
- Sin datos de lenguaje
- Estrellas
- 0
- Forks
- 6
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Descripción
### Link to the coursework
https://docs.github.com/en/actions
### Why are we doing this?
## Setup Github Actions for CYF Hotel Backend deployments to EC2
**Create GitHub Actions Workflow File:** Similar to the frontend, create a new YAML file in your CYF Hotel repository under .github/workflows, and name it appropriately, like backend-ec2-deploy.yml.
**Configure AWS and SSH Credentials:** Store your AWS and SSH credentials securely using GitHub Secrets. These will be used to authenticate and connect to your EC2 instance.
**Write EC2 Deployment Steps:** Outline the steps in the YAML file for SSHing into your EC2 instance, pulling the latest code, and restarting your backend service.
**Test the Workflow:** Like with the frontend, push a change to your repository or manually trigger the workflow from GitHub Actions to ensure that your backend is successfully deployed to the EC2 instance.
### Maximum time in hours
4
### How to get help
Ask calm, curious questions with links, code samples, and no screenshots.
https://curriculum.codeyourfuture.io/guides/asking-questions/
### How to submit
In this advanced module you will demo your work. You may wish to make notes for case studies to add to your portfolio.
Guía de contribución
Línea de trabajo
Lee el material del curso sobre GitHub Actions en https://docs.github.com/en/actions e inspecciona el workflow de frontend comparable. Crea .github/workflows/backend-ec2-deploy.yml, configura los GitHub Secrets necesarios de AWS y SSH, y define los pasos para conectarte por SSH a EC2, obtener el código más reciente y reiniciar el servicio backend. La tarea estará terminada cuando un push o un trigger manual despliegue correctamente el backend.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- aws, github-actions, yaml
- Área
- backend, cloud, devops, infrastructure
- Tipo de issue
- Nueva funcionalidad
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Estancado
- Claridad
- Bastante claro
- Aptitud para principiantes
- 30/100