-
-
Notifications
You must be signed in to change notification settings - Fork 7
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[skip ci] docs: automated update to docs
skip-checks: true
- Loading branch information
1 parent
8e4fb05
commit 694cd7c
Showing
22 changed files
with
128 additions
and
112 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
28 changes: 28 additions & 0 deletions
28
docs/documents/contributing/development-environment/codespaces.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,28 @@ | ||
[**playnite-web-app**](../../../README.md) • **Docs** | ||
|
||
*** | ||
|
||
[playnite-web-app](../../../README.md) / contributing/development-environment/codespaces | ||
|
||
# Developer Environment: Codespace | ||
|
||
## Required Software | ||
|
||
Install the following software on your local machine: | ||
|
||
1. [vscode](https://code.visualstudio.com/Download) | ||
2. XServer (for running Cypress tests in codespace). | ||
- For OSX, recommend: [XQuartz](https://www.bing.com/ck/a?!&&p=c21da4f99329c03fJmltdHM9MTcxODg0MTYwMCZpZ3VpZD0zOTJjZTBlOC1iMzRjLTY3Y2MtMDU4NC1mM2NkYjI2MDY2NjUmaW5zaWQ9NTIyNw&ptn=3&ver=2&hsh=3&fclid=392ce0e8-b34c-67cc-0584-f3cdb2606665&psq=xquartz+&u=a1aHR0cHM6Ly93d3cueHF1YXJ0ei5vcmcv&ntb=1) | ||
- For Windows, still need a recommendation. | ||
|
||
## Preparing Codebase | ||
|
||
1. [Fork the playnite-web repo](https://github.com/andrew-codes/playnite-web/fork) | ||
2. Ensure your XServer application is running on local machine. | ||
- Ensure your XServer is configured to Authenticate and Allow Connections from network clients | ||
3. Start a codespace and open in vscode. | ||
4. Run `yarn` | ||
5. Run `yarn run start` | ||
6. In vscode, forward port 3000. This can be found in same pane as the terminal. | ||
7. Open [http://localhost:3000](http://localhost:3000). | ||
8. Continue to see [commands](./index.md#running-playnite-web) for running tests. |
44 changes: 44 additions & 0 deletions
44
docs/documents/contributing/development-environment/index.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,44 @@ | ||
[**playnite-web-app**](../../../README.md) • **Docs** | ||
|
||
*** | ||
|
||
[playnite-web-app](../../../README.md) / contributing/development-environment/index | ||
|
||
# Development Environment | ||
|
||
- [Development Environment](#development-environment) | ||
- [Overview](#overview) | ||
- [Running Playnite Web](#running-playnite-web) | ||
- [Playnite Web Plugin Development](#playnite-web-plugin-development) | ||
|
||
## Overview | ||
|
||
There are a few options for running Playnite Web for local development. Choose and follow one of the paths below. Then proceed to the next section. | ||
|
||
1. (preferred) [Local environment](local-environment.md), directly on your development machine (requires installing required tooling such as Node.js, yarn, etc.). | ||
2. Via a GitHub codespace (the plugin cannot be run this way). | ||
3. Via Docker and the included dev container (the plugin cannot be run this way). | ||
|
||
> Note the second and third options maybe encounter issues or additional configuration when running component and E2E tests. | ||
## Running Playnite Web | ||
|
||
| Application | Command | Notes | | ||
| :--------------- | :-------------------------------- | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | ||
| Playnite Web App | `yarn run start` | Run Playnite Web application locally. Navigate to [https://localhost:3000](https://localhost:3000) in a browser. Environment variables are pulled from `./apps/playnite-web/local.env`. | | ||
| Playnite Web App | `yarn run test/components` | Run component tests for development. | | ||
| Playnite Web App | `yarn run test/components/update` | Run component tests with intention to update a baseline screenshot. | | ||
| Playnite Web App | `yarn yarn run test/e2e` | Run end-to-end (e2e) tests for development (including visual regression capabilities). A consistent database restored along with consistent game assets. This ensures a reliable data set to test against. | | ||
| Playnite Web App | `yarn yarn run test/e2e/update` | Run end-to-end (e2e) tests with intention to update a baseline screenshot. | | ||
|
||
## Playnite Web Plugin Development | ||
|
||
To develop the Playnite Web plugin, a Windows machine is required. Playnite must be installed. Recommendation is to use Visual Studio Community edition for development. | ||
|
||
1. Install required software | ||
- Playnite | ||
- Visual Studio | ||
2. Open the solution file in Visual Studio; located in `apps/PlayniteWebPlugin/src/PlayniteWeb.sln`. | ||
3. Build the solution. | ||
4. Open Playnite and add the path to the bin directory as a local plugin. This setting is found under the Developer section in the settings. | ||
5. Debugging opens Playnite with the plugin installed. |
36 changes: 36 additions & 0 deletions
36
docs/documents/contributing/development-environment/local-environment.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,36 @@ | ||
[**playnite-web-app**](../../../README.md) • **Docs** | ||
|
||
*** | ||
|
||
[playnite-web-app](../../../README.md) / contributing/development-environment/local-environment | ||
|
||
# Developer Environment: Local | ||
|
||
## Required Software | ||
|
||
Install the following software on your local development machine: | ||
|
||
1. git | ||
2. Bash (this guide assumes a bash shell) | ||
3. [vscode](https://code.visualstudio.com/Download) | ||
4. [Docker](https://www.docker.com/products/docker-desktop/) (for Mongodb and MQTT dependencies) | ||
5. [Node.js@>=22.5.0](https://nodejs.org/en/download/package-manager) (recommend using `nvm` to manage Node.js installations) | ||
- [nvm for OSX](https://github.com/nvm-sh/nvm) | ||
- [nvm for Windows](https://github.com/coreybutler/nvm-windows) | ||
6. [yarn@^4.0.0](https://yarnpkg.com/getting-started) | ||
- With Node.js installed, run `corepack enable && corepack prepare --activate yarn@^4.0.0 && yarn set version berry` | ||
|
||
## Preparing Codebase | ||
|
||
1. [Fork the playnite-web repo](https://github.com/andrew-codes/playnite-web/fork) | ||
2. Clone your forked repo to your local development machine. | ||
3. Open the repo in vscode. | ||
4. Run `yarn` | ||
5. Run `yarn nx run devenv:prepare`. This is only required for the first time working with the codebase. | ||
6. Run `yarn run start` and navigate to [https://localhost:3000](https://localhost:3000) | ||
- Note that MQTT and Mongo will be started via docker automatically. | ||
- Mongo will restore a default database if no database already exists (if there are no files in `.data/mongodb`). | ||
- Note MQTT currently starts with no username/password configured. | ||
7. \[Optional\]: override environment variables when running locally via `cp apps/playnite-web/local.env apps/playnite-web/overrides.env` | ||
- **REMEMBER: do not commit `overrides.env` or sensitive information in `local.env`.** | ||
8. Continue to see [commands](./index.md#running-playnite-web) for running tests. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.