serenovallc/winter

Winter gem application and configuration packaging system.

winter's Issues

Clear conf dir before writing new templates

When config templates change names or are removed, the rendered template files remain in the run/{name}/conf directory. This directory should be removed when the templates are rendered to prevent detritus from accumulating.

Figure out incompatibility between rspec and 'stop' killing the process group

When rake spec is run and the systems tests are performed, the 'stop' method finds the pid of the current process (which is rspec) and kills it. This prevents the test from running successfully.

transitive dependency management

Winter does not detect or resolve dependencies with any bundles or libs included in the Winterfile. Should Winter detect these missing dependencies and do something about it?

64-bit by default; overriding is difficult

JVM is started in 64-bit mode on all platforms. It's possible to override this by including a conf 'foo.json' line to your Winterfile that includes

{
  "64bit" : false
}

However, this is a little annoying for 32-bit platforms. There should either be some platform detection or at least an easier way of overriding the platform precision.

When config.properties is missing OSGi won't start

The java invocation is hard coded in Winter and requires that a config.properties file be present. That's bad.

Generating a default file is an option, but that could conflict with other command line directives passed to the JVM. Removing the hard coded constraint is important, but the container still needs to boot and load the 'libs' and 'bundles' directory.

'winter status' should be able to take a Winterfile path (like start, stop)

winter status currently relies on the Winterfile to be in the current working directory and be named 'Winterfile'. This should take an argument like the 'start' and 'stop' commands but keep 'Winterfile' as the default.

winter prune

winter prune command to parse the Winterfile and remove files from the run directory that should not be there.

During 'winter build'; ctl-c capture and exit cleanly

When running a winter build, if I press ctl-c to stop the process there are still threads running and trying to download artifacts. Winter needs to keep a list of children and kill them when it receives the appropriate signals.

'fetch' a jar/tar/zip from a URL or GAV string

A Winterfile and its configs should be built along with the application and deployed to a maven repository (Artifactory, Nexus, etc). The artifact containing just the configs should be downloaded and extracted by Winter.