We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
If /app/web is not being used as Drupal root, for example /app/docroot, no-robots.sh:7 fails to write robots.txt in non-production environments.
/app/web
/app/docroot
govcmslagoon/.docker/images/nginx/no-robots.sh
Lines 6 to 8 in 264a413
[govcms7-paas]nginx:/app$ sh /lagoon/entrypoints/20-no-robots.sh /lagoon/entrypoints/20-no-robots.sh: line 7: can't create /app/web/robots.txt: nonexistent directory
Maybe doing something like this would help PaaS scallywags?
if [ ! "${LAGOON_ENVIRONMENT_TYPE}" == "production" ]; then printf "User-agent: *\nDisallow: /\n" > /"${APP_DIR:-app}"/"${WEBROOT:-web}"/robots.txt fi
The text was updated successfully, but these errors were encountered:
govCMS#130 Fix No-robots.sh entrypoint fails if using non-standard Dr…
a4ebd39
…upal root.
Note that /app/web is utilized only in Drupal 8, where /app is used for Drupal 7. Will have to double-check that, but to me the above is expected...
Sorry, something went wrong.
The govcmslagoon/.docker/images/nginx/no-robots.sh entrypoint is simply incorrect for D7; should point to /app for SaaS and /app/docroot for PaaS.
/app
There is another block in place at the nginx level (https://github.com/govCMS/govcmslagoon/blob/develop/.docker/images/nginx/helpers/200-no_robots_govcms_host.conf) - but this is not a blanket rule for all non-production environments.
Great pickup, thanks @thompsong
No branches or pull requests
If
/app/web
is not being used as Drupal root, for example/app/docroot
, no-robots.sh:7 fails to write robots.txt in non-production environments.govcmslagoon/.docker/images/nginx/no-robots.sh
Lines 6 to 8 in 264a413
Maybe doing something like this would help PaaS scallywags?
The text was updated successfully, but these errors were encountered: