denoland / denoland/deploy_feedback
Suggestion: deployed project cloning
- Dominant language
- No language data
- Stars
- 79
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
Cloning a project to another user could be a very nice low hurdle route to small web app distribution.
Imagine you have a small web app that persists to sqlite. It proves useful enough that it might be of more general value. To scale it out to other users you need at a minimum to add auth and make the persistence multi-user. Not rocket science, but not a casual chore either.
If instead the deployed version of the app could be cloned to a new user, they get their own version of a single-user web app, with auth potentially taken care of by Deno Deploy. A sort of "self-hosting Lite".
A million wrinkles of course were this to be consumer-facing (though that's an interesting possibility - a Deno Deploy dev marketplace for self-hosted web apps?). But starting with github account holders as a cluey seed audience it might have possibilities.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.