Its a bit strange to state "a number of good '''ways'''", and then present
the reader with exactly one method. Ideally I'd like to see a suggestion
to host multiple sites one one server without weird tricks, but at least
it may be good to indicate there is ony a single method recommended to
deploy when there is indeed only one method... so maybee like this:
> Django’s chock-full of shortcuts to make Web developer’s lives easier,
but all those tools are of
> no use if you can’t easily deploy your sites. Since Django’s inception,
ease of deployment
> has been a major goal. THe best way to deploy Django is through WSGI:
> How to deploy with WSGI
> Deployment checklist
--
Ticket URL: <https://code.djangoproject.com/ticket/24926>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* needs_better_patch: => 0
* stage: Unreviewed => Accepted
* needs_tests: => 0
* needs_docs: => 0
Comment:
Yes, FastCGI was deprecated and now removed in master so the text you
propose is okay though we can probably just chop "There’s a number of good
ways to easily deploy Django:" without replacement. While we're there, it
might be best to remove the outdated reference to Django Book or update
the note to mention that it's discussion of FastCGI is also outdated.
--
Ticket URL: <https://code.djangoproject.com/ticket/24926#comment:1>
* status: new => assigned
* owner: nobody => yamila-moreno
--
Ticket URL: <https://code.djangoproject.com/ticket/24926#comment:2>
* has_patch: 0 => 1
Comment:
PR: https://github.com/django/django/pull/4791
--
Ticket URL: <https://code.djangoproject.com/ticket/24926#comment:3>
* stage: Accepted => Ready for checkin
--
Ticket URL: <https://code.djangoproject.com/ticket/24926#comment:4>
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"f954c517203d1fceaa1de26b17b242690cc138fa" f954c51]:
{{{
#!CommitTicketReference repository=""
revision="f954c517203d1fceaa1de26b17b242690cc138fa"
Fixed #24926 -- Removed outdated information from deployment
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/24926#comment:5>