Peter,
I think you have a really good idea.
I did one like it earlier in the year based around the Tornado web
framework.
Three people showed and it was still a really great afternoon of
digging into the code base with 2 other really smart geeks that day.
I was thinking it could be fun to do a "code camp" one these Saturdays
in the fall or winter while it's raining in Seattle.
Evening meetings are great but 2 or 3 hours is barely enough time to
dig in.
But an all day thing could give people more time to explore, hack
some and share in the process.
To be honest I am actually shocked that more Seattle based Python
startups and companies don't support these kind of ideas.
As where do folks think they are going to find their workers when the
time comes, if everyone is so hush hush.......... about code?
-Kevin
On Aug 3, 2012, at 4:35 PM, Peter Conerly wrote:
I'm getting the feeling that my event might not happen. (Well, it'll
still happen, but it's going to be a one-person event :D ) The
reason I decided on a workday is that I really think it's going to
take that long to get a Chef cookbook that'll do everything a person
needs. (I also chose a workday because, hey, Chef is a really good
skill for an employee to have. Your employer should be fine with you
taking a day to learn.)
Also, some of you are wondering why you should learn Chef (rather
than another framework). I went to the last deployment meeting and
it was pretty clear that Chef is the framework with the most
maturity and community support. That means that there are going to
be a lot of pre-written Chef scripts that we can just grab and not
worry about as much.
The key quotes from the deployment meeting was: "just pick a
deployment system and go with it" and "Every week you put off
implementing a deployment system makes for a more painful transition".
Michael: Thanks for the offer! I'll follow up off-list, but you
should definitely consider helping out SeaPIG with a tutorial!
Peter
On Fri, Aug 3, 2012 at 4:16 PM, Kevin LaTona <[email protected]>
wrote:
Michael,
Oh and sorry I didn't mean to put on the spot out like that on a
public email list.
But this whole idea would dovetail in perfectly with the last
deployment meeting we just had.
Plus I can't make it to Peter's upcoming event next week.
But think it's a really good way on how to get up to speed faster
with a new code base.
-Kevin
On Aug 3, 2012, at 4:07 PM, Kevin LaTona wrote:
Michael,
If Peter's group can't do it after work.
Would you be willing to lead up some kind of a hands on style
meeting at one of the up coming SeaPig meetings?
I think these kind of SeaPig meetings can be lots of fun.
Plus everyone gets so much more out them.
When we look at code, write some code, and talk about what is going
on.
What do you think?
-Kevin
On Aug 3, 2012, at 3:47 PM, Michael Frank wrote:
If you guys can meet after work hours (and would find it useful), i
can give you some suggestions and anecdotes about my experiences
with puppet and chef. i've deployed chef on ~10 nodes in AWS, and
architected a 100 node roll-out of puppet on dedicated
infrastructure. in my current job i'm part of a team deploying
puppet to thousands of dedicated servers across multiple datacenters.
-Michael
On 8/1/12 7:32 PM, Joseph Wright wrote:
I would be interested in this. I need to evaluate Chef, Puppet, and/
or similar tools to see if it would be worth integrating into
existing infrastructure.
Joseph
On Aug 1, 2012, at 6:12 PM, Peter Conerly <[email protected]> wrote:
Hello SeaPIGs and Django-Seattle
I'm pretty unhappy with my server configuration strategy, which is
currently just manually executing a lot commands. The deploy
meeting inspired me to finally take the leap and learn Chef.
Does anyone else want to learn it with me? I've always found that
it helps to have others who are also learning. (A buddy and I
learned Django together-- if we hadn't teamed up, the admin
configuration probably would've defeated us.)
I'm going to spend a workday during the next week to learn Chef. If
anyone wants to join, let me know, and I can provide a meeting space
for us. A group of 3-4 would probably be ideal. I'll be attempting
to use Chef to create Django-ready servers from the amazon ec2
ubuntu base server.
Best,
Peter
