![]() Users can then run the command as fin mycommand to get the mycommand-cli executed in cli. one that does fin exec '/var/mycommand).one with the actual code, that you want to execute (e.g., mycommand-cli).One way to achieve this is to write two commands: In some cases you’d want a command to be executed inside cli instead of the host (e.g., when you do not want to rely onĪny dependencies installed on the host and use the tools available in cli). Note in the above example for node, that custom command meta information lines are wrapped in a comment block You can use any interpreter for your custom command scripts #!/usr/bin/env python3 This is useful for tedious tasks that you need in every project. Put your command in $HOME/.docksal/commands and it will be accessible globally. See an example of command documentation in the phpcs command (examples/.docksal/commands/phpcs located in the Docksal project.) Global Custom Commands The rest of the lines will be available as advanced help via fin help command_name. # Custom command descriptionįin will output the first line of custom command documentation as the short description when using fin help. Here is an example init command for a Drupal website using drush to automate the install: #!/usr/bin/env bashįin drush site-install -y -site-name="My Drupal site"įin looks for lines starting with # for command documentation. ![]() Not available for commands targeting other containers unless you explicitly declare them in your docksal.yml file for These variables are only provided to standard custom commands or commands targeting the cli.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |