docs: consistently reference dokku.me

docs/configuration/domains.md

@@ -60,7 +60,7 @@ The domains plugin allows you to specify custom domains for applications. This p
 # where `node-js-app` is the name of your app
 
 # add a domain to an app
-dokku domains:add node-js-app example.com
+dokku domains:add node-js-app dokku.me
 
 # list custom domains for app
 dokku domains node-js-app
@@ -69,10 +69,10 @@ dokku domains node-js-app
 dokku domains:clear node-js-app
 
 # remove a custom domain from app
-dokku domains:remove node-js-app example.com
+dokku domains:remove node-js-app dokku.me
 
 # set all custom domains for app
-dokku domains:set node-js-app example.com example.org
+dokku domains:set node-js-app dokku.me dokku.org
 ```
 
 ## Displaying domains reports about an app
@@ -88,19 +88,19 @@ dokku domains:report
 ```
 =====> node-js-app domains information
        Domains app enabled: true
-       Domains app vhosts:  ruby-sample.example.org
+       Domains app vhosts:  ruby-sample.dokku.org
        Domains global enabled: true
-       Domains global vhosts: example.org
+       Domains global vhosts: dokku.org
 =====> python-sample domains information
        Domains app enabled: true
-       Domains app vhosts:  ruby-sample.example.org
+       Domains app vhosts:  ruby-sample.dokku.org
        Domains global enabled: true
-       Domains global vhosts: example.org
+       Domains global vhosts: dokku.org
 =====> ruby-sample domains information
        Domains app enabled: true
-       Domains app vhosts:  ruby-sample.example.org
+       Domains app vhosts:  ruby-sample.dokku.org
        Domains global enabled: true
-       Domains global vhosts: example.org
+       Domains global vhosts: dokku.org
 ```
 
 You can run the command for a specific app also.
@@ -112,9 +112,9 @@ dokku domains:report node-js-app
 ```
 =====> node-js-app domains information
        Domains app enabled: true
-       Domains app vhosts:  node-js-app.example.org
+       Domains app vhosts:  node-js-app.dokku.org
        Domains global enabled: true
-       Domains global vhosts: example.org
+       Domains global vhosts: dokku.org
 ```
 
 You can pass flags which will output only the value of the specific information you want. For example:

docs/configuration/ssl.md

@@ -97,11 +97,11 @@ dokku certs:report node-js-sample
 =====> node-js-sample ssl information
        Ssl dir:             /home/dokku/node-js-sample/tls
        Ssl enabled:         true
-       Ssl hostnames:       *.example.org example.org
+       Ssl hostnames:       *.dokku.org dokku.org
        Ssl expires at:      Oct  5 23:59:59 2019 GMT
        Ssl issuer:          C=GB, ST=Greater Manchester, L=Salford, O=COMODO CA Limited, CN=COMODO RSA Domain Validation Secure Server CA
        Ssl starts at:       Oct  5 00:00:00 2016 GMT
-       Ssl subject:         OU=Domain Control Validated; OU=PositiveSSL Wildcard; CN=*.example.org
+       Ssl subject:         OU=Domain Control Validated; OU=PositiveSSL Wildcard; CN=*.dokku.org
        Ssl verified:        self signed.
 ```
 

docs/deployment/one-off-processes.md

@@ -140,7 +140,7 @@ The following is a sample cronfile that you can use for your applications:
 
 ```cron
 # server cron jobs
-MAILTO="mail@example.com"
+MAILTO="mail@dokku.me"
 PATH=/usr/local/bin:/usr/bin:/bin
 SHELL=/bin/bash
 

docs/deployment/zero-downtime-deploys.md

@@ -145,15 +145,15 @@ The `CHECKS` file can contain multiple checks:
 To check an application that supports multiple hostnames, use relative URLs that include the hostname:
 
 ```
-//admin.example.com  Admin Dashboard
-//static.example.com/logo.png
+//admin.dokku.me  Admin Dashboard
+//static.dokku.me/logo.png
 ```
 
 You can also specify the protocol to explicitly check HTTPS requests:
 
 ```
-https://admin.example.com  Admin Dashboard
-https://static.example.com/logo.png
+https://admin.dokku.me  Admin Dashboard
+https://static.dokku.me/logo.png
 ```
 
 While a full url may be used in order to invoke checks, if you are using relative urls, the port *must* be omitted.
@@ -325,13 +325,13 @@ curl: (7) Failed to connect to 172.17.0.155 port 5000: Connection refused
        Listening on 0.0.0.0:5000, CTRL+C to stop
 =====> end node-js-app container output
 -----> Running post-deploy
------> Configuring myapp.dokku.example.com...
+-----> Configuring myapp.dokku.me...
 -----> Creating http nginx.conf
 -----> Running nginx-pre-reload
        Reloading nginx
 -----> Shutting down old container in 60 seconds
 =====> Application deployed:
-       http://myapp.dokku.example.com
+       http://myapp.dokku.me
 ```
 
 ## Example: Failing Rails Deployment
@@ -433,7 +433,7 @@ Could not start due to 1 failed checks.
          vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.0/lib/active_record/connection_adapters/postgresql_adapter.rb:44:in `postgresql_connection
 =====> end node-js-app container output
 /usr/bin/dokku: line 49: 23409 Killed                  dokku deploy "$APP"
-To dokku@dokku.example.com:myapp
+To dokku@dokku.me:myapp
  ! [remote rejected] dokku -> master (pre-receive hook declined)
-error: failed to push some refs to 'dokku@dokku.example.com:myapp'
+error: failed to push some refs to 'dokku@dokku.me:myapp'
 ```

docs/development/plugin-triggers.md

@@ -998,7 +998,7 @@ set -eo pipefail; [[ $DOKKU_TRACE ]] && set -x
 
 APP="$1";
 
-curl "https://example.com/starting/${APP}" || true
+curl "https://dokku.me/starting/${APP}" || true
 ```
 
 ### `proxy-build-config`
@@ -1102,7 +1102,7 @@ plugn trigger receive-app $APP $newrev
 set -eo pipefail; [[ $DOKKU_TRACE ]] && set -x
 APP="$1"; HOSTNAME=$(hostname -s)
 
-mail -s "$APP containers on $HOSTNAME failed to retire" ops@example.com
+mail -s "$APP containers on $HOSTNAME failed to retire" ops@dokku.me
 ```
 
 ### `report`