Skip to content

Commit 59802a2

Browse files
user guide: move "compound commands" in with "installing workflows"
1 parent 8c9629c commit 59802a2

File tree

3 files changed

+64
-53
lines changed

3 files changed

+64
-53
lines changed

src/7-to-8/major-changes/cli.rst

Lines changed: 11 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -113,12 +113,17 @@ GUI. Consequently the following commands have also been removed:
113113
The ``cylc gui`` command remains, it launches a standalone version of the
114114
web GUI (providing the `Cylc UI Server`_ is installed).
115115

116-
.. seealso::
117-
118-
:ref:`CompoundCommands` - For your convenience we have
119-
provided commands which represent common working practices. For
120-
example ``cylc vip`` (Validate-Install-Play) which runs
121-
``cylc validate``, ``cylc install`` and ``cylc play``.
116+
Additionally, there are two
117+
":ref:`compound commands <installing_workflows.compound_commands>`"
118+
which automate common working practices, namely:
119+
120+
``cylc vip``
121+
Validate, install and play a workflow. This is similar to what
122+
``rose suite-run`` did.
123+
``cylc vr``
124+
Valiate, install, then either reload (if the workflow is running) or restart
125+
(if it is stopped) the workflow. This is similar to what
126+
``rose suite-run --reload`` and ``rose suite-run --restart`` did.
122127

123128

124129
Cylc 8 Standardised IDs

src/user-guide/compound-commands.rst

Lines changed: 0 additions & 47 deletions
This file was deleted.

src/user-guide/installing-workflows.rst

Lines changed: 53 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -25,6 +25,11 @@ location, called a :term:`source directory`.
2525
``cylc install`` will create a new run directory in the :term:`cylc-run directory`
2626
for each installation of a workflow.
2727

28+
.. contents:: Contents
29+
:depth: 2
30+
:local:
31+
32+
2833
.. _Install-Workflow:
2934

3035
The Cylc Install Command
@@ -449,3 +454,51 @@ There are some occasions when installation is expected to fail:
449454
previous installation. i.e. running ``cylc install`` in
450455
``~/cylc-src/my-flow``, followed by running ``cylc install`` from
451456
``~/different/my-flow``.
457+
458+
459+
.. _installing_workflows.compound_commands:
460+
461+
Compound Commands
462+
-----------------
463+
464+
Cylc provides compound commands which carry out multiple operations.
465+
466+
For example Cylc provides a command to validate, install and play a workflow.
467+
468+
Compound commands make common ways of working easier.
469+
470+
.. note::
471+
472+
Use ``cylc command --help`` to get help for each compound command,
473+
including a full list of available options.
474+
475+
476+
``cylc vip`` (Validate, Install and Play)
477+
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
478+
479+
``cylc vip /home/me/cylc-src/my-workflow`` is the same as running:
480+
481+
.. code-block:: bash
482+
483+
$ cylc validate /home/me/cylc-src/my-workflow
484+
$ cylc install /home/me/cylc-src/my-workflow
485+
INSTALLED my-workflow/run1 from /home/me/cylc-src/my-workflow
486+
$ cylc play my-workflow
487+
488+
``cylc vr`` (Validate, Reinstall and Reload or Play)
489+
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
490+
491+
``cylc vr my-workflow`` is the same as running:
492+
493+
.. code-block:: bash
494+
495+
# Check that the changes you want to
496+
# make will be valid after installation:
497+
$ cylc validate my-workflow --against-source
498+
$ cylc reinstall my-workflow
499+
500+
# If workflow is running:
501+
$ cylc reload my-workflow
502+
503+
# If workflow is stopped:
504+
$ cylc play my-workflow

0 commit comments

Comments
 (0)