-
Notifications
You must be signed in to change notification settings - Fork 11
can we update the README.adoc if on OSIO? #46
Comments
Adding @rhoads-zach to the issue |
thanks @gastaldi. @jstrachan I can add the content, but i need to see the boosters running in osio/che. Do you all still need to add the che stack info/config to the boosters? or can they run as-is? |
@rhoads-zach thanks! the spring boot / vertx REST / configmap / health check boosters should run as is. (The CRUD / CircuitBreakers / WF Swarm ones don't run AFAIK) - we setup the Che stack correctly in the new project wizard (or import wizard) |
@jstrachan I know it's off topic here, but FYI, Swarm boosters will work after fabric8io/fabric8-team-components#122 is available on OSIO and Swarm 2017.9.0 is released and boosters updated (we had to workaround a JBoss Modules issue in Swarm). I only tested the basic REST booster, but will look at the other boosters this week. |
@Ladicek thanks! I hope to be able to test that soon |
Just extracted the Readme template into a protected method which can be overriden in the OSIO addon: 5f3e5ad |
awesome thanks! |
I wonder how hard it'd be to update the
ReadmeProcessor
to generate nicer docs that are more suitable to OSIO?e.g. there's no real docs in this generated quickstart thats of any relevance to using OSIO - which should focus on using Che to edit/run/debug then Jenkins CI / CD for CI + PRs and CD for versioned releases - and only after all that even mention stand alone (and am not sure it even should really - it'll just add confusion?)
The text was updated successfully, but these errors were encountered: