Main app name with a startproject template (1.4)

[Dominique Guardiola Falco]

I have a template project I want to use to ease deployment of instances of a rather complex app

In the example source of django, the name of the "main app" folder, just above the root project folder is named "project_name" and when the command is used, the name is replaced by the project name.
I tried to put the name I want, but the command crafts a new name, like "project-name-template-66b7f02"

Is it mandatory in django 1.4 new folder structure that this first app has the same name as the project ?

I have references to this first app models in other packaged apps (that are here in order to be modified easily depending on the need of the particulat needs of this site instance), so I need this "main app" to have a fixed name, whereas the  project folder name is rather the name of this particular django instance.

Thanks for your help

Dominique

[Ramiro Morales]

On Sat, May 5, 2012 at 4:27 AM, Dominique Guardiola Falco
<dom.gu...@gmail.com> wrote:
> I have a template project I want to use to ease deployment of instances of a
> rather complex app
>
> In the example source of django, the name of the "main app" folder, just
> above the root project folder is named "project_name" and when the command
> is used, the name is replaced by the project name.

It is very hard to understand what you are trying to. Please try to refomulate
your question more clearly. Try to don't use ad-hoc names like "main app"
because it confuses things even further. A good idea would be to use the
same terms used in the documentation of the startproject command.

And please keep this topic on this list that's where it belongs.

Regards,

--
Ramiro Morales

[Dominique Guardiola Falco]

Ok Ramiro

While looking to explain it clearer, I isolated the problem : I'm calling an online gzipped template (from a github repo actually), and the problem is the final output of the startproject command , example here to create a "pony" project :

$ django-admin.py startproject --template=https://github.com/quinode/coop-template/tarball/master pony
$ tree pony
pony
└── github-repo-name-b8bf505
    ├── local_site
    │   ├── admin.py
    │   ├── __init__.py
    │   ├── local_settings.py
...

Instead of using the content of the unzipped folder, the command outputs it also in the rendering
So this is not really a bug, rather an unexpected behaviour, that means I have to create a gzip archive without an enclosing folder

Dominique