[Django] #33467: Small Framework to create a Demo-System
Django
------------------------------------------+------------------------
Reporter: Thomas Güttler | Owner: nobody
Type: Uncategorized | Status: new
Component: Uncategorized | Version: 4.0
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
------------------------------------------+------------------------
If Django would provide a small framework how to create demo-system, this
would helpfull:
* Developers would waste less time creating fundamental data-structures,
just to be able to use a view in the development system
* It would it make easier to unboard a new django developer in a company,
since he/she would be familiar with it
* Less teams would copy the production-DB into the development-DB.
There are several ways how to get there here is one idea:
The AppConfig class can provide a method called `create_demo_data()`. This
implements
the creation process. It is up to the developer to implement it (if he
wants to).
There is a new management command which calls all AppConfigs.
Of course there are some details not solved yet. For example: how to
handle the case where
App2 depends on data of App1.
Would you accept a pull-request?
--
Ticket URL: <https://code.djangoproject.com/ticket/33467>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Django
Reporter: Thomas Güttler | Owner: nobody
Type: Uncategorized | Status: new
Component: Uncategorized | Version: 4.0
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
Description changed by Thomas Güttler:
Old description:
> If Django would provide a small framework how to create demo-system, this
> would helpfull:
>
> * Developers would waste less time creating fundamental data-structures,
> just to be able to use a view in the development system
>
> * It would it make easier to unboard a new django developer in a company,
> since he/she would be familiar with it
>
> * Less teams would copy the production-DB into the development-DB.
>
> There are several ways how to get there here is one idea:
>
> The AppConfig class can provide a method called `create_demo_data()`.
> This implements
> the creation process. It is up to the developer to implement it (if he
> wants to).
>
> There is a new management command which calls all AppConfigs.
>
> Of course there are some details not solved yet. For example: how to
> handle the case where
> App2 depends on data of App1.
>
> Would you accept a pull-request?
New description:
If Django would provide a small framework how to create demo-system, this
would helpful:
* Developers would waste less time creating fundamental data-structures,
just to be able to use a view in the development system
* It would it make easier to onboard a new django developer in a team,
since he/she would be familiar with it
* Less teams would copy the production-DB into the development-DB. This is
a bad habit since it usually violates data-protection regulations.
There are several ways how to get there here is one idea:
The AppConfig class can provide a method called `create_demo_data()`. This
implements
the creation process. It is up to the developer to implement it (if he
wants to).
There is a new management command which calls all AppConfigs.
Of course there are some details not solved yet. For example: how to
handle the case where
App2 depends on data of App1.
Would you accept a pull-request?
--
--
Ticket URL: <https://code.djangoproject.com/ticket/33467#comment:1>
Django
Reporter: Thomas Güttler | Owner: nobody
Component: Uncategorized | Version: 4.0
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
Changes (by Thomas Güttler):
* type: Uncategorized => New feature
--
Ticket URL: <https://code.djangoproject.com/ticket/33467#comment:2>
Django
--------------------------------+--------------------------------------
Reporter: Thomas Güttler | Owner: nobody
Component: Uncategorized | Version: 4.0
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--
Ticket URL: <https://code.djangoproject.com/ticket/33467#comment:3>
Django
--------------------------------+--------------------------------------
Reporter: Thomas Güttler | Owner: nobody
Component: Core (Other) | Version: 4.0
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
Changes (by Mariusz Felisiak):
* status: new => closed
* resolution: => wontfix
* component: Uncategorized => Core (Other)
Comment:
Thanks for the ticket, I'm now sure how you would like to builtin an
universal way to create a demo. Please first start a discussion on the
DevelopersMailingList, where you'll reach a wider audience and see what
other think. I doubt there would be consensus to add that complexity.
Personally, I think that a third-party package is the best way to proceed.
Hope it makes sense.
Closing as "wontfix" with a request to start a discussion.
--
Ticket URL: <https://code.djangoproject.com/ticket/33467#comment:4>