Joel in being Joel shocker :p
Though there's a fair point in there somewhere, I'm sure...
On 25 Jul 2014 18:28, "Sue Spence" wrote:
> On 25 July 2014 17:59, Joel Bernstein wrote:
>
> > On 25 July 2014 18:22, Tom Hukins wrote:
> >
> > > We invite anyone who would like to work on anything
> > > P
On 25 July 2014 17:59, Joel Bernstein wrote:
> On 25 July 2014 18:22, Tom Hukins wrote:
>
> > We invite anyone who would like to work on anything
> > Perl-related to attend. Everyone from complete Perl beginners to
> > experts is welcome.
> >
>
> How do you define Perl-related? Perl itself? Per
On 25 July 2014 18:22, Tom Hukins wrote:
> We invite anyone who would like to work on anything
> Perl-related to attend. Everyone from complete Perl beginners to
> experts is welcome.
>
How do you define Perl-related? Perl itself? Perl modules? Apps in Perl?
Apps partly in Perl? Apps in Ruby (e
On Saturday 20th September, 2014, London Perl Mongers will host our
first hack day. We invite anyone who would like to work on anything
Perl-related to attend. Everyone from complete Perl beginners to
experts is welcome.
This event will take place at the London Hack Space between 12pm and
5pm.
On Fri, 2014-07-25 at 12:08 +0200, James Laver wrote:
> On 25 Jul 2014, at 11:54, Andrew Beverley wrote:
>
> > The main problem is that it seems to be a victim of its own success:
> > there is a huge backlog of merge requests. I'd like to provide some
> > simple patches to a couple of modules to
On 25 Jul 2014, at 11:54, Andrew Beverley wrote:
> The main problem is that it seems to be a victim of its own success:
> there is a huge backlog of merge requests. I'd like to provide some
> simple patches to a couple of modules to make them work better for me,
> but have little hope that they'
On Fri, 2014-07-25 at 10:11 +0200, James Laver wrote:
> Ansible I do like for the most part
I'm a fan of Ansible, and am in the process of using it to deploy code
(although more by accident than design).
The main problem is that it seems to be a victim of its own success:
there is a huge backlog
Hey,
We're in a similar boat to Leo for our use of Puppet - used to manage stuff
in /etc/ and the general Debian packages we have installed - but mostly we
build our own. We have an /opt/lokku/pkgs which contains our own Perl,
Apache, Percona DB, node.js, etc. We manage /opt/lokku/bin with swpkg -
On 25 Jul 2014, at 09:40, mascip wrote:
> and the idempotence: you can run a playbook as many times as you like, it
> should
> have just the same effect as running it once (true for most Ansible things).
That’s in stark contrast to my experiences. I found ansible requires you to
think about t
On 25 Jul 2014, at 08:52, Ben Tisdall wrote:
> However, I would urge you to spend a day each investigating Ansible &
> SaltStack, the latter in salt-ssh mode if you want to make a direct
> comparison. Both of the aforementioned tools do ad-hoc remote
> execution, task orchestration and configura
I've loved using Ansible on a personal project recently. Almost zero set up
and learning.
Compared to bash scripts, I love the reuse with Roles, the fact that many
tasks and roles exist (Ansible Galaxy is Ansible's CPAN), and the
idempotence: you can run a playbook as many times as you like, it sho
>> On 24 July 2014 22:31, Paul Makepeace wrote:
>>>
>>> capistrano is a (the?) winner for sure.
>>
I've used Capistrano a bit - it's ok but too much magic for my liking
(and in general I'm a big fan of the Ruby ecosystem). Fabric is a more
sensible alternative IMO (you might find
http://www.slide
12 matches
Mail list logo
