Skip to content

fix: properly handle paths in init-container.sh#136

Merged
mcdurdin merged 1 commit intomasterfrom
fix/135-cdnrefresh-path
Feb 19, 2025
Merged

fix: properly handle paths in init-container.sh#136
mcdurdin merged 1 commit intomasterfrom
fix/135-cdnrefresh-path

Conversation

@mcdurdin
Copy link
Member

Allows CDN refresh to run on production, which called resources/init-container.sh instead of ./init-container.sh.

Fixes: #135

@mcdurdin mcdurdin added this to the B18S2 milestone Feb 19, 2025
@mcdurdin mcdurdin added the fix label Feb 19, 2025
@mcdurdin mcdurdin requested a review from darcywong00 February 19, 2025 06:49
Copy link
Contributor

@darcywong00 darcywong00 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

Why would the cwd be different now?

Allows CDN refresh to run on production, which called
`resources/init-container.sh` instead of `./init-container.sh`.

Fixes: #135
@mcdurdin mcdurdin force-pushed the fix/135-cdnrefresh-path branch from 58bffa3 to 96a3c79 Compare February 19, 2025 06:52
@mcdurdin
Copy link
Member Author

lgtm

Why would the cwd be different now?

This has been broken for a long time. A longer term fix is to add set -eu into our deploy scripts to catch these errors. If /cdn/deploy does not exist, then the cdn infrastructure uses /cdn/dev instead, so things "work" on dev sites etc. But it's not great.

We have some other cdn issues also, e.g. references to images etc in css stylesheets is difficult.

@mcdurdin mcdurdin merged commit 035feb3 into master Feb 19, 2025
2 checks passed
@mcdurdin mcdurdin deleted the fix/135-cdnrefresh-path branch February 19, 2025 06:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

bug: cdn deployment is not working in production

2 participants