I've made a quick and dirty howto about using capistrano with django :
http://cyberdelia.tryphon.org/blog/2007/10/27/django-capistrano/
It should help us waiting for a more django and pythonic way to do it ;)
Cheers,
--
Timothée Peignier
http://people.tryphon.org/~tim/
On Mon, 2007-09-10 at
I've put up the script I use for deploying our apps, on our internal
work server. It's pretty ugly, but It could be extended/improved
*alot*. It doesn't check about anything _at all_, it just works or
doesn't. :)
http://code.google.com/p/djdeliver
Anyone who feels like contributing, just let me
On Sep 27, 8:36 am, "Jon Atkinson" <[EMAIL PROTECTED]> wrote:
> Is anything happening with this project, or has it died on the vine?
>
Just a noob here, but why would Django need a Capistrano-like thing?
Rails needs it in order to marshal 5 mongrel processes per
application, etc etc, for
Is anything happening with this project, or has it died on the vine?
--Jon
On 9/13/07, rex <[EMAIL PROTECTED]> wrote:
>
> Hello.
>
> I'd be interested in helping with writing a Capistrano replacement for
> Django in python (not a port!).
> I'm relatively new to django sites, but quite an old
Hello.
I'd be interested in helping with writing a Capistrano replacement for
Django in python (not a port!).
I'm relatively new to django sites, but quite an old hand at python.
Regarding names... surely this is the least important part of a
project like this :)
My 2c though: dojango!
I really don't see a need for a huge project to accomplish the goals
you've outlined:
0) Checking in the local source changes if they have not already been
checked in (optional).
1) Logging into the deployment target.
2) Checking out the latest source.
3) Modifying the production database as
El mar, 11-09-2007 a las 12:26 -0700, Jonas escribió:
> Before that someone starts working about this, you must consider this:
>
> 1. It's already has been created a project with that intention. Its
> name is capystrano [1] and althought has been not uploaded code -he
> could be working
Before that someone starts working about this, you must consider this:
1. It's already has been created a project with that intention. Its
name is capystrano [1] and althought has been not uploaded code -he
could be working offline-, it would be best contact with its author to
doesn't duplicate
On 9/11/07, Chris Hoeppner <[EMAIL PROTECTED]> wrote:
>
> I'll be creating a google code page as soon as we settle down on a name.
> I like Djangostrano. Sounds nice. But I'm not sure about anyone crying
> out something about "ripping other people's ideas".
>
I don't think I can help with
Just some names:
There is a genre called Jazz Fusion (
http://en.wikipedia.org/wiki/Jazz_fusion)
Here's a very long list of names that belong to that category:
http://en.wikipedia.org/wiki/List_of_jazz_fusion_artists
--~--~-~--~~~---~--~~
You received this
On Sep 11, 9:20 am, "Alvaro Mouriño" <[EMAIL PROTECTED]> wrote:
> Capistrano is:
> * A saint:http://en.wikipedia.org/wiki/Giovanni_da_Capistrano
> * An Italian city:http://en.wikipedia.org/wiki/Capistrano_%28VV%29
> * A city in
>
On Sep 8, 10:47 am, Chris Hoeppner <[EMAIL PROTECTED]> wrote:
> This is just to make it a bit more obvious. I've decided to make up a
> python application similar to Capistrano, for Django.
I'll just echo here that yes, I'd be very interested in this. It's on
my queue to learn Capistrano as a
Excellent - I look forward to the URL.
--Jon
On 9/11/07, Chris Hoeppner <[EMAIL PROTECTED]> wrote:
>
> I know, I know. Know what? I'll setup a trac site on a domain of mine.
> We can always move it somewhere else.
>
> El mar, 11-09-2007 a las 14:02 +0100, Jon Atkinson escribió:
> > I'm not sure
I know, I know. Know what? I'll setup a trac site on a domain of mine.
We can always move it somewhere else.
El mar, 11-09-2007 a las 14:02 +0100, Jon Atkinson escribió:
> I'm not sure the name is really as important as working code.
>
> --Jon
>
> On 9/11/07, Chris Hoeppner <[EMAIL PROTECTED]>
I'm not sure the name is really as important as working code.
--Jon
On 9/11/07, Chris Hoeppner <[EMAIL PROTECTED]> wrote:
>
> I'll be creating a google code page as soon as we settle down on a name.
> I like Djangostrano. Sounds nice. But I'm not sure about anyone crying
> out something about
I'll be creating a google code page as soon as we settle down on a name.
I like Djangostrano. Sounds nice. But I'm not sure about anyone crying
out something about "ripping other people's ideas".
El mar, 11-09-2007 a las 11:45 +0100, Jon Atkinson escribió:
> Are you going to create a wiki and
Here we are doing just a brainstorm, wiki comes later ;)
2007/9/11, Jon Atkinson <[EMAIL PROTECTED]>:
>
> Are you going to create a wiki and repository for this project any
> time soon? It would be a much more effective means of collaboration
> than the mailing list.
>
> --Jon
>
> On 9/11/07,
> > I think db schema migration should wait until django has some
> > feature that supports it, a limited set of scripting (python itself
> > of course) should be allowed in the "recipes"
I will take note of that. I thought that I'd leave that bit for the end
anyways.
The bit about the
I think db schema migration should wait until django has some feature that
supports it, a limited set of scripting (python itself of course) should be
allowed in the "recipes"
"recipes" is capistrano nomenclature, how should be called in this new
project? "jobs", or "tasks" is a good way to go.
On 10 Sep 2007, at 4:13 pm, Chris Hoeppner wrote:
> I see your point. Why reinvent the wheel? True. But I'm not trying to
> re-do capistrano using python instead of ruby. Capistrano has been the
> spark that made me think about doing this, but that's all there is to
> Capistrano.
>
> I'm doing
I see your point. Why reinvent the wheel? True. But I'm not trying to
re-do capistrano using python instead of ruby. Capistrano has been the
spark that made me think about doing this, but that's all there is to
Capistrano.
I'm doing this because:
1) I've anyways been thinking about this for
On 10 Sep 2007, at 1:10 pm, Chris Hoeppner wrote:
>> Would it not be
>> better to look at writing a django recipe for capistrano rather than
>> trying to re-implement it?
>
> Also, we can use a ferrari to drive heavy cargo. It's not really about
> "can I use it", but more about "will it be
> 3) Modifying the production database as necessary.
There's one major problem point in making this happen: Rails'
migrations. It's pretty simple really, once laid out.
Beside svn & tar methods, this is one of the most complex point of this
project, and it's also one of the points I'd need most
> "automating django's deployment tasks" sounds like a good start for me.
A rough list of what I consider those tasks to be:
0) Checking in the local source changes if they have not already been
checked in (optional).
1) Logging into the deployment target.
2) Checking out the latest source.
3)
Well, I'm interesed in the project and as first idea from the bainstrom is
the name: Capistrano's url is http://www.capify.org/, why can we call it
capipy, the py at the end is a clasic (tm) of projects coded in Python.
Another good idea is to review the concept of the tool to draw what it
should
25 matches
Mail list logo
