Roadmap

[miguelrk]

This issue exists as a continually growing roadmap. In general, there should be 3 ways of deploying a project in implementation order:

• 1. Deploy within Netzo: enable quick edits and simple deployments (alpha: not the best DX in editor)
• 2. Deploy with netzo/cli: enables local development and manual deployment via netzo deploy
• 3. Deploy with Github integration: enables automatic deployment and source control via GitHub
  • 3a. Automatic: link a repo+branch in app, set up webhook in github, and let api listen to new commits on push
  • 3b. Github Action: ability to customize deployment with additional steps in workflow (advanced)

netzo/cli

Preview Give feedback

1. [cli] add deploy subcommand (local --> remote) netzo#11
   priority: high type: feature +2
   
2. [cli] add upgrade subcommand netzo#12
   priority: high type: feature +2
   
3. [cli] add clone subcommand netzo#13
   priority: high type: feature +2
   
4. [cli] add logs subcommand netzo#14
   priority: medium type: feature +2
   
5. [cli] add "Automatic" deployments netzo#15
   flag: future priority: low type: feature +3
   

netzo/lib

Preview Give feedback

1. [ui] add unocss-preset-netzo (instead of components library) netzo#9
   priority: high type: feature +2
2. [modules] add restdb module to serve a REST API for Deno KV netzo#10
   group: modules priority: medium type: idea +3
   
3. [apis] add support for oauth2 authentication netzo#16
   priority: medium type: feature +2
   

DevOps

Preview Give feedback

1. [scripts] build item.fs of templates dynamically by walking file tree netzo#17
   priority: medium type: enhancement +2
   

[miguelrk]

Closing to track using GitHub projects