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
Copy file name to clipboardExpand all lines: SETUP.md
+2-4Lines changed: 2 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,12 +4,10 @@ The infrastructure is managed using Hashicorp Terraform Cloud.
4
4
Deployments are triggered from GitHub Actions workflows.
5
5
6
6
## Setting up your own project
7
-
8
-
### Linode
9
7
* Login to Linode account.
10
8
* Create a personal access token. This secret is the value of "token" input variable of the Terraform module.
11
9
12
-
### Terraform Cloud
10
+
13
11
* Login to Terraform Cloud.
14
12
* Create an organization like "mysite-org".
15
13
* Create a Team Token scoped to owners. This secret is the value of TF_API_TOKEN used by GitHub Actions to authenticate to Hashicorp Terraform Cloud.
@@ -21,7 +19,7 @@ Deployments are triggered from GitHub Actions workflows.
21
19
* In the workspace, create a workspace variable called "token" with the value of the Linode Personal Access Token.
22
20
* Go back to the organization-level variable set you created previously and apply to the workspace specifically.
23
21
24
-
### GitHub
22
+
25
23
* Clone this repository. Name it like "mysite-site-terraform".
26
24
* Create a TF_API_TOKEN repository secret by going to Settings > Secrets and variables > Actions. This secret is used by GitHub Actions to authenticate to Hashicorp Terraform Cloud during runs.
27
25
* Change the values of TF_CLOUD_ORGANIZATION and TF_WORKSPACE in .github/workflows/terraform-apply.yml and .github/workflows/terraform-plan.yml.
0 commit comments