-
Notifications
You must be signed in to change notification settings - Fork 5
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.
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
adding fork and begin shuffle text #12
base: main
Are you sure you want to change the base?
Conversation
This looks good. you don't need to clone it down though, you can point kustomize right at the url like the original |
@@ -2,8 +2,13 @@ | |||
|
|||
* We have a Kustomization that we can use to easily get it up and running | |||
|
|||
Clone the repository for the `kustomization.yaml`. | |||
```execute-2 | |||
git clone https://github.com/springone-tour-2021/docker-services.git |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Like @tybritten said this is not necessary
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the lab from March we had them clone the original and look at the file I was trying to keep the disect petclinic
part that does that and use the files at the same time. We can have them clone the original repo. I was thinking to put the original as a reference for those that want to repeat locally if we go with the fork.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should just stick to referencing the fork throughout the workshop
No description provided.