-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
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
Update caddy to 2.8 #70
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm fine with merging as-is, if you view this as too minor to address.
sed -i 's/# tls cert.pem key.pem/tls cert.pem key.pem/g' proxy/Caddyfile | ||
rm allow.acl deny.acl | ||
sed -i.bak 's/# tls cert.pem key.pem/tls cert.pem key.pem/g' proxy/Caddyfile | ||
rm proxy/Caddyfile.bak allow.acl deny.acl |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same here... Why create a .bak file if we have no intention of leaving it around?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
because sed -i 's...
doesn't work on macos (-i requires an argument) and the internet says that while sed -i ''
will work on macos it will break on linux. The only fully cross-platform way is to create the backup file and then remove it
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ahhhh, so that's the M1-specific update you made... I was wondering.
Do you want to leave a comment to that effect, with a reference? That will stop ignorant folks like me from removing it in future updates.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
would it make more sense to just install gnu-sed with homebrew?
Changes:
validate
is still broken due to incompatible architecture issuesMarking this as draft until I'm able to deploy this to a known-working 2.7 proxy setup to verify no downstream surprises