[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-3642":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":10,"totalLinesOfCode":10,"stars":12,"forks":13,"watchers":14,"openIssues":15,"contributorsCount":16,"subscribersCount":16,"size":16,"stars1d":17,"stars7d":18,"stars30d":19,"stars90d":16,"forks30d":16,"starsTrendScore":18,"compositeScore":20,"rankGlobal":10,"rankLanguage":10,"license":21,"archived":22,"fork":22,"defaultBranch":23,"hasWiki":24,"hasPages":22,"topics":25,"createdAt":10,"pushedAt":10,"updatedAt":41,"readmeContent":42,"aiSummary":43,"trendingCount":16,"starSnapshotCount":16,"syncStatus":44,"lastSyncTime":45,"discoverSource":46},3642,"platform","hcengineering\u002Fplatform","hcengineering","Huly — All-in-One Project Management Platform (alternative to Linear, Jira, Slack, Notion, Motion)","https:\u002F\u002Fhuly.io",null,"TypeScript",26170,1933,79,780,0,15,63,285,44.86,"Eclipse Public License 2.0",false,"develop",true,[26,27,28,29,30,31,32,33,34,35,36,37,38,39,40],"applicant-tracking-system","chat-application","crm","crm-platform","hrms","human-resources","issue-management","issue-tracker","jira-alternative","project-management","qms","support","team-management","team-platform","wiki","2026-06-12 02:00:52","# Huly Platform\n\n[![X (formerly Twitter) Follow](https:\u002F\u002Fimg.shields.io\u002Ftwitter\u002Ffollow\u002Fhuly_io?style=for-the-badge)](https:\u002F\u002Fx.com\u002Fhuly_io)\n![GitHub License](https:\u002F\u002Fimg.shields.io\u002Fgithub\u002Flicense\u002Fhcengineering\u002Fplatform?style=for-the-badge)\n\n⭐️ Your star shines on us. Star us on GitHub!\n\n## About\n\nThe Huly Platform is a robust framework designed to accelerate the development of business applications, such as CRM systems.\nThis repository includes several applications, such as Chat, Project Management, CRM, HRM, and ATS.\nVarious teams are building products on top of the Platform, including [Huly](https:\u002F\u002Fhuly.io) and [TraceX](https:\u002F\u002Ftracex.co).\n\n![Huly](https:\u002F\u002Frepository-images.githubusercontent.com\u002F392073243\u002F6d27d5cc-38cd-4d88-affe-bb88b393180c)\n\n## Self-Hosting\n\nIf you're primarily interested in self-hosting Huly without the intention to modify or contribute to its development, please use [huly-selfhost](https:\u002F\u002Fgithub.com\u002Fhcengineering\u002Fhuly-selfhost).\nThis project offers a convenient method to host Huly using `docker`, designed for ease of use and quick setup. Explore this option to effortlessly enjoy Huly on your own server.\n\n## Activity\n\n![Alt](https:\u002F\u002Frepobeats.axiom.co\u002Fapi\u002Fembed\u002Fc42c99e21691fa60ea61b5cdf11c2e0647621534.svg 'Repobeats analytics image')\n\n## API Client\n\nIf you want to interact with Huly programmatically, check out our [API Client](https:\u002F\u002Fgithub.com\u002Fhcengineering\u002Fhuly.core\u002Ftree\u002Fmain\u002Fpackages\u002Fapi-client) documentation. The API client provides a typed interface for all Huly operations and can be used to build integrations and custom applications.\n\nYou can find API usage examples in the [Huly examples](https:\u002F\u002Fgithub.com\u002Fhcengineering\u002Fhuly-examples) repository.\n\n## Changelog\n\nFor detailed information about changes, improvements, and bug fixes in each version, see our [Changelog](.\u002Fchangelog.md).\n\n## Versions\n\nThe Huly Platform uses two types of version tags to distinguish between production-ready and development releases:\n\n- **Production Versions (`v*`)** - Stable releases for end users\n  - Example: `v0.7.310`, `v0.7.307`, `v0.6.501`\n  - These versions are recommended for production deployments\n  - Suitable for self-hosted installations\n  - Published with release notes on [GitHub Releases](https:\u002F\u002Fgithub.com\u002Fhcengineering\u002Fplatform\u002Freleases)\n\n- **Development Versions (`s*`)** - Pre-release builds for developers\n  - Example: `s0.7.313`, `s0.7.292`, `s0.7.288`\n  - Used for development and testing purposes\n  - May contain experimental features or bug fixes\n  - Not recommended for production use\n\n## Architecture\n\nFor detailed information about the platform architecture, services, and their interactions, see our [Architecture Overview](.\u002FARCHITECTURE_OVERVIEW.md).\n\n## Table of Contents\n\n- [Huly Platform](#huly-platform)\n  - [About](#about)\n  - [Self-Hosting](#self-hosting)\n  - [Activity](#activity)\n  - [API Client](#api-client)\n  - [Changelog](#changelog)\n  - [Versions](#versions)\n  - [Architecture](#architecture)\n  - [Table of Contents](#table-of-contents)\n  - [Pre-requisites](#pre-requisites)\n  - [Verification](#verification)\n  - [Branches \\& Contributing](#branches--contributing)\n  - [Setup dev environment](#setup-dev-environment)\n  - [Fast start](#fast-start)\n  - [Installation](#installation)\n  - [Build and run](#build-and-run)\n  - [Run in development mode](#run-in-development-mode)\n  - [Update project structure and database](#update-project-structure-and-database)\n  - [Troubleshooting](#troubleshooting)\n  - [Build \\& Watch](#build--watch)\n  - [Tests](#tests)\n    - [Unit tests](#unit-tests)\n    - [UI tests](#ui-tests)\n  - [Package publishing](#package-publishing)\n  - [Additional testing](#additional-testing)\n  - [WSL build guide](#wsl-build-guide)\n\n## Pre-requisites\n\n- Before proceeding, ensure that your system meets the following requirements:\n  - [Node.js](https:\u002F\u002Fnodejs.org\u002Fen\u002Fdownload\u002F) (v20.11.0 is required)\n  - [Docker](https:\u002F\u002Fdocs.docker.com\u002Fget-docker\u002F)\n  - [Docker Compose](https:\u002F\u002Fdocs.docker.com\u002Fcompose\u002Finstall\u002F)\n\n## Verification\n\nTo verify the installation, perform the following checks in your terminal:\n\n- Ensure that the `docker` commands are available:\n\n```bash\ndocker --version\ndocker compose version\n```\n\n## Branches & Contributing\n\n- The `main` branch is the default branch used for production deployments.\n  Changes to this branch are made from the `staging` branch once a version is ready for community use.\n\n- The `staging` branch is used for pre-release testing.\n  It is stable enough for testing but not yet ready for production deployment.\n\n- The `develop` branch is used for development and is the default branch for contributions.\n\nWe periodically merge `develop` into `staging` to perform testing builds. Once we are satisfied with the build quality in our pre-release deployment, we merge changes into `main` and release a new version to the community.\n\n## Setup dev environment\n\n### To initialise the communication submodule\n\n```bash\ngit submodule init\ngit submodule update\n```\n\n### To update the communication submodule\n\n```bash\ngit submodule update\n```\n\n### Authentication\n\nThis project uses GitHub Packages for dependency management. To successfully download dependencies, you need to generate a GitHub personal access token and log in to npm using that token.\n\nFollow these steps:\n\n1. Generate a GitHub Token:\n- Log in to your GitHub account\n- Go to **Settings** > **Developer settings** > **Personal access tokens** (https:\u002F\u002Fgithub.com\u002Fsettings\u002Fpersonal-access-tokens)\n- Click **Generate new token**\n- Select the required scopes (at least `read:packages`)\n- Generate the token and copy it\n\n2. Authenticate with npm:\n```bash\nnpm login --registry=https:\u002F\u002Fnpm.pkg.github.com\n```\n\nWhen prompted, enter your GitHub username, use the generated token as your password\n\n\n## Fast start\n\n```bash\nsh .\u002Fscripts\u002Ffast-start.sh\n```\n\n## Installation\n\nYou need Microsoft's [rush](https:\u002F\u002Frushjs.io) to install the application.\n\n1. Install Rush globally using the command:\n\n```bash\nnpm install -g @microsoft\u002Frush\n```\n\n2. Navigate to the repository root and run the following commands:\n\n```bash\nrush install\nrush build\n```\n\nAlternatively, you can just execute:\n\n```bash\nsh .\u002Fscripts\u002Fpresetup-rush.sh\n```\n\n## Build and run\n\nDevelopment environment setup requires Docker to be installed on system.\n\nSupport is available for both amd64 and arm64 containers on Linux and macOS.\n\n```bash\ncd .\u002Fdev\u002F\nrush build    # Will build all the required packages.\n# rush rebuild  # could be used to omit build cache.\nrush bundle   # Will prepare bundles.\nrush package  # Will build all webpack packages.\nrush validate # Will validate all sources with typescript and generate d.ts files required for ts-node execution.\nrush svelte-check # Optional. svelte files validation using svelte-check.\nrush docker:build   # Will build Docker containers for all applications in the local Docker environment.\nrush docker:up # Will set up all the containers\n```\n\nBe aware `rush docker:build` will automatically execute all required phases like build, bundle, package.\n\n> **Note:** For resource-constrained machines, you can use the minified variants `rush docker:min` and `rush docker:up:min` to build and run only the required services (excludes hulypulse, redis, process, backup, rating, preview, link-preview, elastic, fulltext, payment, stats, print, sign, hulygun, hulykvs).\n\nAlternatively, you can just execute:\n\n```bash\nsh .\u002Fscripts\u002Fbuild.sh\n```\n\nBy default, Docker volumes named dev_db, dev_elastic, and dev_files will be created for the MongoDB, Elasticsearch, and MinIO instances.\n\nAdd the following lines to your hosts file:\n\n- **macOS \u002F Linux:** `\u002Fetc\u002Fhosts`\n- **Windows:** `C:\\Windows\\System32\\drivers\\etc\\hosts`\n\n```plain\n127.0.0.1 huly.local\n::1 huly.local\n```\n\nAccessing the URL \u003Chttp:\u002F\u002Fhuly.local:8087> will lead you to the app in development mode.\n\nLimitations:\n\n- Local installation does not support sending emails, thus disabling functionalities such as password recovery and email notifications.\n\n## Run in development mode\n\nDevelopment mode allows for live reloading and a smoother development process.\n\n```bash\ncd dev\u002Fprod\nrush validate\nrushx dev-server\n```\n\nThen go to \u003Chttp:\u002F\u002Flocalhost:8080>\n\nSelect \"Sign up\" on the right panel and click the \"Sign up with password\" link at the bottom. Enter the new user's credentials, then proceed to create a workspace for them.\n\n## Update project structure and database\n\nIf the project's structure is updated, it may be necessary to relink and rebuild the projects.\n\n```bash\nrush update\nrush build\n```\n\n## Troubleshooting\n\nIf a build fails, but the code is correct, try to delete the [build cache](https:\u002F\u002Frushjs.io\u002Fpages\u002Fmaintainer\u002Fbuild_cache\u002F) and retry.\n\n```bash\n# from the project root\nrm -rf common\u002Ftemp\u002Fbuild-cache\n```\n\n## Build & Watch\n\nFor development purpose `rush build:watch` action could be used.\n\nIt includes build and validate phases in watch mode.\n\n## Tests\n\n### Unit tests\n\n```bash\nrush test # To execute all tests\n\nrushx test # For individual test execution inside a package directory\n```\n\n### UI tests\n\n```bash\ncd .\u002Ftests\nrush build\nrush bundle\nrush docker:build\n## creates test Docker containers and sets up test database\n.\u002Fprepare.sh\n## runs UI tests\nrushx uitest\n```\n\nTo execute tests in the development environment, please follow these steps:\n\n```bash\ncd .\u002Ftests\n.\u002Fcreate-local.sh ## use .\u002Frestore-local.sh if you only want to restore the workspace to a predefined initial state for sanity.\ncd .\u002Fsanity\nrushx dev-uitest # To execute all tests against the development environment.\nrushx dev-debug -g 'pattern' # To execute tests in debug mode with only the matching test pattern.\n```\n\n## Package publishing\n\n```bash\nnode .\u002Fcommon\u002Fscripts\u002Fbump.js -p projectName\n```\n\n## Additional testing\n\nThis project is tested with BrowserStack.\n\n## WSL build guide\n\nThis guide describes the nuances of building and running the application from source code located on your NTFS drive, which is accessible from both Windows and WSL.\n\n### Prerequisites\n\n#### Disk Space Requirements\n\nEnsure you have sufficient disk space available:\n- A fully deployed local application in clean Docker will consume slightly more than **35 GB** of WSL virtual disk space\n- The application folder after build (sources + artifacts) will occupy **4.5 GB**\n\nIf there's insufficient space on your system drive (usually `C:\\`), you can change the virtual disk location in Docker Settings → Resources → Advanced.\n\n#### Docker WSL Integration\n\nMake sure Docker is accessible from WSL:\n\n1. Go to Docker Settings → Resources → Advanced → WSL Integration\n2. Select the distribution where you'll be building and running the application\n3. Verify integration works by running this command in WSL:\n   ```bash\n   docker run hello-world\n   ```\n\n### Common Issues and Solutions\n\n#### Git Line Endings on Windows\n\nWindows Git often automatically replaces line endings. Since most build scripts are `.sh` files, ensure your Windows checkout doesn't break them.\n\n**Solution options:**\n- Checkout from WSL instead of Windows\n- Configure Git on Windows to disable auto-replacement:\n  ```bash\n  git config --global core.autocrlf false\n  ```\n  This disables auto-replacement for all repositories on your machine.\n\n#### Elevated Privileges in WSL\n\nSome commands in the instructions require elevated privileges when working in WSL. If you're using Ubuntu distribution, prefix commands with `sudo`:\n\n```bash\nsudo npm install -g @microsoft\u002Frush\n```\n\n#### WSL Configuration\n\nIf the source code is located on a Windows NTFS drive, then edit the `\u002Fetc\u002Fwsl.conf` file in WSL (e.g., `sudo nano \u002Fetc\u002Fwsl.conf`) and add the following content if it doesn't exist:\n\n```ini\n[automount]\nenabled = true\nroot = \u002Fmnt\u002F\noptions = \"metadata,umask=22,fmask=11\"\n\n[interop]\nappendWindowsPath = false\n```\n\nHowever, we recommend storing the repository on a WSL disk, as this dramatically improves build and maintenance operations.\n\n### Running the Application\n\nAfter these preparations, the build instructions should work without issues.\n\n#### Port Conflicts\n\nWhen starting the application (`rush docker:up`), some network ports in Windows might be occupied. You can fix port mapping in the `\\dev\\docker-compose.yaml` file.\n\n**Important:** Depending on which port you change, you'll need to:\n1. Find what's using that port\n2. Update the new address in the corresponding service configuration\n\n\u003Csub>\u003Csup>© 2025 \u003Ca href=\"https:\u002F\u002Fhardcoreeng.com\">Hardcore Engineering Inc\u003C\u002Fa>.\u003C\u002Fsup>\u003C\u002Fsub>\n","Huly Platform 是一个一体化项目管理平台，旨在替代Linear、Jira、Slack、Notion等工具。其核心功能包括聊天应用、项目管理、CRM系统、HRM以及ATS等，使用TypeScript编写，支持高度自定义和扩展。技术特点上，Huly提供了丰富的API接口以方便与其他系统集成，并且支持通过Docker进行快速部署。该平台非常适合需要在一个统一环境中管理多个业务流程的团队或企业使用，无论是初创公司还是大型机构都能从中受益。",2,"2026-06-11 02:55:10","top_language"]