You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Previously, the way the information was organized made it seem as if make dev.down would not do full docker-compse down. This hopes to fix that confusion and better organize info to recommend using make dev.down instead of make dev.down.service
Copy file name to clipboardExpand all lines: docs/devstack_interface.rst
+11-6Lines changed: 11 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -63,19 +63,24 @@ Useful Commands and Summary
63
63
64
64
+ ``make dev.up.without-deps.<service>`` will only bring up the <service> container
65
65
66
-
- ``dev.stop.<service>``: only stops the container. This does not remove the container or the networks it has created
66
+
- ``dev.stop``: Stops all running containers. This does not remove the containers or the networks they had created
67
67
68
-
When to use: When you are pausing your work on this container/devstack and you want to pick back up from where you left off. Next time you use dev.up to bring up containers, you should be able to mostly pick back up from where you started.
68
+
When to use: When you are pausing your work on devstack and you want to pick back up from where you left off. Next time you use dev.up.<service> to bring up containers, you should be able to mostly pick back up from where you started.
69
69
70
-
- ``dev.down.<service>``: stops the specified container and also removes the stopped containers as well as any networks that were created. Next time you use dev.up to bring up container, your container have reverted back to the pulled image.
70
+
Variation:
71
+
+ ``make dev.stop.<service>`` will only stop the specified container
72
+
73
+
- ``dev.down``: stops and removes all running containers as well as any networks that were created. Next time you use dev.up.<service> to bring up containers, your containers have reverted back to the pulled image.
71
74
72
75
Note: This will not affect content of the databases.
73
76
74
-
Note: This will only bring down <service>'s container and not its dependencies.
77
+
When to use: use this command only if you are okay with removing any changes you might have made to your containers. You will likely want to use ``make dev.stop`` instead of ``make dev.down``.
78
+
79
+
Variation:
75
80
76
-
When to use: use this command only if you are okay with removing any changes you might have made to the container
81
+
+ ``make dev.down.<service>`` will stop and remove only the specified container.
77
82
78
-
Variation: ``make dev.down`` will stop all your containers
83
+
Note: This will only bring down <service>'s container and not its dependencies.
79
84
80
85
- ``dev.shell.<service>``: used to enter the shell of the specified service container.
0 commit comments