* Initial work to support curv
* Correct the initial code file location
* Preview and stl mvp working
* Prepare changes for review and preview build
* Run curv inside of /tmp
When exporting an stl it writes temporary files which is not allowed
when deployed to aws unless it's in temp.
* Lock in specific curv commit for reproducible builds
see: https://discord.com/channels/412182089279209474/886321278821216277/912507472441401385
* Add curv to backend schema
* Frontend changes to accommodate curv deploy
* Use vcount instead of vsize, as it's independant of geometry size,
This is good for CadHub usecase where we don't know anything about the
user's project
* Final tweaks for deploy
virtual screen size does matter,and curv is a little more memory hungry
than the other functions
* Format project
Co-authored-by: lf94 <inbox@leefallat.ca>
Co-authored-by: Kurt Hutten <k.hutten@protonmail.ch>
I've been able to get a proof of concept of downloading a openscad
library when the docker image builds
https://twitter.com/IrevDev/status/1400785325509660678
Since its experimental atm I'll leave it with just the one for now.
I've also got a local dev working again for the cad lambdas.
Resolves#338
