Question 1

How do I automatically deploy my Ghost theme from GitHub?

Accepted Answer

Set up a GitHub Actions workflow with this action, configure your API credentials as secrets in GitHub, and define deployment triggers in a YAML file. The README provides a step-by-step example to automate deployments on commits.

Question 2

Can I use this action with a self-hosted Ghost blog?

Accepted Answer

Yes, it works with any Ghost installation that has the Admin API enabled, including self-hosted instances. You need to generate API credentials from your Ghost Admin panel and store them as secrets.

Question 3

What's the best way to secure Ghost API keys in GitHub Actions?

Accepted Answer

Store them as encrypted secrets in your GitHub repository settings. The action uses these via the `secrets` context, ensuring they are not exposed in logs or code, following security best practices.

Question 4

How does GitHub Actions for Ghost theme compare to manual deployment?

Accepted Answer

Automated deployment saves time and reduces errors by triggering on code changes, ideal for frequent updates. Manual uploads offer more control for one-off changes but lack CI/CD integration.

Question 5

How to exclude files from my Ghost theme deployment?

Accepted Answer

Use the `exclude` option in the action configuration to list files or patterns, like 'gulpfile.js *dist/*', to omit from the zip file, reducing deployment size as recommended in the README.

Question 6

Does this support deploying themes from a subdirectory in my repo?

Accepted Answer

Yes, set the `working-directory` option to specify a custom directory, such as 'packages/my-theme', to zip and deploy themes located in subdirectories, per the configuration details.

Build and deploy a theme to Ghost CMS

What is Build and deploy a theme to Ghost CMS?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions