[sf-lug] where should django apps go?

[Samir Faci]

Since nobody said anything in a while, I figured I'd chime in.

I found that most of the time, packaged wb application in *Nix seems
to do a pretty bad job.

Half the tutorials on setting python and god help you rails, usually
start by......

ignore whatever came with your distribution and install pip or rvm

Is there any reason you want to use a .deb file to distribute your
application?  I'm not sure how good/ bad it is, since I haven't
used it much, but isn't fabric the hip python thing to use for deployment?

http://docs.fabfile.org/en/1.6/  ?



On Mon, May 13, 2013 at 3:11 PM, Sameer Verma <sverma at sfsu.edu> wrote:
> We have a Python Django application called Pathagar.
>
> https://github.com/PathagarBooks/pathagar
>
> Currently, we install using a set of instructions to install
> dependencies (apt or yum) and then go configure the django part
> itself. We've done this both in a home directory of a newly created
> user (bookserver) and in /opt
>
> Now, we are thinking of packaging up all of this into an RPM and/or
> DEB, but are at a loss. Conventionally, where should Python Django
> apps go?
>
> Pinging the list because some of you may know.
>
> cheers,
> Sameer
>
> _______________________________________________
> sf-lug mailing list
> sf-lug at linuxmafia.com
> http://linuxmafia.com/mailman/listinfo/sf-lug
> Information about SF-LUG is at http://www.sf-lug.org/



-- 
Samir Faci
*insert title*
fortune | cowsay -f /usr/share/cows/tux.cow

Sent from my non-iphone laptop.