github actions (5 posts)

As I posted before, this blog is running on GCP Cloud Run and also is built with Next.js. https://blog.petitviolet.net/post/2021-12-28/running-a-blog-powered-by-next.js-on-cloud-run Previously, before migrating to Next.js from Gatsby, this blog used to get deployed automatically via GitHub Action

Previously, I posted about how to deploy this blog via GitHub Actions to Google AppEngine. https://blog.petitviolet.net/post/2020-03-10/deploy-blog-via-github-actions However, because of recent updates, it started failing. This post describes how to update the GitHub Action configurations to fix

When I write a new blog entry, I'd like to schedule its publishing since usually write them at night and it's not a good time to make it open. As I write in [the last post](/post/deploy-blog-via-github-actions), this blog is running on GAE and deployed via GitHub Actions when PR is merged. Therefor

[The previous entry](/post/deploy-blog-via-github-actions) describes how to deploy static sites through GitHub Actions. As the next step, this entry is going to show how to manage new entries, and also how to publish entries based on schedules. Deploy preview versions triggered by pull requests

This blog(https://blog.petitviolet.net) is hosted on Google AppEngine(a.k.a GAE). GAE is super useful not only for dynamic WEB applications but also for static sites. To deploy applications and sites on GAE, it just needs to call gcloud app deploy command. Speaking of GAE deployments, it usuall