Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

added some tasks for soft stop and start and for showing logs #97

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

itheodoridis
Copy link

.. also changed the stop to show that containers are deleted when doing invoke stop (it was a surprise the first time I ran it).

…hanged the stop to show that containers are deleted
@@ -160,7 +160,7 @@ def restart(context):
@task
def stop(context):
"""Stop Nautobot and its dependencies."""
print("Stopping Nautobot...")
print("Stopping Nautobot (deleting containers)...")
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My only concern with this phrasing is that someone new to Docker might think they're losing data when this is done due to the "delete" word being used. I'd say we should probably have some documentation too around why someone might want to use down vs stop, etc.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suppose you are right, would you like to include something in the comments at line 162? I did get confused when my containers got deleted when using this option (I probably should have read the doc more closely as well).
Or we would modify the message adding info about the volumes, for example:
print("Stopping Nautobot (deleting containers but keeping volumes and data)...")

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it'd make sense to alter the console message to be clearer about what's happening and also documenting what the various invoke task options are. i know we're currently missing the later at this time.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree. I am not sure how to help move this forward though. About presenting the options I think a help message should be defined in a central point in order to avoid repeating it for each option, possibly through a function (preferably) or a global variable. How can I help?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants