bevyengine / bevyengine/bevy-website

Host PR branches somewhere publicly accessible

Open
#313 16 comments 1 reaction 0 assignees View on GitHub
A-Book A-Build-System
Dominant language
JavaScript
Stars
249
Forks
450
Avg merge
16h 20m
Merged PRs (30d)
6

Description

We want to be able to host a dev version of the website to make collaboration easier. The main issue stopping us is that github pages can only host a single branch.

Here are the some of the possible options:

- Vercel https://vercel.com
- https://vercel.com/pricing
- The main issue with vercel is that they ask too many github permissions when setting it up
- Cloudflare pages https://pages.cloudflare.com
- Netlify https://www.netlify.com
- https://www.netlify.com/pricing/
- Asks for a reasonable amount of permissions and I believe we can stay on the free tier
- Self-host
- Needs a server, needs to maintain it, needs something to autodeploy and generate url for deployed PR
- Not free

Contributor guide

Open the contributing guide

Research direction

No repository files, tests, or entry points are named. Start by mapping the existing GitHub Pages deployment and PR workflow, then compare Vercel, Cloudflare Pages, Netlify, and self-hosting against permissions, cost, maintenance, and automatic preview URLs. Done means the project has a decided and documented way to publish publicly accessible PR branches.

Written by the indexing model from the issue text.

Assessment

Tech stack
github, javascript
Domain
ci-cd, cloud, devops
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.