-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Identify and deliver minimal administration guide, installation guide, and user guide to migrate to che-docs master branch #21264
Comments
why is this a "no"? kubespray, gcp, and azure? I don't think those are supported. AWS is only supported in the context of ROSA afaik @RickJWagner ? I'd remove the whole "running-che-locally" section as that's prone to problems. maybe keep codeready containers if @l0rd agrees ?
|
Re: AWS support: Yes, we support on AWS (outside of ROSA). |
To help map the blog posts to the future Guides, I've added a Guides column to the list of blogs. eclipse-che/blog#19 (comment) It is subject to interpretation / edit by various owners/stakeholders. WDYT @themr0c @l0rd ? |
Created a new issue for contributing and extensions #21286. Cleaned up the description. |
Is your task related to a problem? Please describe
In the che-docs
master
branch, we started a fresh documentation for Che using the Devworkspace engine only.Describe the solution you'd like
We need to migrate docs from the che-docs
master
branch that are still relevant.Describe alternatives you've considered
Blog posts are not covering everything eclipse-che/blog#19
Additional context
STEP 1: Remove obsolete sections considered
STEP 2: Update remaining content
STEP 3: Add new content (not required for v3.0, described in a separate issue)
The text was updated successfully, but these errors were encountered: