Show HN: Use GitHub Actions to serve a serverless service
1–10 of 13 posts
Re: Show HN: Use GitHub Actions to serve a serverless service
#2Re: Show HN: Use GitHub Actions to serve a serverless service
#3This goes against githubs TOS and is not the first project to do so.
Re: Show HN: Use GitHub Actions to serve a serverless service
#4This goes against githubs TOS and is not the first project to do so.
was the other project also using github actions?
Take a look:
https://docs.github.com/en/github/site-policy/github-additio...
Specifically: "any activity that places a burden on our servers, where that burden is disproportionate to the benefits provided to users (for example, don't use Actions as a content delivery network or as part of a serverless application, but a low benefit Action could be ok if it’s also low burden); or"
Re: Show HN: Use GitHub Actions to serve a serverless service
#5Earlier quoted context omitted.
was the other project also using github actions?
Yes, got killed pretty quickly. Take a look: https://docs.github.com/en/github/site-policy/github-additio... Specifically: "any activity that places a burden on our servers, where that burden is disproportionate to the benefits provided to users (for example, don't use Actions as a content delivery network or as part of a serverless application, but a low benefit Action could be ok if it’s also low burden); or"
Re: Show HN: Use GitHub Actions to serve a serverless service
#6Re: Show HN: Use GitHub Actions to serve a serverless service
#7Re: Show HN: Use GitHub Actions to serve a serverless service
#8Re: Show HN: Use GitHub Actions to serve a serverless service
#9Is this anything besides a static website that could be hosted on S3 just as well? Seems like you're just using Actions to compile the static assets, which is probably not as good as doing it locally.
This is not the same as running locally.