Re: Proposal: django project name

Christian González - Wed, 13 May 2020 at 22:13:34 > TL;DR: Django has no (builtin/explicit) settings variable like > PROJECT_NAME. Should have. 4 of those were comments (i wish the project templates stopped doing that) 3 of those were env variables which a deployment can override with an actual e

Re: Proposal: django project name

Hi Adam, > > TL;DR: Django has no (builtin/explicit) settings variable like > PROJECT_NAME. Should have. > > > I can see how it would be useful in several situations. But in most > long-lived projects I've come across, the "project name" is different > to the website name (or names, plural,

Re: Proposal: django project name

thank you for reply Virus-free. www.avast.com <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA

Re: Proposal: django project name

> > Wherever you place the template, users can already override it by creating > one in their project with the same name, in an app that appears first in > INSTALLED_APPS. There's a documentation page on this topic: > https://docs.djangoproject.com/en/3.0/howto/overriding-templates/ > Alternatively

Re: Proposal: django project name

Hi Christian > TL;DR: Django has no (builtin/explicit) settings variable like > PROJECT_NAME. Should have. > I can see how it would be useful in several situations. But in most long-lived projects I've come across, the "project name" is different to the website name (or names, plural, if it has

Proposal: django project name

Hi all, I didn't find anything about that in the archive here, so I'd like to come to you with an idea which is either very dumb (please tell me) or I don't know why anyone hasn't thought about it... I'm starting a bigger project with a self-created plugin system (GDAPS, alrady mentioned). Workin