for example, check whether this level of customization capabilities of the
generated project that you need:
pip install tox cookiecutter
cookiecutter https://github.com/ionelmc/cookiecutter-pylibrary.git
The ionelmc cookiecutter-pylibrary project uses the cookiecutter hooks to
customize post
Sounds like you might want to take a look at cookiecutter[0] and/or
project templates[1]
[0] https://github.com/audreyr/cookiecutter
[1]
https://docs.djangoproject.com/en/dev/ref/django-admin/#startproject-projectname-destination
On Tue, Jun 23, 2015 at 2:26 PM, Hiroki Kiyohara wrote:
> Thanks,
You may also want to look into cookiecutter as a way of managing more
complex templates for projects.
Marc
On 23 Jun 2015 05:26, "Hiroki Kiyohara" wrote:
> Thanks, Josh.
>
> * I thought the config (.djangorc) should be included in project template
> it's own.
> * bash alias is OK, but it's not e
Thanks, Josh.
* I thought the config (.djangorc) should be included in project template
it's own.
* bash alias is OK, but it's not easy to share this way with lots of
developers like "Hey, when you start development, please type `alias
mystartproject...` (so long)."
anyway, I got it. I'll create
There are a couple of problems with this proposal IMO.
1) The .djangorc file would need to be somewhere on the file system (like
~/.djangorc), because you want it for the startproject command, it can't be
deployed with startproject
2) It doesn't seem to provide that big a benefit
3) A simple bas
Hi all.
I propose a new feature `.djangorc`.
It should be included in root of project template.
You can write down configations for `startproject --template=...`
## Motivation
I always use custom project template, but it requires a lot of arguments
like...
django-admin startproject --templ
