Opened 10 years ago

Closed 9 years ago

Last modified 7 years ago

#11578 closed (wontfix)

Include init.d script in source for downstream packaging

Reported by: Sebastian Rahlf Owned by: nobody
Component: Uncategorized Version: master
Severity: Keywords: init.d
Cc: Triage Stage: Design decision needed
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no


There is a working init.d script in the wiki
I may be a good idea to include this in the source to enable downstream package maintainers to include it, as well.

The debian maintainer is all up for it

Attachments (1)

django-init-d.patch (5.0 KB) - added by Sebastian Rahlf 10 years ago.

Download all attachments as: .zip

Change History (5)

Changed 10 years ago by Sebastian Rahlf

Attachment: django-init-d.patch added

comment:1 Changed 10 years ago by Sebastian Rahlf

Summary: Include init.d script in source for ownstream packagingInclude init.d script in source for downstream packaging

Stupid typo!

comment:2 Changed 10 years ago by Alex Gaynor

Triage Stage: UnreviewedDesign decision needed

comment:3 Changed 9 years ago by Russell Keith-Magee

Resolution: wontfix
Status: newclosed

I'm not convinced that the Django repository is the right place for this. init.d scripts are highly OS dependent, and can even be OS version dependent. If package maintainers want to include scripts like this, I encourage them to do so, but I don't see what having this code in the Django repository does to improve that process.

On top of the platform issue, there is also the issue that Django has historically treated deployment as a documentation issue. We have avoided providing Apache config files, wsgi scripts, or any other deployment artefact because local configuration of a webserver is something that always needs to be tuned to local needs.

comment:4 Changed 7 years ago by Jacob

milestone: 1.2

Milestone 1.2 deleted

Note: See TracTickets for help on using tickets.
Back to Top