Skip to content

[Website] Make deployment script more usable for self-hosting #2764

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.

Sign up for GitHub

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

Jump to bottom
Merged
brandonpayton merged 8 commits into from
Oct 11, 2025
Merged

[Website] Make deployment script more usable for self-hosting #2764

brandonpayton merged 8 commits into from
Oct 11, 2025

Conversation

@brandonpayton
Copy link
Member

@brandonpayton brandonpayton commented Oct 10, 2025

Motivation for the change, related issues

The Telex project wants to self-host Playground and pin it to a specific version. This is a PR to make deployment to WP Cloud easier for folks like them.

Implementation details

This PR:

  • Adds a GIT_REF_TO_DEPLOY var so users can configure the workflow environment to deploy a specific branch, tag, or revision.
  • Adds a CORS_PROXY_URL var to allow folks to choose their CORS proxy.
  • Renames the workflow file from build-website.yml to deploy-website.yml to better match its purpose.
  • Makes names within the workflow more generic with self-hosting in mind. For example, "Deploy to playground.wordpress.net" becomes "Deploy Playground website".
  • Updates to actions/checkout@v5 since we might as well make the updates when touching this workflow.
  • Deletes the private deploy workflow because it is redundant and no longer used.

Testing Instructions (or ideally a Blueprint)

  • Test deploying to other WP Cloud site in Playground fork. This is already done here.
  • Test deploying to playground.wordpress.net after merge.

@brandonpayton brandonpayton requested a review from a team October 10, 2025 03:16
@brandonpayton brandonpayton self-assigned this Oct 10, 2025
@brandonpayton
Copy link
Member Author

brandonpayton commented Oct 10, 2025

Note:
This PR adds requires two new variables from its GitHub Actions environment, and those are already set here for the WordPress/wordpress-playground repo.

Screenshot 2025-10-09 at 11 18 56 PM

@brandonpayton
Copy link
Member Author

brandonpayton commented Oct 10, 2025 •
edited
Loading

I plan to merge this and test the deploy today, but to avoid invalidating the cache while folks are still working, let's wait until later this evening.

@brandonpayton brandonpayton merged commit 4205266 into trunk Oct 11, 2025
28 checks passed
@brandonpayton brandonpayton deleted the deployment/support-deploying-specific-branch branch October 11, 2025 02:31
@brandonpayton
Copy link
Member Author

brandonpayton commented Oct 11, 2025

I ran a deploy after merge, and it looks like everything is working well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

@brandonpayton brandonpayton

Labels

[Aspect] Website [Package][@wp-playground] Client [Package][@wp-playground] Remote [Type] Developer Experience

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@brandonpayton