pproach, as I don't
have any experience with binary only packaging (all our distributed
code is open source). But these at least should give you a starting
point for your own investigation.
Regards,
--
Andrew Cutler
--
You received this message because you are subscribed to the Google Groups
&quo
admin to plumb everything together. Perhaps
later on I'll roll some generic Debs and RPMS that satisfy the
required dependencies, but for now we assume our end users are
technically proficient, so we can get away with a less integrated
approach.
Cheers,
--
Andrew Cutler
--
You received this me
On 18 April 2012 23:21, Daniel Sokolowski
wrote:
> Can you clarify if you approach can handle things that are not installable
> through pip? For example I run into an issue with geodjango requirements -
> I was not able to get everything installed through PIP and had to resort to
> manually using
On 15 March 2012 12:33, Andrew Cutler wrote:
>
> We also want to be able to distribute a self contained Django project
> with sane defaults (and this is where it gets tricky).
>
Answering my own question here... But I've finally achieved the "holy
grail" of Djan
On 15 March 2012 02:40, bruno desthuilliers
wrote:
> We dont - we use virtualenvs (no-site-packages), pip requirements, and
> git.
We do the same here. Our deployment looks something like
# mkvirtualenv --no-site-packages foo
# workon foo
# cdvirtualenv
# svn checkout bar
# pip install -r deploy
5 matches
Mail list logo
