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.

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

User guide - Customizing workspaces' containers (and other components) #21297

Closed
l0rd opened this issue Mar 23, 2022 · 2 comments
Closed

User guide - Customizing workspaces' containers (and other components) #21297

l0rd opened this issue Mar 23, 2022 · 2 comments
Assignees
Labels
area/doc Issues related to documentation kind/enhancement A feature request - must adhere to the feature request template. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. severity/P1 Has a major impact to usage or development of the system.

Comments

@l0rd
Copy link
Contributor

l0rd commented Mar 23, 2022

Is your enhancement related to a problem? Please describe

User Guide needs to be updated (global issue). This issue is about the creation of a new "Customizing workspaces' containers (and other components)" section.

Describe the solution you'd like

We should explain what a Devfile is, how Che uses it (we recommed to version it in git) and link to the related documentation.

We should provide information on how to prepare an container image to be used in a Che workspace:

  • The entrypoint should be non terminating
  • Ready to run as an arbitrary user
  • A nice terminal experience ($PS1, $HOME, ...)
  • Some dedicated folders may be overridden (automouted git credentials, tokens, certs)

We should explain what should not be specified in a Devfile: infrastructure related, user related, IDE related configurations are not supposed to be in a Devfile.

We should cover attributes that are handled by Che/DevWorkspace but are not part of the Devfile spec.

We should specify how ports that need to be exposed or not can be defined to avoid pop-ups all the way.

@l0rd l0rd added the kind/enhancement A feature request - must adhere to the feature request template. label Mar 23, 2022
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Mar 23, 2022
@l0rd l0rd added area/doc Issues related to documentation severity/P1 Has a major impact to usage or development of the system. and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Mar 23, 2022
@pmkovar
Copy link

pmkovar commented May 11, 2022

@che-bot
Copy link
Contributor

che-bot commented Dec 4, 2022

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 4, 2022
@nickboldt nickboldt removed the team/doc label Dec 9, 2022
@che-bot che-bot closed this as completed Dec 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/doc Issues related to documentation kind/enhancement A feature request - must adhere to the feature request template. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. severity/P1 Has a major impact to usage or development of the system.
Projects
None yet
Development

No branches or pull requests

5 participants