* Latest npm in @colanode/web Docker, add optional plat/arch dependencies
There are a number of issues with lightningcss and node 22/npm.
This is related to platform-/architecture-specific packages.
This uses a number of pieces from multiple solutions found in the notes
for #160.
This addresses the issues by the following measures:
- Make sure npm is up-to-date in the @colanode/web Docker build
- Add optional dependencies for all the platform-specific lightningcss
packages that are most likely to be used in the project (HSF and
mainline) in the npm project modules that require them:
- @colanode/desktop
- @colanode/web
- @colanode/ui
Closes#159.
* Fix darwin-arm64 version.
* Remove unnecessary optional dependencies; remove duplicate version property
* Fix merge issue where the version field got deleted.
* Move the version field back to where it was before.
Between 0.2.9 and 0.3.0, there were changes in dependencies that caused
the types to become incompatible between Uint8Array and
FileSystemWriteChunkType where the base compatible type is ArrayBuffer
but Uint8Array is based on ArrayBufferLike, which can be an
ArrayBuffer but also can be a number of other incompatible types, and
is thus incompatible with FileSystemWriteChunkType.
I introduced a compatibility layer (Adapter Pattern-like) to copy the
buffer into an ArrayBuffer if it is not an ArrayBuffer, otherwise just
use the buffer if it already is.
* Track upload progress in clients
* Implement client side jobs
* Separate local files, downloads and uploads
* Use dates instead of timestamps in jobs
* Improve some recurring jobs
* Local file improvements
* Remove job schedules on cancel
* Improve avatar handling
* Fix manual download
* Improve file uploads and downloads
* Improve downloads
* Use tus resumable uploads
* Drop file states table migration
* Remove some unused file system methods and types
* Use Redis KV and Locker for distributed TUS deployments
* Fix file name generation
* Add uploads clean job
* Have a dedicated endpoint for TUS uploads
* Do not revert uploads state because ot TUS resumables
* Use integer instead of text for job and job schedule status
* Rename a query
* Fix error handling for file uploads and downloads jobs
* Check node sync for file uploads
* Rename the temp files clean job
* Minor renames for consistency
* Improve uploads badge
* Small refactor in server job service
* Add env varaibles config for some tus stuff
* Use ms package for millisecond conversions
* Fix some migrations
* Fix logout
* Update hosting values
* Add Helm chart for Kubernetes deployment and reorganize hosting setup
- Created Helm chart for deploying Colanode on Kubernetes with PostgreSQL, Redis, and MinIO configurations
- Moved Docker Compose files to /hosting folder for better organization
- Added health check endpoints for database, Redis, and S3 services
- Introduced Dockerfile for PostgreSQL with pgvector extension to support Helm deployment
- Added GitHub Actions workflow for building and publishing Helm chart
- Updated README with Kubernetes deployment instructions
* Renames and restructure
* Update Helm chart workflow for Colanode deployment
* Remove health check route and related configurations from the server and Kubernetes deployment files.
---------
Co-authored-by: Hakan Shehu <hakanshehu15@gmail.com>
Closes#68
When the desktop app is running on os.platform() === 'win32', the path
requires preprocessing before it can be used as part of a local file
URI.
The logical components of this fix are:
- Add / in front of an absolute path (a path with a drive root like C:)
that is already present in *nix paths because that's how the fs
already represents an absolute path
- Convert all \ to / to conform to the file:// URI spec
This commit adds the required preprocessing in the file-system and
protocols modules of the desktop app and fixes the issue of the
disappearing account button in the SidebarMenuFooter UI component when
a custom avatar is used for the user account that is logged in.
