* feat(server): allow ratelimiting to be explicitly disabled
- allows rate limiter to be enabled or disabled explicitly
- example .env file for testing now explicitly disables it
- disables rate limiter in CI tests, except where explicitly testing the rate limiter
* first pass of CLI ifc converter
* some updates
* closer
* yarn works
* can execute ifc?
* change exe
* remove extra venv needs
* invocation works
* fixed dockerfile and url
* refactor(fileimport): temp results path should not be hardcoded in parsers
* update importer to output stuff
* fix up argments
* remove dead code
* adjust dockerfile to have tini and workdir better
* fix node to a specific version
* Add shell statement and pin yarn version
* add ifc converter c# to ignore
* merge fix
* move ifc c#
* fix the api usage
* update the importer to new SDK
* Adds a feature flag `FF_FILEIMPORT_IFC_DOTNET_ENABLED` for enabling .Net IFC parser
* move directories
* put back ifc js
* use FF and reversions
* needs token too
* fix docker?
* one last copy fix
* adjust prettier ignore
* change to enable
* fix helm chart nesting
* Amend healthcheck node binary path
* Add FF_FILEIMPORT_IFC_DOTNET_ENABLED to feature flag parser
* Allow app to write to /.config directory
* fix: volume name has to be lower case
* update ifc importing
---------
Co-authored-by: Iain Sproat <68657+iainsproat@users.noreply.github.com>
Co-authored-by: root <root@Clynelish>
* fix(workspaces): allow workspace delete for paid workspaces
* feat(gendo): multi region gendo with new api integration and limits
* feat(gendo): user credits
* feat: adds limits to gendo panel, and terms and conditions link
* fix: reworks setting back camera view
* feat(gendo): webhook signature verification
* fix(gendo): nullability
* test(blobstorage): fix test dependency injection
---------
Co-authored-by: Dimitrie Stefanescu <didimitrie@gmail.com>
* feat(helm chart): include multi-region feature flag and volume from secret
* fix monitoring deployment template
* Add environment variables to all services
* feat(projects): add project regions, default to null
* feat(multiregion): add projectRegion Db client lookup logic
* feat(multiregion): add project region repositories and caching
* feat(multiRegion): db initialization and get project db client
* feat(docker-compose): add second db for regions testing
* feat(multiRegion): initialize region with pubs and subs working
* fix(multiRegion): get region client even if it was registered in another pod
* feat(workspaces): create workspace resolver split
* feat: update server region metadata
* feat(projects): rewrite project creation
* feat(multiRegion): getRegionDb
* fix(workspaces): get projects now can retur null
* feat(multiRegion): make local multi region DB-s work
* feat: set d efault workspace region
* CR changes
* tests
* feat(multiRegion): bind region properly
* fe update
* test fixes
* feat(multiRegion): automatically create aiven extras plugin
* ci(postgres): use published postgres with aiven extras
* fix(multiRegion): roll back the aiven extras migration, there is a better way
* tests fix
* fix(billing): we do not need to add a seat, if the workspace is on a plan, but has no sub
---------
Co-authored-by: Kristaps Fabians Geikins <fabis94@live.com>
* feat(multi region config): mount file and read config from file
* feat(helm): allow multi region config to be mounted from a secret
* Allow the file name to be amended
* Initial work
* fallback image
* Update api name
* Add read time
* Filter out newly updated stories
* Update webflow.ts
* Add NuxtImg
* Update webflow.ts
* Update Card.vue
* Rename to Webflow Items
* Helm changes
* Rename webflow to blog
* useAsyncData
* Throw error if no API
- this makes the chart more robust and the behaviour can be determined at template time
- previously, the unique values were removed by kubernetes which made modification difficult
* chore(dockerfile): move to distroless
- remove unnecessary env vars (these are provided via the deployment system)
- uses relative paths if in a working directory
* Amend entrypoint for use with distroless
* Update startup probe & docker compose readiness probe
- when sending Speckle objects to the server, they are batched into multi-part files
- a multi-part file therefore contains one or more Speckle objects
- the maximum limit for the multi-part file must therefore be greater than the maximum limit for a single Speckle object
Iain Sproat