Open vgalin opened 1 year ago
We will add a section explaining how it works on the README.
We plan to have an "on prem" solution at some point. The SaaS offering will allow us to refine the produce first.
this behavior deviates from the original textual where the 'apps' were obviously run locally
Just to be clear too: your applications are still run "locally"; as in they're still run on the machine that you're running textual-web
on; but the communication with the client browser goes via our servers.
Is there a way to test fully locally as of today? Or the SaaS part of it is an integral part of the solution and can’t be left aside?
It depends on a server component that we host, which you can't yet run locally.
It depends on a server component that we host, which you can't yet run locally.
Got it. Thanks.
[A web search led me to this thread, so I'll ask my follow-up question here:]
Is one of the goals of Textual Web to be able to package a CLI app so that it can run in a browser, in a way that I can upload some files to my server to run at mydomain.com/myapp/
?
It depends on a server component that we host, which you can't yet run locally.
Is there any update on local hosting here? This seems like a handy tool for local development but I don't want to expose anything to the web.
Hello, I recently tested
textual-web
within a corporate network and encountered this warning/error:This led me to realize that apps run through
textual-web
are not hosted locally but are instead served from a third-party server, generating a unique URL. I find this worth mentioning explicitly in the README for clarity and to set proper user expectations, especially because this behavior deviates from the originaltextual
where the 'apps' were obviously run locally.Could you consider updating the README to specify this information?
Additionally, are there any plans to support local hosting of Textual apps using
textual-web
in the future?