Simplify the process of deploying static files

[BitPatty]

Is your feature request related to a problem? Please describe.

CapRover makes it easy to deploy containerized applications, but the procedure to deploy static files still comes with a bit of an overhead such as:

0. Understanding the docs on how this process works
1. Creating a definition file
2. Packing the application
3. Requiring the CapRover CLI to be installed (and knowing how it works).

Describe the solution you'd like

It'd be great if I could upload a simple zip (or tar) file (containing just the static files) via the Web UI and have CapRover automatically set up nginx to serve these files without having to go through steps 1 and 3 (and most of 0). This would allow anyone quickly to spin up a demo page for their project on a CapRover instance without all the technical setup/knowledge.

[Andrewpk]

Also it's worth mentioning that the documented process for deploying static web sites involves having a nginx container running, while caprover itself is already running an instance of nginx. It would be awesome to reduce this overhead for users with memory constrained servers.

[githubsaturn]

@Andrewpk - curious to know what your use case is? how much memory does your nginx container use?