Hi Santiago
All the mentions of virtualenv and pip are good, but I want to throw in
another suggestion that will make your life a lot easier when working in
teams and lower the discrepancy between "development machine" and "live
server": Vagrant [1].
In fact, we're now running *all* projects
Not sure if it was mentioned earlier in this thread (couldn't find it), but
what some people miss is that virtualenv is not just for development. You
can, and should, deploy to a virtualenv on your server too.
Matt.
--
You received this message because you are subscribed to the Google Groups
On Wed, Feb 22, 2012 at 9:17 AM, Santiago Basulto
wrote:
> I'm unsing virtualenvs and Pip. Seems great, is really easy that way.
>
> What about deployment? Will it be simple? Or should i care about the
> specific webserver?
on deployment there should be a 'real' webserver (as opposed to the
devel
Thank you guys.
I'm unsing virtualenvs and Pip. Seems great, is really easy that way.
What about deployment? Will it be simple? Or should i care about the
specific webserver?
Thanks!
On Feb 21, 1:21 pm, Tom Evans wrote:
> On Tue, Feb 21, 2012 at 3:54 PM, Shawn Milochik wrote:
> > On 02/21/201
On Tue, Feb 21, 2012 at 3:54 PM, Shawn Milochik wrote:
> On 02/21/2012 10:53 AM, Javier Guerra Giraldez wrote:
>>
>>
>> i do exactly that. just a tip: to create and maintain the pip
>> requirements file do:
>>
>> pip freeze> piprequirementsfile.txt
>>
>
>
> +1
>
> And it's checked into version c
On 02/21/2012 10:53 AM, Javier Guerra Giraldez wrote:
i do exactly that. just a tip: to create and maintain the pip
requirements file do:
pip freeze> piprequirementsfile.txt
+1
And it's checked into version control.
Shawn
--
You received this message because you are subscribed to the G
On Tue, Feb 21, 2012 at 8:24 AM, Sébastien Billion
wrote:
> Set a virtualenv is good thing. You can write a shell script which set the
> virtualenv and install all the external module with pip -r. Use pip -r
> nameofrequriementsfile.txt. In this file, put the list of module with
> version.
i do e
On Tue, Feb 21, 2012 at 1:24 PM, Sébastien Billion
wrote:
> Hi,
>
> Set a virtualenv is good thing. You can write a shell script which set the
> virtualenv and install all the external module with pip -r. Use pip -r
> nameofrequriementsfile.txt. In this file, put the list of module with
> version.
Hi,
Set a virtualenv is good thing. You can write a shell script which set the
virtualenv and install all the external module with pip -r. Use pip -r
nameofrequriementsfile.txt. In this file, put the list of module with
version.
Exemple:
django==1.3
PIL==1.1.7
If you want distribute your own apps
Hello people,
some time ago with a couple of friends started a project with Django.
We are really getting into it now, and have made several progress in
the last 3 months. But, as the code starts to grow up, everything
start to get complicated.
Right now we have our project hosted on Bitbucket, a
10 matches
Mail list logo
