Skip to content
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

Test with wget-spider.sh on every build #390

Open
obscurerichard opened this issue Jan 5, 2025 · 0 comments
Open

Test with wget-spider.sh on every build #390

obscurerichard opened this issue Jan 5, 2025 · 0 comments
Labels
enhancement good first issue help wanted Help wanted - can you take this on? infrastructure Issues requiring changes to cloud, database, or server infrastructure

Comments

@obscurerichard
Copy link
Member

obscurerichard commented Jan 5, 2025

In #161 we introduced test/wget-spider.sh and we now run it vs. producton on every deploy (see #256) vs. the production site.

We should also be running this on every build. But to do that, we have to have a running site for every build. So this is blocked by not having a test site of some kind. freezingsaddles/freezing-compose#57 would resolve that by having GitHub Actions spin up an ephemeral test site for every build. So this would get unblocked when that is available.

@obscurerichard obscurerichard added enhancement good first issue help wanted Help wanted - can you take this on? infrastructure Issues requiring changes to cloud, database, or server infrastructure labels Jan 5, 2025
@obscurerichard obscurerichard added this to the 2025 - Competition End milestone Jan 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement good first issue help wanted Help wanted - can you take this on? infrastructure Issues requiring changes to cloud, database, or server infrastructure
Projects
Status: To do
Development

No branches or pull requests

1 participant