You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Configure a Continuous Integration or Continuous Deployment system (CI/CD) to automatically deploy a new version of an app to production/development when a branch is pushed or workflow triggered.
7
7
8
-
This guide sets up a CI/CD system using GitHub Actions and Cerebriums' Service Accounts.
8
+
This guide sets up a CI/CD pipeline using GitHub Actions and Cerebriums' Service Accounts.
9
9
10
-
> Maintaining **separate development and production apps** in separate projects is recommended, so that changes can be safely tested before going live.
10
+
<Note> Maintaining **separate development and production apps** in separate projects is recommended, so that changes can be safely tested before going live.</Note>
11
11
12
12
### 1. Authenticating to Cerebrium
13
13
@@ -41,7 +41,7 @@ GitHub Actions use workflow files located in the `.github/workflows/` directory
41
41
2. Within that directory, create a new file named `cerebrium-deploy.yml`
42
42
3. Paste the following YAML into the file:
43
43
44
-
```
44
+
```yaml
45
45
name: Cerebrium Deployment
46
46
on:
47
47
push:
@@ -83,9 +83,9 @@ jobs:
83
83
84
84
```
85
85
86
-
Once committed, this workflow will automatically:
86
+
Once committed, this workflow will automatically:
87
87
88
-
- Deploy a production application on every push to master
89
-
- Deploy a development app on pull requests to master or development it.
88
+
- Deploy a production application on every push to master.
89
+
- Deploy a development app on pull requests to master or development branches.
90
90
91
-
You can monitor workflow runs in the “Actions” tab of your repository.
91
+
Monitor workflow runs in the “Actions” tab of the repository on GitHub.
0 commit comments