5de4a7e75b
If we trigger a deploy, then we want the deploy to actually run. I am assuming that this was in place when there was a single GitHub Actions workflow that would trigger this all the time, even when nothing changed in `docs/**`. Since https://github.com/dagger/dagger/pull/1498, we no longer have this problem. After merging https://github.com/dagger/dagger/pull/1591, I was caught by this behaviour which to me seemed surprising. This change should make docs deploy via Netlify behave in a more predictable way. Signed-off-by: Gerhard Lazu <gerhard@lazu.co.uk>
43 lines
816 B
TOML
43 lines
816 B
TOML
[build]
|
|
publish = "build/"
|
|
command = "yarn build"
|
|
environment = { NODE_VERSION = "16.13.1" }
|
|
|
|
[context.production]
|
|
|
|
[context.deploy-preview]
|
|
command = "yarn build:withoutAuth"
|
|
|
|
[[redirects]]
|
|
# Embargoes compliance. DO NOT REMOVE
|
|
conditions = {Country = ["CU", "IR", "KP", "SY", "UA"]}
|
|
from = "/*"
|
|
to = "/restricted"
|
|
status = 302
|
|
force = true
|
|
|
|
[[redirects]]
|
|
from = "/github-proxy/*"
|
|
to = "https://github.com/:splat"
|
|
status = 200
|
|
|
|
[[redirects]]
|
|
from = "/github-api-proxy/*"
|
|
to = "https://api.github.com/:splat"
|
|
status = 200
|
|
|
|
[[redirects]]
|
|
from = "/docs-access/*"
|
|
to = "https://j20f3pfq11.execute-api.us-east-1.amazonaws.com/Prod/u/:splat"
|
|
status = 200
|
|
|
|
[[redirects]]
|
|
from = "/t"
|
|
to = "https://api.amplitude.com"
|
|
status = 200
|
|
|
|
[[redirects]]
|
|
from = "/reference"
|
|
to = "/reference/alpine"
|
|
status = 302
|