Commit all the ddev commands and home additions that are now there

This commit is contained in:
Benjamin Melançon 2019-08-08 17:35:33 -04:00
parent 9c3cdda643
commit c262f7becd
14 changed files with 180 additions and 0 deletions

16
.ddev/commands/db/README.txt Executable file
View file

@ -0,0 +1,16 @@
Scripts in this directory will be executed inside the db
container. A number of environment variables are supplied to the scripts, including:
DDEV_APPROOT: file system location of the project on the host)
DDEV_HOST_DB_PORT: Localhost port of the database server
DDEV_HOST_WEBSERVER_PORT: Localhost port of the webserver
DDEV_HOST_HTTPS_PORT: Localhost port for https on webserver
DDEV_DOCROOT: Relative path from approot to docroot
DDEV_HOSTNAME: Comma-separated list of FQDN hostnames
DDEV_PHP_VERSION
DDEV_WEBSERVER_TYPE: nginx-fpm, apache-fpm, apache-cgi
DDEV_PROJECT_TYPE: drupal8, typo3, backdrop, wordpress, etc.
DDEV_ROUTER_HTTP_PORT: Router port for http
DDEV_ROUTER_HTTPS_PORT: Router port for https
More environment variables may be available, see https://github.com/drud/ddev/blob/52c7915dee41d4846f9f619520b726994c0372c5/pkg/ddevapp/ddevapp.go#L1006-L1030

9
.ddev/commands/db/mysql Executable file
View file

@ -0,0 +1,9 @@
#!/bin/bash
## #ddev-generated
## Description: run mysql client in db container
## Usage: mysql [flags] [args]
## Example: "ddev mysql" or "ddev mysql -uroot -proot" or "echo 'SHOW TABLES;' | ddev mysql"
## `ddev mysql --database=mysql -uroot -proot` gets you to the 'mysql' database with root privileges
mysql -udb -pdb $@

View file

@ -0,0 +1,7 @@
#!/bin/bash
## Description: run mysqldump in web container
## Usage: mysqldump [flags] [args]
## Example: "ddev mysqldump db" or "ddev mysqldump otherdb" or "ddev mysqldump db | gzip >db.sql.gz"
mysqldump -uroot -proot $@

18
.ddev/commands/host/README.txt Executable file
View file

@ -0,0 +1,18 @@
Scripts in this directory will be executed on the host
but they can take easily take action on containers by using
`ddev exec`. A number of environment variables are supplied to the scripts
including:
DDEV_APPROOT: file system location of the project on the host)
DDEV_HOST_DB_PORT: Localhost port of the database server
DDEV_HOST_WEBSERVER_PORT: Localhost port of the webserver
DDEV_HOST_HTTPS_PORT: Localhost port for https on webserver
DDEV_DOCROOT: Relative path from approot to docroot
DDEV_HOSTNAME: Comma-separated list of FQDN hostnames
DDEV_PHP_VERSION
DDEV_WEBSERVER_TYPE: nginx-fpm, apache-fpm, apache-cgi
DDEV_PROJECT_TYPE: drupal8, typo3, backdrop, wordpress, etc.
DDEV_ROUTER_HTTP_PORT: Router port for http
DDEV_ROUTER_HTTPS_PORT: Router port for https
More environment variables may be available, see https://github.com/drud/ddev/blob/52c7915dee41d4846f9f619520b726994c0372c5/pkg/ddevapp/ddevapp.go#L1006-L1030

View file

@ -0,0 +1,31 @@
#!/bin/bash
## Description: Run MySQLWorkbench against current db
## Usage: mysqlworkbench
## Example: "ddev mysqlworkbench"
# Note that this examle uses $DDEV_HOST_DB_PORT to get the port for the connection
# Mysql Workbench can be obtained from https://dev.mysql.com/downloads/workbench/
query="root:root@127.0.0.1:${DDEV_HOST_DB_PORT}"
case $OSTYPE in
linux-gnu)
# You may need "apt-get install libproj-dev gnome-keyring" if it complains about those
mysql-workbench --query "$query" &
echo "Attempted to launch mysql-workbench"
;;
"darwin"*)
"/Applications/MySQLWorkbench.app/Contents/MacOS/MySQLWorkbench" --query "$query" &
echo "Attempted to launch MySQLWorkbench.app"
;;
"win*"* | "msys"*)
# 'C:\Program Files\MySQL\MySQL Workbench 8.0 CE\mysqlworkbench.exe'
# You may need to add it to your system %PATH% or change the path here
# On docker toolbox you'll need to change the query to use the toolbox IP address,
# likely 192.168.99.100
'C:\Program Files\MySQL\MySQL Workbench 8.0 CE\mysqlworkbench.exe' --query "$query"
#;;
esac

