Re: command for stopping server
The advice here is solid, but to answer the initial query... i created a
one liner to kill any runservers from my current user, as they can get lost
in my sea of terminals. This may help:
alias kill-runserver="ps -eaf | grep 'manage.py runserver' |
grep "'$USER'" | grep -v grep | awk '{print "'$2'"}' | xargs kill -9"
Good luck!
On Monday, September 7, 2020 at 9:37:50 AM UTC-4 tond...@gmail.com wrote:
> Hello there,
>
> This question on StackOverflow is a workaround for stopping the server
>
> https://stackoverflow.com/questions/27066366/django-development-server-how-to-stop-it-when-it-run-in-background
>
> Basically I would like to run the server and stop it by a program, it is
> hard, when the default way is literally "pressing ctrl+C",
> killing the process is different on different OS'es.
> When searching the web (StackOverflow) users replies to individual answers
> were "This worked for me." or "This didn't work for me.",
> this showcases that different conditions make it hard to get to actually
> stopping the server.
>
> A unified solution would be very nice. If we want to keep "python
> manage.py runserver" together with "press ctrl+C to quit",
> then I would suggest a new command, let's call it "startserver", that
> would be non-blocking, running subprocess, or something,
> once the user is done he simply calls "stopserver" to stop it.
> "startserver" vs "runserver" might be similar for some, suggest different
> command name if you like.
>
> It is only my suggestion, I don't care if it will be more complicated as
> long as it will "just work" on all OS'es and will be clear to use.
>
> Thanks for your time and consideration
> Antonín Drdácký
>
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-developers/5712fd9d-2555-45f2-ad7c-3e4d05b65660n%40googlegroups.com.
Re: command for stopping server
A little tip Tim - your one-liner can also be achieved with the pkill
utility: pkill -u $USER -f manage.py runserver . The user matching with -u
$USER flag is cautious but probably unnecessary.
https://linux.die.net/man/1/pkill
On Tue, 8 Sep 2020 at 10:48, Tim Allen wrote:
> The advice here is solid, but to answer the initial query... i created a
> one liner to kill any runservers from my current user, as they can get lost
> in my sea of terminals. This may help:
>
> alias kill-runserver="ps -eaf | grep 'manage.py runserver' |
> grep "'$USER'" | grep -v grep | awk '{print "'$2'"}' | xargs kill -9"
>
> Good luck!
>
> On Monday, September 7, 2020 at 9:37:50 AM UTC-4 tond...@gmail.com wrote:
>
>> Hello there,
>>
>> This question on StackOverflow is a workaround for stopping the server
>>
>> https://stackoverflow.com/questions/27066366/django-development-server-how-to-stop-it-when-it-run-in-background
>>
>> Basically I would like to run the server and stop it by a program, it is
>> hard, when the default way is literally "pressing ctrl+C",
>> killing the process is different on different OS'es.
>> When searching the web (StackOverflow) users replies to individual
>> answers were "This worked for me." or "This didn't work for me.",
>> this showcases that different conditions make it hard to get to actually
>> stopping the server.
>>
>> A unified solution would be very nice. If we want to keep "python
>> manage.py runserver" together with "press ctrl+C to quit",
>> then I would suggest a new command, let's call it "startserver", that
>> would be non-blocking, running subprocess, or something,
>> once the user is done he simply calls "stopserver" to stop it.
>> "startserver" vs "runserver" might be similar for some, suggest different
>> command name if you like.
>>
>> It is only my suggestion, I don't care if it will be more complicated as
>> long as it will "just work" on all OS'es and will be clear to use.
>>
>> Thanks for your time and consideration
>> Antonín Drdácký
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers (Contributions to Django itself)" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-developers+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/5712fd9d-2555-45f2-ad7c-3e4d05b65660n%40googlegroups.com
>
> .
>
--
Adam
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-developers/CAMyDDM1%3DGOr9hjw7d5kA6iscGzykftif1ff9xrJPWQLXj0e63A%40mail.gmail.com.
Fellow Reports -- September 2020
Hi all. Calendar Week 36 -- ending 06 September. Released Django versions 3.1.1, 3.0.10 and 2.2.16. Triaged: https://code.djangoproject.com/ticket/30952 -- KeyError: '_password_reset_token' during password reset. (needsinfo) https://code.djangoproject.com/ticket/31974 -- SplitDateTimeWidget and is_valid problem (Invalid) https://code.djangoproject.com/ticket/31970 -- Logging in from one browser logs me out from other browsers (wontfix) https://code.djangoproject.com/ticket/31961 -- forms.ChoiceField calls choices callback multiple times. (Duplicate of #11390) https://code.djangoproject.com/ticket/31941 -- FileField with a callable storage does not deconstruct properly (Accepted) https://code.djangoproject.com/ticket/31938 -- Add a mechanism for page cache invalidation. (Duplicate of #5815) Reviewed: https://github.com/django/django/pull/13331 -- Async docs incorrectly stated that async_to_sync runs async function in same thread https://github.com/django/django/pull/12017 -- Refs #21231 -- Backport urllib.parse.parse_qsl() from Python 3.8. https://github.com/django/django/pull/13382 -- Refs #31224 -- Made sync_to_async() examples with ORM calls use thread sensitive. https://github.com/django/django/pull/12928 -- Fixed #25791 -- Implement autoreload behaviour for cached template loader https://github.com/django/django/pull/13134 -- Fixed #31747 -- Fixed model enumeration via admin URLs. https://github.com/django/django/pull/13381 -- Fixed #31979 -- Made django.test.utils.setup_databases()'s time_keeper argument optional. https://github.com/django/django/pull/13379 -- Refs #31901 -- Fixed SeleniumTests.test_list_editable_popups with headless mode. https://github.com/django/django/pull/12646 -- Fixed #31169 -- Adapted the parallel test runner to use spawn. [GSoC] https://github.com/django/django/pull/13364 -- Fixed #31858 - Reallowed whitespaces in URL paths outside of parameters. https://github.com/django/django/pull/13343 -- Fixed #31941 -- Corrected FileField.deconstruct() with a callable storage. #13343 Authored: https://github.com/django/django/pull/13376 -- Refs #11390 -- Clarified dual-calling of ChoiceField.choices callable. Kind Regards, Carlton -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/3224d277-0c8d-4935-85b4-4ff591c76ffdn%40googlegroups.com.
