I've not used lets-encrypt for Wave, but I've used it to automate the
creation of a Docker Registry server.
See here:
https://github.com/odoko-devops/uberstack/tree/master/apps/registry
Upayavira
On Thu, 8 Dec 2016, at 03:13 AM, Evan Hughes wrote:
> Gonna see if I can setup a demo server and tr
We really need to improve our docs, like reeaaalllyyy need to.
On Thu, 8 Dec 2016 at 21:40 Upayavira wrote:
> I've not used lets-encrypt for Wave, but I've used it to automate the
> creation of a Docker Registry server.
>
> See here:
> https://github.com/odoko-devops/uberstack/tree/master/apps/r
Hey all,
Wanting to grab the oppions of the community on whether we stick to an
uberjar/shadowjar/box of magic or extend our script to put the dependencies
on the path and then run the wave jar.
This shouldn't change any functionality but since we are cleaning up some
of the build logic I thought
I have some experience using onejar archives for deployment. It mostly
worked but we had some issues. it doesn't work well with AOP - in our case
we had issues using it with AppDynamics and Kamon. Also, it makes it hard
to access configuration files since they are wrapped twice in jars. I guess
tha
Pablo,
Thanks for this. It seems to have fixed my debugging issues for now anyway.
Cheers,
Darin
> On Dec 6, 2016, at 6:29 AM, pablojan wrote:
>
> GitHub user pablojan opened a pull request:
>
>https://github.com/apache/incubator-wave/pull/18
>
>Fixes taken from SwellRT
>
>This
