-
front 배포과정은 docker로 함
front file들은 dockerfile과 package.json으로 종속성, 의존성 관리를 함
nginx, dockerfile, docker-compose.yml, cicd 파일들을 추가해서 배포 자동화 인프라를 구축했음
nginx 설정은 백엔드와 분리해서 따로 컨테이너를 제작해서 주소입력이 일치할…
-
-
### Describe the Bug
I was able to create a CICD flow to update my local schema an data to my remote instance when I push to my repo, however each time I modify the local data in a specific collect…
-
I am using azd version 1.11.0 to deploy Aspire Project using below mentioned link
`https://learn.microsoft.com/en-us/dotnet/aspire/deployment/azure/aca-deployment-github-actions?tabs=windows&pivots=a…
-
- [ ] #21
- [ ] #18
- [ ] #19
- [ ] #20
-
1. 서버를 도커를 통해 로컬에서 사용, 배포만을 AWS를 사용하여 배포 구성, 검증은 깃 액션을 사용.
2. 서버, 배포 모두 AWS를 사용하여 구성, 검증은 깃 액션을 사용.
- 🔗 [CI/CD pipeline 구축해서 배포 자동화하기](https://mihee0703.tistory.com/45)
- 추가 방안 있을 시 현재 이슈에 답변.
-
Create a repo and some code for a GitHub bot to handle some annoying automation like:
1. Mirroring Milestones between projects to give us a "fake" milestone that spans multiple projects (work around f…
-
-
### New feature motivation
In corporate environments, Git and CICD are defacto standard.
Especially GitLab and GitHub are the most used Services.
Often, there are specific compliance / governance …
-
Currently our bridge e2e tests do not run in CI. This is because of a strange error we were getting some time ago.
- Make sure e2e is running in CI and runs when the label `cicd:bridge` is set