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

make it possible to use custom codenvy images like for codenvy saas #1162

Closed
riuvshin opened this issue Nov 16, 2016 · 5 comments
Closed

make it possible to use custom codenvy images like for codenvy saas #1162

riuvshin opened this issue Nov 16, 2016 · 5 comments
Assignees
Milestone

Comments

@riuvshin
Copy link

riuvshin commented Nov 16, 2016

Today in dockerized codenvy we support only codenvy/codenvy docker image aka codenvy onprem. But to use dockerized codenvy internally for development and put it to our dev/acceptance servers we should add possibility to switch between codenvy images somehow. For saas we have separate packaging and I (@riuvshin) can help with setting up docker image for codenvy saas packaging.
so here is some goals:

  • dev mode should work with both codenvy onprem and codenvy saas packagings and switching between them must be really easy with CLI
  • saas image must be same way respected during updates and version checks
  • it seems we will need nightly and latest images for both packagings too

@TylerJewell I think it will require your help on that also.

@TylerJewell
Copy link
Contributor

We should wait for the consolidation of the codenvy cli and Che cli to be finished first. We can create a custom assembly abstraction so the same cli can work for Che, codenvy onprem, saas and artik without constant reconfigure.

@riuvshin
Copy link
Author

riuvshin commented Nov 16, 2016

@TylerJewell You are right. btw here I've created PR: https://github.com/codenvy/customer-saas/pull/82 which sync customer saas project with onrem which will allow use it dockerized.

@benoitf
Copy link
Contributor

benoitf commented Dec 15, 2016

is this issue could be closed now ?

@TylerJewell
Copy link
Contributor

+1

1 similar comment
@riuvshin
Copy link
Author

+1

@benoitf benoitf added this to the 5.0.0-M9 milestone Dec 15, 2016
@benoitf benoitf closed this as completed Dec 15, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants