+ getDrushSanitizeInterface() + + +
+ + +Returns the Drush Sanitize Interface namespace depending on the current version.
+ +
+ private
+ getDrushSanitizeInterface() : string
+
+ diff --git a/classes/EcEuropa-Toolkit-AuthorizationBasic.html b/classes/EcEuropa-Toolkit-AuthorizationBasic.html index db29fd303..1ef1f150f 100644 --- a/classes/EcEuropa-Toolkit-AuthorizationBasic.html +++ b/classes/EcEuropa-Toolkit-AuthorizationBasic.html @@ -497,7 +497,7 @@
Returns the Drush Sanitize Interface namespace depending on the current version.
+ +
+ private
+ getDrushSanitizeInterface() : string
+
+ docker-compose vendor/bin/run toolkit:build-assets
- This will (re)generate the output file(s) defined on the config file(s).
-// Execute an available command from the ecl-builder list - Get help:
docker-compose exec web ./vendor/bin/run toolkit:build-assets --ecl-command=help
- For more detail, check the consolidation/annotated-command documentation.
-token [SKIP_INSECURE]
in the commit message.
All metapackages
and local packages are ignored.
Uses the Quality Assurance packages inventory to validate that no development packages are used in the production environment.
-Environment variables will be loaded by Docker Compose when running docker-compose up -d
.
overrides
key.
- You can simply copy/paste the tunnel url and visit your site.
-resources/git/hooks
folder.
- Alternatively you can use the option hooks
to enable a set of hooks.
Alternatively you can use the option hooks
to disable a set of hooks.
.git/hooks
directory.
- EcEuropa\Toolkit\TaskRunner\Commands\GitHooksCommands
- #!/bin/sh
./vendor/bin/run toolkit:hooks-run `basename "$0"` $1 $2
- Using default configuration, the development site files should be available in the web directory and the development site should be available at: http://localhost:8080/web.
-docker-compose exec web ./vendor/bin/run toolkit:build-dev
docker-compose exec web ./vendor/bin/run toolkit:install-clean --existing-config
- Below we explain the difference between setting up a new project and setting up an existing project:
-docker-compose exec web ./vendor/bin/run
- docker-compose exec web ./vendor/bin/run toolkit:run-phpcbf
- docker-compose exec web ./vendor/bin/run toolkit:test-phpunit
- docker-compose exec web ./vendor/bin/run toolkit:lint-js
- docker-compose exec web ./vendor/bin/run toolkit:lint-yaml
- Any customization done in your project will be respected in Drone build.
-docker-compose exec web ./vendor/bin/run toolkit:generate-documentation
-