Guess this is a longshot but Im trying to avoid having to deploy a separate webserver (apache/ngnix/jetty etc…) to provide additional material/functionality related to the content in a specific metabase installation.
For example, if I had a static html page called “mystuff.html” could I share it through the metabase server and access it as a resource/endpoint, something like: http://localhost:3000/mystuff.
I know we have the cards option but Im looking to include functionality such as html form submission that would be, I believe, beyond its capabilities, and yes I could reverse my approach an embed metabase in a separate application but Im trying to minimize my overall footprint.
Thanks in advance.