Releases: speckleworks/SpeckleServer
Speckle Server
Chagelog 1.5.2:
- Fixes some problems with the query criteria and field projection in the
StreamGetAll
route.
Speckle Server
Chagelog 1.5.1:
- hotfix on
StreamGetAll
route
Changelog 1.5.0:
Loads of bugfixes, and some backwards compatible upgrades. Most notably:
- frontend plugin registration system see #77 and the new api description of the server or, even better, the sample plugin page
- websocket rooms for any resource (stream, project, comment, user, objects) so you can propagate live updates for individual objects.
- fixed #82, which was a bit of a hassle
- better logging (logs are now also piped into daily rotated files rotated in /logs)
- added env vars for defaulting streams to public or private
- #85, #86, #76, #95, #97 (but in a backwards compatible way)
Speckle Server
Change log:
// TODO
1.0.0-beta
Finally a clean and nice api. See the latest specs, or just poke inside.
Speckle Server 0.0.4
Speckle Server will now better use available VM resources. Docker images and installation instructions have been bumped and CI has been set.
Speckle Server 0.0.3 Hotfix Release
Limits request sizes to 3mb deflated, anything over gets a 413
error. Reasons: see #39
Speckle Server 0.0.3 (Release for DOI)
Please ignore this release! It's there for the EU's zenodo open access, etc. that are part of Innochain's requirements.
Speckle Server 0.0.3-controllers 🎚
Merge pull request #33 from speckleworks/improving-stream-put-post Improving stream put post
Speckle Server 0.0.3 🦉
Scaffolded some routes and added the forgotten ObjectsGetBulk
route, which is a POST request masquerading as a GET with a request body.
Speckle Server 0.0.3-prerelease
Fixes most of the issues and potentially introduces more. For the full api docs head to the api docs.