I was hoping to make it official, just wasn't sure who I should get to jump in 
and sign off.  It'd be neat to get this done in time for the conference :-)

I also wasn't sure of the best way to handle versioning, and in particular 
Dancer v. Dancer2, so any insight or advice is appreciated.

By the way, thanks for pointing me to those blog posts, and thanks to Rob for 
writing it!

Sent from my iPhone

> On Oct 1, 2014, at 3:15, Jakob Voß <[email protected]> wrote:
> 
> Hi,
> 
> Peter Martini has created a Docker image for Dancer, which I have contributed 
> to:
> 
> https://github.com/PeterMartini/docker-dancer
> https://registry.hub.docker.com/u/petermartini/docker-dancer/
> 
> If this is ok to Peter, I'd prefer this to be an official repository at 
> https://github.com/PerlDancer. You should also create an Docker organization 
> account for the Dancer community:
> https://hub.docker.com/account/organizations/
> 
> The current documentation could be extended to a tutorial.
> Rob N already did good work here: http://robn.io/docker-perl/
> (I'm not sure we should recommend the git glone approach as *only* way to 
> build your dancer application image, one could also use "COPY" in a 
> Dockerfile and "docker build"). A similar tutorial for another language is 
> https://docs.docker.com/examples/nodejs_web_app/.
> 
> Anyway: I think that an (or multiple) official Docker images for Dancer could 
> improve the visibility and usability of Dancer framework a lot.
> 
> Cheers,
> Jakob
> 
> P.S: If Task::Dancer wasn't stalled (no updates since 2012?!) I'd recommend 
> to install Task::Dancer instead of just Dancer
> 
> -- 
> Jakob Voß <[email protected]>
> Verbundzentrale des GBV (VZG) / Common Library Network
> Platz der Goettinger Sieben 1, 37073 Göttingen, Germany
> +49 (0)551 39-10242, http://www.gbv.de/
_______________________________________________
dancer-users mailing list
[email protected]
http://lists.preshweb.co.uk/mailman/listinfo/dancer-users

Reply via email to