kubernetes/contrib
Eric Paris 4b309aa864 Do not use {} in systemd environment variables
From the systemd man page:
 Use "${FOO}" as part of a word, or as a word of its own, on the command
 line, in which case it will be
 replaced by the value of the environment variable including
 all whitespace it contains, resulting in a single argument.
 Use "$FOO" as a separate word on the
 command line, in which case it will be replaced
 by the value of the environment variable split at
 whitespace, resulting in zero or more arguments.

Since we want people to be able to use these for multiple arguments we
need to make sure we don't use {} around the env vars...
2015-02-05 11:36:55 -05:00
..
completions/bash remove --ns-path option from .kubeconfig file, kick tests 2015-02-03 14:22:55 -05:00
for-demos Reduce size of serve_hostname image 2015-01-24 09:49:26 -08:00
for-tests/network-tester Fix contrib webserver so that it compiles. 2015-02-02 15:20:28 -08:00
init/systemd Do not use {} in systemd environment variables 2015-02-05 11:36:55 -05:00
logging Launch Elasticsearch and Kibana automatically 2015-01-09 13:41:46 -08:00
podex README: shorter filename 2015-02-04 11:31:54 -08:00
recipes Fix up for posix flags 2015-01-15 09:12:19 -08:00