>On Tue, Feb 17, 2015 at 10:58 PM, Bertrand Delacretaz < >[email protected]> wrote: > >>(...) >>Tomasz just published https://github.com/trekawek/Sling-S3 with >>interesting setups for running Sling on Oak + Mongo. That stuff is not >>officially part of Sling but now that he's a committer, having more >>users might convince him to bring this here as a contrib ;-) > > >After such call I have no other choice but to move Sling-S3 to the Sling >contrib :) I'll do it in a few days. >
I¹d like to update that debian packaging module I did to use this crankstart mechanism instead of launchpad because it provides a more flexibility for configuring options at runtime. There¹s a few options here. 1) If the Sling-S3 is as a contrib component, then I can depend on it within the packaging module. Although I¹m not sure exactly what the cleanest way to pull it in is, as it¹s not a maven artifact and I really just need the base templates & the ruby script. I suppose it could be packaged as resources in a jar. That doesn¹t feel right though. Where you you see this in the sling tree? While it is an end to end S3/mongo setup, it¹s more akin to a contrib module for crankstart as it provides a quick start setup for crankstart. 2) I could pull your scripts directly into the packaging module, but I think this loses some flexibility. While it doesn¹t restrict anyone from using it in a non-debian/ubuntu manner, it does make it a bit confusing if it¹s all wrapped up with the debian bits. 3) Add the debian packaging folder under Sling-S3 (or whatever you end up calling it). That way I can refer to the parent module for all the pieces I need and it doesn¹t imply that one needs to build a .deb to use it. Regarding the actual packaging I¹m thinking of putting the crank.*/ dirs into /etc/sling/crank.*/ such that they are treated as config files such that they are created if not present on initial installation, but then remain untouched by update installations. This lets the user modify these files as needed, while at the same time retaining the ability to update the crank.d/*-sling-startlevel-*.txt manually for existing installations. The building phase (install-deps & make target/*) would take place from the package¹s postinst script, as it will have internet connectivity during this phase. Lastly, /etc/default/sling will define the storage mode for sling, unset (default to tar), s3, mongo, or s3-mongo. -Bruce
