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

[Documentation] Expand the current studio page #2581

Closed
ShalokShalom opened this issue Jun 13, 2017 · 2 comments
Closed

[Documentation] Expand the current studio page #2581

ShalokShalom opened this issue Jun 13, 2017 · 2 comments
Assignees
Labels
Documentation Flags an issue / PR for attention by the technical documentation team Type: Chore Issues for general code and infrastructure maintenance
Milestone

Comments

@ShalokShalom
Copy link

ShalokShalom commented Jun 13, 2017

Expand the current studio page: https://www.habitat.sh/docs/concepts-studio/

  1. I think it's senseful to explain the fact, that different studios get created when entered in different places, plus its own pros and cons.

  2. I think it's more useful to create one directory where all plans take place and I create one studio there. Under the line, this is the most KISS solution I can think about. See also this issue here in relation: [Feature] to select from different plans at build #2556

  3. Explain that the studio is a chroot on Linux and a Docker container in OSX/Windows, plus what this means for the users

  4. Explain how to kill a chroot/Docker studio and why

  5. Document baseimage, busybox and stage1, the studio types

@eeyun
Copy link
Contributor

eeyun commented Jun 20, 2017

This issue is very similar in scope to #2585 closing this issue in support of that. Lets bundle the studio documentation issue into a single scoped piece of work.

@reset
Copy link
Collaborator

reset commented Aug 10, 2017

Duplicate of #2882

@reset reset marked this as a duplicate of #2882 Aug 10, 2017
@christophermaier christophermaier added the Type: Chore Issues for general code and infrastructure maintenance label Jul 24, 2020
@christophermaier christophermaier added Documentation Flags an issue / PR for attention by the technical documentation team and removed A-documentation labels Aug 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Documentation Flags an issue / PR for attention by the technical documentation team Type: Chore Issues for general code and infrastructure maintenance
Projects
None yet
Development

No branches or pull requests

5 participants