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: README.md
+4-6Lines changed: 4 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -87,17 +87,15 @@ create_vm = true
87
87
```
88
88
and re-apply terraform: `terraform apply -var-file=var.tfvars`.
89
89
90
-
This will create the VPS and required roles.
90
+
This will create the VPS and required managed identities.
91
91
92
-
Use `proxy-vps` to proxy all network requests through the vps with sshuttle. sshuttle will likely ask for a sudo password.
92
+
`bin/rake test_azure_vm` and `bin/rake test_app_service` will establish a VPN connection to the VM or App service container and run the test suite. You might be prompted for a sudo password when the VPN starts (sshuttle).
93
93
94
-
Then use `bin/rake test_entra_id` to run the tests with Entra ID.
95
-
96
-
After you are done, running terraform again without the var file (`terraform apply`) it should destroy the VPS.
94
+
After you are done, run terraform again without the var file (`terraform apply`) to destroy the VPS and App service application.
97
95
98
96
#### Cleanup
99
97
100
-
Some test copied over from Rails codebase don't clean after themselves. A rake task is provided to empty your containers and keep cost low: `bin/rake flush_test_container`
98
+
Some tests copied over from Rails don't clean after themselves. A rake task is provided to empty your containers and keep cost low: `bin/rake flush_test_container`
0 commit comments