-
Notifications
You must be signed in to change notification settings - Fork 154
docs: more language refresh #556
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
base: master
Are you sure you want to change the base?
Conversation
7137d66
to
2aa8720
Compare
Signed-off-by: Mathias Bogaert <[email protected]>
2aa8720
to
95dc356
Compare
This is covering a lot of files, will review later. Considering this low priority. If there are smaller changes that you think are critical then please break them out into smaller PRs. |
|
||
Pipelines, builds, and all other user data are owned by \italic{teams}. A team | ||
is just a conceptual owner and a separate namespace, tied to an authorization | ||
config. For example, a team may authorize all members of the \code{concourse} | ||
is simply a conceptual owner and separate namespace, tied to an authorization |
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.
is BOTH a conceptual owner and separate namespace
cluster. | ||
|
||
In the future, we'll probably have this as a flag on a team, indicating | ||
In the future, we'll likely add this as a flag on a team, indicating |
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 future, we plan on adding this
sensitive information. | ||
|
||
This can be remedied with configuration specified on Garden to restrict | ||
access to the internal network, but this is not detailed in our docs, and | ||
we'll probably want to find a better answer than configuration in the | ||
future. | ||
we'll likely want to find a better solution in the future. |
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.
we're actively considering better approaches to this problem.
|
||
\codeblock{bash}{{ | ||
$ fly -t example intercept powershell | ||
}} | ||
} | ||
|
||
Containers are around for a short time after a build finishes in order to | ||
allow people to intercept them. | ||
Containers remain available for a short time after a build finishes to |
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.
Do we know how long? Is it configurable?
are looking to extend the capabilities of managing a Concourse deployment. For | ||
users that are new to these concepts, we do recommend learning how to set up | ||
users who are new to these concepts, we recommend learning how to set up |
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.
Repetition of "users who"
No description provided.