Welcome to the new era of micro saas! Our company has established itself as the leading digital micro saas platform in France.
Since when? Since 2020, we've been supporting individuals and businesses who want to create their own saas easily, with just a few clicks, and in just a few seconds.
But what's exactly Saashup ?
Saashup is a simple solution for saasifying your application. We assist you in promoting your application and simplifying its management. Build and develop your software, and let us deploy it to your customers through your own customized SaaS. Our services remain flexible and scalable, adapting to your business needs.
The fd will only be used to stor it temporary since, we first need to sent headers, and the headers need to be sent before the bofy. The server base os working fine now with accept and a patch request os already sent to bash. So probaböy on the next release accept will be full usable.
Since now, multiple concurrent connections will work after my patch. (Need to add subshell) i will need to consider using fd as output cache. Instead of temporary files.
I follow some projects from you on github. Keep up the work!
Falling back to something like socat, would destroy the whole idea behind it. I think the best way is patching accept and shipping it with the project. Like this no need to fallback.
And considering using something like socat, will force you to fork each request into a new process, which will be slow as hell.
I worked before on a web framework, which was used behind httpd or nginx as cgi, it was fast. But the moment where you get more connections it was slow as hell.
The idea of this project is writing some kind of fastCGI (like php-fpm), but for this i would need, to allow multithreading etc..
Well that's true. I took me two hours to get this done. Since accept was not clear at the beginning. But it will be cleaner in the future, i'm still not convinced how it works currently.