Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fixing Github Actions folder name on README.md #11

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

fixing Github Actions folder name on README.md #11

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions 4. Projects/3. Microservices/Problem/Stage 2/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -148,7 +148,7 @@ Before we talk about continuous deployment let's setup continuous integration.

Specifically, we will add a GitHub Actions workflow that builds and tests your code before it is merged into master.

Copy over the `.github/workflow/prod.yml` file to your repository.
Copy over the `.github/workflows/prod.yml` file to your repository.

This file defines the workflow. Let's go through it:

Expand Down Expand Up @@ -211,7 +211,7 @@ Finally we build and test the app.

![Github Actions](gh_actions.png)

After adding `.github/workflow/prod.yml` to your repository and pushing the changes up to master, you should see your workflow execute.
After adding `.github/workflows/prod.yml` to your repository and pushing the changes up to master, you should see your workflow execute.

### Step 3 (Optional)

Expand Down Expand Up @@ -253,7 +253,7 @@ To setup continuous deployment follow these steps:

Next we will update our GitHub workflow to deploy the app anytime changes are pushed to master.

Copy over `.github/workflow/prod.yml` to your repository. Notice that now the workflow only runs when changes are pushed to master (not when creating PRs).
Copy over `.github/workflows/prod.yml` to your repository. Notice that now the workflow only runs when changes are pushed to master (not when creating PRs).

Let's review the rest of the changes:

Expand Down Expand Up @@ -322,7 +322,7 @@ To setup continuous deployment follow these steps:

5. Update Github Secrets & Variables

You may have noticed that the new `.github/workflow/prod.yml` file has some variables in it (ex: `vars.DROPLET_IP` and `secrets.DROPLET_PASSWORD`). These secrets & variables will need to be defined inside your GitHub repo for the workflow to succeed.
You may have noticed that the new `.github/workflows/prod.yml` file has some variables in it (ex: `vars.DROPLET_IP` and `secrets.DROPLET_PASSWORD`). These secrets & variables will need to be defined inside your GitHub repo for the workflow to succeed.

Secrets are encrypted variables that you can create for a repository. Secrets are available to use in GitHub Actions workflows.

Expand All @@ -345,7 +345,7 @@ To setup continuous deployment follow these steps:

![Github Variables](gh_variables.png)

After adding these secrets/variables you should be able to push your updated `.github/workflow/prod.yml` file to the `master` branch and have your project automatically deployed.
After adding these secrets/variables you should be able to push your updated `.github/workflows/prod.yml` file to the `master` branch and have your project automatically deployed.

6. Check droplet

Expand Down