liftedinit / liftedinit/roadmap
Deploy a website in a decentralized manner via API POC
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Description: This story is a POC for dweb hosting on Manifest. This story is to enable users to deploy their site via the hosting API. This should be able to be achieved by sending a ZIP file of the entire site and letting us unzip and deploy it. We will create a separate story for updating a site via the API. API should live in traditional cloud environment. Can deploy Liftedinit.org as a test POC.
API POC only contains hitting the API with a zip file.
As TLI, I want to deploy the liftedinit.org site via an API POC so that it is decentrally hosted on Manifest.
- [ ] Should be able to receive a ZIP file via API.
- [ ] Should be able to unzip the file and deploy the site.
- [ ] Should be demoed.
Assumptions:
- Site exits and has SSL.
- User management and auth exists.
Questions:
- Where does zip file go?
- How do we trigger the site update?
Contributor guide
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
Start with the API POC scope in this issue and confirm the assumptions about liftedinit.org, SSL, user management, and authentication. Resolve where the ZIP file goes and how deployment is triggered before implementation. Done means the API accepts a complete site ZIP, unzips and deploys it, and the result is demonstrated.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100