sillsdev / sillsdev/appbuilder-buildengine-api
Support publishing PWA to GitHub/Cloudflare
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
We know of at least one Scriptoria user who is not storing their PWA in Scriptoria because they are using GitHub to store the PWA build output and then publishing it to Cloudflare pages.
Questions:
- What credentials would be necessary?
- Could this be accomplished with a Personal Access Token (PAT)?
- Pros: only one thing to store
- Cons: Have a limited lifespan, though this can technically be set to infinite?
- Could this be accomplished with a Personal Access Token (PAT)?
- Security concerns? Should these be private repositories? If private, could create difficulty for us to debug.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named in the issue. Start by defining the GitHub and Cloudflare Pages publishing flow, required credentials, repository visibility, token lifetime, and security expectations with the maintainers. Done should mean an agreed implementation scope and acceptance criteria for safely publishing a PWA build.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, typescript
- Domain
- api, cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100