mirror of
				https://codeberg.org/yeentown/barkey.git
				synced 2025-11-04 07:24:13 +00:00 
			
		
		
		
	docs: 開発環境のセットアップ手順を詳細にする (#14235)
* docs: mentioning Devcontainer fix #13753 * revise * revise 2 * Apply suggestions from code review per https://github.com/misskey-dev/misskey/pull/14235#discussion_r1680883942 Co-authored-by: anatawa12 <anatawa12@icloud.com> * 下の方にあったDevcontainerのセクションをマージ * revise 3 * Update CONTRIBUTING.md https://github.com/misskey-dev/misskey/pull/14235#discussion_r1680928026 Co-authored-by: おさむのひと <46447427+samunohito@users.noreply.github.com> * mention Meilisearch * Update CONTRIBUTING.md --------- Co-authored-by: anatawa12 <anatawa12@icloud.com> Co-authored-by: おさむのひと <46447427+samunohito@users.noreply.github.com>
This commit is contained in:
		
							parent
							
								
									de166a8ed4
								
							
						
					
					
						commit
						e716c201c6
					
				
					 1 changed files with 32 additions and 20 deletions
				
			
		| 
						 | 
					@ -106,6 +106,38 @@ If your language is not listed in Crowdin, please open an issue.
 | 
				
			||||||

 | 
					
 | 
				
			||||||
 | 
					
 | 
				
			||||||
## Development
 | 
					## Development
 | 
				
			||||||
 | 
					### Setup
 | 
				
			||||||
 | 
					Before developing, you have to set up environment. Misskey requires Redis, PostgreSQL, and FFmpeg.
 | 
				
			||||||
 | 
					
 | 
				
			||||||
 | 
					You would want to install Meilisearch to experiment related features. Technically, meilisearch is not strict requirement, but some features and tests require it.
 | 
				
			||||||
 | 
					
 | 
				
			||||||
 | 
					There are a few ways to proceed.
 | 
				
			||||||
 | 
					
 | 
				
			||||||
 | 
					#### Use system-wide software
 | 
				
			||||||
 | 
					You could install them in system-wide (such as from package manager).
 | 
				
			||||||
 | 
					
 | 
				
			||||||
 | 
					#### Use `docker compose`
 | 
				
			||||||
 | 
					You could obtain middleware container by typing `docker compose -f $PROJECT_ROOT/compose.local-db.yml up -d`.
 | 
				
			||||||
 | 
					
 | 
				
			||||||
 | 
					#### Use Devcontainer
 | 
				
			||||||
 | 
					Devcontainer also has necessary setting. This method can be done by connecting from VSCode.
 | 
				
			||||||
 | 
					
 | 
				
			||||||
 | 
					Instead of running `pnpm` locally, you can use Dev Container to set up your development environment.
 | 
				
			||||||
 | 
					To use Dev Container, open the project directory on VSCode with Dev Containers installed.  
 | 
				
			||||||
 | 
					**Note:** If you are using Windows, please clone the repository with WSL. Using Git for Windows will result in broken files due to the difference in how newlines are handled.
 | 
				
			||||||
 | 
					
 | 
				
			||||||
 | 
					It will run the following command automatically inside the container.
 | 
				
			||||||
 | 
					``` bash
 | 
				
			||||||
 | 
					git submodule update --init
 | 
				
			||||||
 | 
					pnpm install --frozen-lockfile
 | 
				
			||||||
 | 
					cp .devcontainer/devcontainer.yml .config/default.yml
 | 
				
			||||||
 | 
					pnpm build
 | 
				
			||||||
 | 
					pnpm migrate
 | 
				
			||||||
 | 
					```
 | 
				
			||||||
 | 
					
 | 
				
			||||||
 | 
					After finishing the migration, you can proceed.
 | 
				
			||||||
 | 
					
 | 
				
			||||||
 | 
					### Start developing
 | 
				
			||||||
During development, it is useful to use the
 | 
					During development, it is useful to use the
 | 
				
			||||||
 | 
					
 | 
				
			||||||
```
 | 
					```
 | 
				
			||||||
| 
						 | 
					@ -135,26 +167,6 @@ MK_DEV_PREFER=backend pnpm dev
 | 
				
			||||||
- To change the port of Vite, specify with `VITE_PORT` environment variable.
 | 
					- To change the port of Vite, specify with `VITE_PORT` environment variable.
 | 
				
			||||||
- HMR may not work in some environments such as Windows.
 | 
					- HMR may not work in some environments such as Windows.
 | 
				
			||||||
 | 
					
 | 
				
			||||||
### Dev Container
 | 
					 | 
				
			||||||
Instead of running `pnpm` locally, you can use Dev Container to set up your development environment.
 | 
					 | 
				
			||||||
To use Dev Container, open the project directory on VSCode with Dev Containers installed.  
 | 
					 | 
				
			||||||
**Note:** If you are using Windows, please clone the repository with WSL. Using Git for Windows will result in broken files due to the difference in how newlines are handled.
 | 
					 | 
				
			||||||
 | 
					 | 
				
			||||||
It will run the following command automatically inside the container.
 | 
					 | 
				
			||||||
``` bash
 | 
					 | 
				
			||||||
git submodule update --init
 | 
					 | 
				
			||||||
pnpm install --frozen-lockfile
 | 
					 | 
				
			||||||
cp .devcontainer/devcontainer.yml .config/default.yml
 | 
					 | 
				
			||||||
pnpm build
 | 
					 | 
				
			||||||
pnpm migrate
 | 
					 | 
				
			||||||
```
 | 
					 | 
				
			||||||
 | 
					 | 
				
			||||||
After finishing the migration, run the `pnpm dev` command to start the development server.
 | 
					 | 
				
			||||||
 | 
					 | 
				
			||||||
``` bash
 | 
					 | 
				
			||||||
pnpm dev
 | 
					 | 
				
			||||||
```
 | 
					 | 
				
			||||||
 | 
					 | 
				
			||||||
## Testing
 | 
					## Testing
 | 
				
			||||||
- Test codes are located in [`/packages/backend/test`](/packages/backend/test).
 | 
					- Test codes are located in [`/packages/backend/test`](/packages/backend/test).
 | 
				
			||||||
 | 
					
 | 
				
			||||||
| 
						 | 
					
 | 
				
			||||||
		Loading…
	
	Add table
		
		Reference in a new issue