Skip to content

Commit f0eb9fe

Browse files
authored
Cleanup readme (#1386)
* chore: clean up lint warnings in README - format for 80 cols - add block formatting markers * chore: add recommended packageManager attribute * chore: typos
1 parent 214d726 commit f0eb9fe

File tree

2 files changed

+55
-21
lines changed

2 files changed

+55
-21
lines changed

README.md

+53-20
Original file line numberDiff line numberDiff line change
@@ -6,94 +6,127 @@
66
[![GitHub contributors](https://img.shields.io/github/contributors/qmk/qmk_configurator.svg)](https://github.com/qmk/qmk_configurator/pulse/monthly)
77
[![GitHub forks](https://img.shields.io/github/forks/qmk/qmk_configurator.svg?style=social&label=Fork)](https://github.com/qmk/qmk_configurator/)
88

9-
The QMK Configurator is an online tool used for easily creating firmware files for keyboards supported in [qmk_firmware](https://github.com/qmk/qmk_firmware). The tool is located on https://config.qmk.fm.
9+
The QMK Configurator is an online tool used for easily creating firmware files
10+
for keyboards supported in [qmk_firmware](https://github.com/qmk/qmk_firmware).
11+
The tool is located on <https://config.qmk.fm>.
1012

11-
The QMK Configurator allows simple keymap creation and saving via .json keymap files, and generates appropriate firmware files for flashing onto selected keyboards.
13+
The QMK Configurator allows simple keymap creation and saving via .json keymap
14+
files, and generates appropriate firmware files for flashing onto selected
15+
keyboards.
1216

13-
This project is very much a work in progress. To begin contributing, please refer to the following:
17+
This project is very much a work in progress. To begin contributing, please
18+
refer to the following:
1419

15-
* [Issues](https://github.com/qmk/qmk_configurator/issues)
20+
- [Issues](https://github.com/qmk/qmk_configurator/issues)
1621

1722
## Development
1823

19-
We recommend you install and use [NVM](https://github.com/creationix/nvm) to manage node versions. There is a .nvmrc file in the root of the project directory that has been tested with our dependencies.
24+
We recommend you install and use [NVM](https://github.com/creationix/nvm) to
25+
manage node versions. There is a .nvmrc file in the root of the project
26+
directory that has been tested with our dependencies.
2027

2128
### Select node version
29+
2230
```shell
2331
nvm use
2432
```
2533

2634
### Project setup
27-
```
35+
36+
```shell
2837
yarn install
2938
```
3039

3140
### Compiles and hot-reloads for development
32-
```
41+
42+
```shell
3343
yarn run dev
3444
```
3545

3646
### Compiles and minifies for production
37-
```
47+
48+
```shell
3849
yarn run build
3950
```
4051

4152
### Run your tests
42-
```
53+
54+
```shell
4355
yarn run test
4456
```
4557

4658
### Lints and fixes files
47-
```
59+
60+
```shell
4861
yarn run lint
4962
```
5063

5164
### Run your end-to-end tests
52-
Start the server separatly
53-
```
65+
66+
Start the server separately
67+
68+
```shell
5469
yarn run test:cypress
5570
```
5671

5772
### Run your end-to-end tests like CI
58-
Start the server separatly
59-
```
73+
74+
Start the server separately
75+
76+
```shell
6077
yarn run test:cypress:ci
6178
```
6279

6380
### Run your unit tests
64-
```
81+
82+
```shell
6583
yarn run test:unit
6684
```
6785

6886
### Customize configuration
87+
6988
See [Configuration Reference](https://vitejs.dev/config/).
7089

7190
## Docker
7291

73-
If you don't have a webserver already and don't already have one in mind you can use docker. By default it spins up a self-contained environment.
92+
If you don't have a webserver already and don't already have one in mind you
93+
can use docker. By default it spins up a self-contained environment.
7494

95+
```shell
7596
docker run -p 8080:80 qmkfm/qmk_configurator:latest
97+
```
7698

7799
You can specify a different backend URL by setting `VUE_APP_API_URL`:
78100

101+
```shell
79102
docker run -e VITE_API_URL=http://localhost:8080 -p 8080:80 qmkfm/qmk_configurator:latest
103+
```
80104

81-
If you'd like to develop locally you can use a volume to tie your local filesystem to the container:
105+
If you'd like to develop locally you can use a volume to tie your local
106+
filesystem to the container:
82107

108+
```shell
83109
docker run --mount type=volume,source=.,target=/qmk_configurator -p 8080:80 qmkfm/qmk_configurator:latest
110+
```
84111

85112
### Building The Docker Image
86113

87-
Most of the time you don't need to do this, you can use volume mounts as described above to use the pre-built image with your local tree.
114+
Most of the time you don't need to do this, you can use volume mounts as
115+
described above to use the pre-built image with your local tree.
88116

89117
If for some reason you do need to build it yourself, you can use this command:
90118

119+
```shell
91120
docker build -t qmk_configurator .
121+
```
92122

93-
This process will take a while. You may want to go make some tea or something. When it finishes you can run it with this command:
123+
This process will take a while. You may want to go make some tea or something.
124+
When it finishes you can run it with this command:
94125

126+
```shell
95127
docker run -p 8080:80 qmk_configurator
96-
128+
```
129+
97130
## Internationalization Guide
98131

99132
Please refer to [this document](internationalization_guide.md)

package.json

+2-1
Original file line numberDiff line numberDiff line change
@@ -81,5 +81,6 @@
8181
"minimist": "^1.2.3",
8282
"yargs-parser": "^18.1.2",
8383
"trim-newlines": "^4.0.1"
84-
}
84+
},
85+
"packageManager": "[email protected]+sha512.a6b2f7906b721bba3d67d4aff083df04dad64c399707841b7acf00f6b133b7ac24255f2652fa22ae3534329dc6180534e98d17432037ff6fd140556e2bb3137e"
8586
}

0 commit comments

Comments
 (0)