|
|
4 years ago | |
|---|---|---|
| .devcontainer | 0774d3eebb - Fix named volume name | 5 years ago |
| .github | e3647e6236 organize npm scripts for linting and testing | 4 years ago |
| .vscode | 9d0cb75d37 update debug settings | 4 years ago |
| bin | fe302dcfd1 mv bin | 4 years ago |
| packages | c74b4526f3 Merge branch 'master' into feat/6450 | 4 years ago |
| public | cafe48ebec Merged master | 4 years ago |
| tmp | cafe48ebec Merged master | 4 years ago |
| .editorconfig | 2d42c72e58 add .editorconfig | 9 years ago |
| .eslintignore | d694b3cfe0 organize lint settings | 4 years ago |
| .eslintrc.js | 04a35e1bd0 organize eslint packages and settings | 4 years ago |
| .gitignore | db7b299cb6 organize .gitignore | 4 years ago |
| .markdownlint.yml | e465990009 update .markdownlint.yml | 6 years ago |
| .prettierrc | 4c699fe833 apply stylelint | 7 years ago |
| .stylelintrc.json | d694b3cfe0 organize lint settings | 4 years ago |
| CHANGES.md | 730639188c Merge remote-tracking branch 'origin/master' into support/make-app-monorepo | 4 years ago |
| LICENSE | 282f6c3101 Update LICENSE | 8 years ago |
| README.md | 2f24e0348c remove unnecessary lines | 4 years ago |
| README_JP.md | 2f24e0348c remove unnecessary lines | 4 years ago |
| THIRD-PARTY-NOTICES.md | e120411d72 add EmojiOne to THIRD-PARTY-NOTICES.md | 6 years ago |
| lerna.json | 5292a2b245 add lerna | 5 years ago |
| package.json | 6c33d53206 organize npm scripts | 4 years ago |
| tsconfig.base.json | 99fd5ad853 support optional chaining | 4 years ago |
| yarn.lock | 2d416cc7d8 use tsconfig-paths-webpack-plugin | 4 years ago |
| demonstration |
|---|
![]() |
Migration Guide from Crowi (en/ja) is here.
See GROWI Docs: Admin Guide (en/ja).
See GROWI Docs: Environment Variables (en/ja).
| command | desc |
|---|---|
yarn app:build |
Build GROWI app client |
yarn app:server |
Launch GROWI app server |
yarn start |
Invoke yarn app:build and yarn app:server |
For more info, see GROWI Docs: List of npm Commands.
If you found a bug in the source code, you can help us by submitting an issue to our GitHub Repository. Even better, you can submit a Pull Request with a fix.
You can request a new feature by submitting an issue to our GitHub Repository. If you would like to implement a new feature, firstly please submit the issue with your proposal to make sure we can confirm it. Please clarify what kind of change you would like to propose.
You can write issues and PRs in English or Japanese.
If you have questions or suggestions, you can join our Slack team and talk about anything, anytime.
