You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
sed -i "s|PROJECT_ROOT_VALUE|$PWD|g" nginx-proxy.conf
fails on OSX because -i (edit in-place) expects an extension to backup the original file, so
sed -i .orig "s|PROJECT_ROOT_VALUE|$PWD|g" nginx-proxy.conf
will work, but man sed actually tells you to put -i right before the filename
sed "s|PROJECT_ROOT_VALUE|$PWD|g" -i nginx-proxy.conf
or better sed "s|PROJECT_ROOT_VALUE|$PWD|g" -i .orig nginx-proxy.conf
Wouldn't it be even better to have nginx-proxy.conf.template files and only create nginx-proxy.conf after replacing the variables? That way you can always run make init again if something changed.
Like so: sed "s|PROJECT_ROOT_VALUE|$PWD|g" nginx-proxy.conf.template > nginx-proxy.conf
The text was updated successfully, but these errors were encountered:
# Using | instead of / because $PWD contains /'s
sed "s|PROJECT_ROOT_VALUE|$PWD|g
s|PROJECT_NAME_VALUE|$PROJECT_NAME|g" nginx-proxy.conf.template > nginx-proxy.conf
sed "s|PROJECT_NAME_VALUE|$PROJECT_NAME|g" nginx.conf.template > nginx.conf
sed "s|NGINX_PORT=80|NGINX_PORT=$NGINX_PORT|g
s|PROJECT_NAME_VALUE|$PROJECT_NAME|g" .env.template > .env
sed -i "s|PROJECT_ROOT_VALUE|$PWD|g" nginx-proxy.conf
fails on OSX because -i (edit in-place) expects an extension to backup the original file, so
sed -i .orig "s|PROJECT_ROOT_VALUE|$PWD|g" nginx-proxy.conf
will work, but
man sed
actually tells you to put -i right before the filenamesed "s|PROJECT_ROOT_VALUE|$PWD|g" -i nginx-proxy.conf
or better
sed "s|PROJECT_ROOT_VALUE|$PWD|g" -i .orig nginx-proxy.conf
Wouldn't it be even better to have nginx-proxy.conf.template files and only create nginx-proxy.conf after replacing the variables? That way you can always run
make init
again if something changed.Like so:
sed "s|PROJECT_ROOT_VALUE|$PWD|g" nginx-proxy.conf.template > nginx-proxy.conf
The text was updated successfully, but these errors were encountered: