Documentation - Installation from scratch

[Marc Rechté]

Hello,

Just a small comment on my first exposure to LFS.

The documentation currently gives an install procedure that upset me to the point I was about to abandon its installation. That would have been a mistake !

I am sure that for setup with no previous Django exposure, the current procedure is fine.

On the other hand when one has already the Django framework installed and a little experience with it (at least the tutorial), the current procedure is very confusing.
It does not show the Django integration and add more complexity (what are gunicorn, buildout, and are they useful for testing and discovering LFS ?)

Why not provide some guidelines that would more or less follow:

1)  explain the Python dependencies required and how to install them
2) copy the source code to a local directories
3) provide the urls.py, settings.py, manage.py as models
4) then follow the classic manage.py syncdb, lfs_init, runserver (with a bit of explanation for lfs_init)

Actually I ended up in doing this but it took me some digging into the lfs_installer and source code.

If somebody wishes to deploy LFS on a production site he/she will eventually be faced with this type of installation.

I think this would help LFS to become more popular.

Anyway congratulation to the dev team for the promising work.

Thanks for reading

[Jo]

Hi Marc,

On Monday, 22 October 2012 11:07:09 UTC+2, Marc Rechté wrote:

Why not provide some guidelines that would more or less follow:

1)  explain the Python dependencies required and how to install them
2) copy the source code to a local directories
3) provide the urls.py, settings.py, manage.py as models
4) then follow the classic manage.py syncdb, lfs_init, runserver (with a bit of explanation for lfs_init)

Actually I ended up in doing this but it took me some digging into the lfs_installer and source code.

I think this is a good proposal, since I have the same problems.
Maybe you can post your findings to help others.

Cheers,

Jo

[Kai Diefenbach]

Hi,

thanks for the suggestion.

Please consider to fork LFS and contribute a chapter to the
documentation.

FWIW, the next generation installer won't use buildout anymore:

https://github.com/MrTango/django-lfs-bootstrap

Kai

[Noe Nieto]

Hi Kaj,

I'm curious. Why abandon zc.buildout? Is it just because it freaks out new users or because django-lfs-bootstrap offers superior functionality?

Are you going to make incompatible changes in lfs that would prevent the use of zc.buildout?

--
Noe

2012/10/22 Kai Diefenbach <kai.die...@iqpp.de>

--
You received this message because you are subscribed to the Google Groups "django-lfs" group.

To post to this group, send email to djang...@googlegroups.com.
To unsubscribe from this group, send email to django-lfs+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-lfs?hl=en.

--
---
Noe Nieto
NNieto Consulting Services
M: nni...@noenieto.com
W: http://noenieto.com
T:  @tzicatl
Li: Perfil en LinkedIn

[Kai Diefenbach]

Hi Noe,

On Oct 22, 5:23 pm, Noe Nieto <nni...@noenieto.com> wrote:
> Hi Kaj,

(It's Kai, BTW)

> I'm curious. Why abandon zc.buildout? Is it just because it freaks out new
> users or because django-lfs-bootstrap offers superior functionality?

It's more Django-ish.

> Are you going to make incompatible changes in lfs that would prevent the
> use of zc.buildout?

I don't think so.

Kai

[Noe Nieto]

Cool.

Sorry for mistyping your name ;)

--
Noe