George Gastaldi

@VeerMuchandi I can change in the launcher-backend, but the boosters will have to be forked and changed to support the newly-created `SOURCE_REPOSITORY_NAME` parameter in https://github.com/fabric8-launcher/launcher-backend/issues/385. Given the time constraint, you'll...

@VeerMuchandi I merged https://github.com/fabric8-launcher/launcher-backend/issues/385, can you give it a try by using it in a forked version of the `wf-swarm-rest-http` booster for example? I can give you further instructions to...

@VeerMuchandi yes, as long as you keep the `fabric8/launcher-backend:latest` image tag in the template (BACKEND_IMAGE and BACKEND_IMAGE_TAG parameters)

That is the GitHub repository name taken from the SOURCE_REPOSITORY_URL used (the repository URL where the deployed booster lives) Em Sex, 4 de mai de 2018 16:34, VeerMuchandi escreveu: >...

>I just noticed the 'Try out the Beta version' link, this new wizard version does take an application name as input. Yes, this is the OpenShift project name, we probably...

> Should we rename this parameter SOURCE_REPOSITORY_NAME to APPLICATION_NAME instead? Ultimately I think we could use the application name (project name) that was specified when the wizard starts instead (right...

@VeerMuchandi @petenorth sorry, I think I wasn't clear in my previous comment. I mean that in the UI the Application Name asked when you enter the wizard would be used...

Yes, images always come from a registry. There isn't a file representing the image afaik.

@alrubinger it would be possible, but I don't think that's commonly used among developers

Where can we find the technical instructions on how to do that?