cadquery-server icon indicating copy to clipboard operation
cadquery-server copied to clipboard

A web server used to render 3d models from CadQuery code loaded dynamically.

Results 35 cadquery-server issues
Sort by recently updated
recently updated
newest added

To visually separate the pars I use different colors for my models: ```` python show_object(partA, options={"alpha":0.2, "color": (64, 164, 223)}, name='Part A') ```` Also the _alpha_ property is very useful...

_This issue is copied from https://github.com/CadQuery/cadquery/issues/1181_. The issue appears not to be specifically with `cadquery-server` (given that it appears when I run `python example.py`) but rather with the Docker image...

Image: latest (0.4.1) Steps to reproduce: create folder with an cadquery example (here: _/home/Peedy/Projects/docker/cadquery/test.py_) launch docker instance as described in README.md `docker run -p 5000:5000 -v /home/Peedy/Projects/docker/cadquery:/data cadquery/cadquery-server` Instance fails...

You can now download your models using the endpoint /download. You need to specify the parameters `m` for which module and `format` for which format you want it in. Ex:...

Using the `gh-pages` branch is not practical when working with git, if we don't want the website content pushed on main branch. Using gh action should fix this.

good first issue

## `/api/sandbox` - `/` - `POST`: retrieve some code as plain text and return the resulting model in the given format ## `/api/models/` - `GET`: retrieve information about all models...

- `/`: used to show the website main page from where a user can select a project. - `/api/`: DCI openAPI endpoint (#54), which is not available on exported static...

The readme starts to be a bit long. A documentation website built with [MkDocs](https://github.com/mkdocs/mkdocs) and published on github pages should be nice. The website generation and content must be integrated...

good first issue

Or, if a solution is found to have the same behavior without the extension, update instructions in the cqe readme and mark the extension as obsolete / archived.

waiting external action