View file

@ -0,0 +1,8 @@
#!/bin/bash
## Description: Open PHPStorm with the current project
## Usage: phpstorm
## Example: "ddev phpstorm"
# Example is macOS-specific, but easy to adapt to any OS
open -a PHPStorm.app ${DDEV_APPROOT}

View file

@ -0,0 +1,10 @@
#!/bin/bash
## Description: Tail the main solr log
## Usage: solrtail
## Example: ddev solrtail
# This can't work unless you have a solr service,
# See https://ddev.readthedocs.io/en/latest/users/extend/additional-services/#apache-solr
ddev exec -s solr tail -40lf /opt/solr/server/logs/solr.log

24
.ddev/commands/solr/README.txt Executable file
View file

@ -0,0 +1,24 @@
Scripts in this directory will be executed inside the solr
container (if it exists, of course). This is just an example,
but any named service can have a directory with commands.
Note that /mnt/ddev_config must be mounted into the 3rd-party service
with a stanza like this in the docker-compose.solr.yaml:
volumes:
- type: "bind"
source: "."
target: "/mnt/ddev_config"
A number of environment variables are supplied to the scripts, including:
DDEV_DOCROOT: Relative path from approot to docroot
DDEV_HOSTNAME: Comma-separated list of FQDN hostnames
DDEV_PHP_VERSION
DDEV_WEBSERVER_TYPE: nginx-fpm, apache-fpm, apache-cgi
DDEV_PROJECT_TYPE: drupal8, typo3, backdrop, wordpress, etc.
DDEV_ROUTER_HTTP_PORT: Router port for http
DDEV_ROUTER_HTTPS_PORT: Router port for https
More environment variables may be available, see https://github.com/drud/ddev/blob/52c7915dee41d4846f9f619520b726994c0372c5/pkg/ddevapp/ddevapp.go#L1006-L1030

View file

@ -0,0 +1,12 @@
#!/bin/bash
## Description: Tail the main solr log
## Usage: solrtail
## Example: ddev solrtail
# This example runs inside the solr container.
# Note that this requires that /mnt/ddev_config be mounted
# into the solr container and of course that you have a container
# named solr.
tail -f /opt/solr/server/logs/solr.log

20
.ddev/commands/web/README.txt Executable file
View file

@ -0,0 +1,20 @@
Scripts in this directory will be executed inside the web
container. You can copy the example file or just rename it:
`mv drush.example drush`, for example, and it will become
a live command.
A number of environment variables are supplied to the scripts, including:
DDEV_APPROOT: file system location of the project on the host)
DDEV_HOST_DB_PORT: Localhost port of the database server
DDEV_HOST_WEBSERVER_PORT: Localhost port of the webserver
DDEV_HOST_HTTPS_PORT: Localhost port for https on webserver
DDEV_DOCROOT: Relative path from approot to docroot
DDEV_HOSTNAME: Comma-separated list of FQDN hostnames
DDEV_PHP_VERSION
DDEV_WEBSERVER_TYPE: nginx-fpm, apache-fpm, apache-cgi
DDEV_PROJECT_TYPE: drupal8, typo3, backdrop, wordpress, etc.
DDEV_ROUTER_HTTP_PORT: Router port for http
DDEV_ROUTER_HTTPS_PORT: Router port for https
More environment variables may be available, see https://github.com/drud/ddev/blob/52c7915dee41d4846f9f619520b726994c0372c5/pkg/ddevapp/ddevapp.go#L1006-L1030

View file

@ -0,0 +1,7 @@
#!/bin/bash
## Description: Run drush inside the web container
## Usage: drush [flags] [args]
## Example: "ddev drush uli" or "ddev drush sql-cli" or "ddev drush --version"
drush $@

View file

@ -0,0 +1,7 @@
#!/bin/bash
## Description: Reload config for nginx and php-fpm inside web container
## Usage: restart-nginx
## Example: "ddev restart-nginx"
killall -HUP nginx php-fpm

6
.ddev/homeadditions/README.txt Executable file
View file

@ -0,0 +1,6 @@
Files in .ddev/homeadditions will be copied into the web container's home directory.
An example bash_aliases.example is provided here. To make this file active you can either
cp bash_aliases.example .bash_aliases
or ln -s bash_aliases.example .bash_aliases

View file

@ -0,0 +1,5 @@
# To make this file active you can either
# cp bash_aliases.example .bash_aliases
# or ln -s bash_aliases.example .bash_aliases
alias ll="ls -lhA"