|
6 | 6 | [](https://github.com/qmk/qmk_configurator/pulse/monthly)
|
7 | 7 | [](https://github.com/qmk/qmk_configurator/)
|
8 | 8 |
|
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>. |
10 | 12 |
|
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. |
12 | 16 |
|
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: |
14 | 19 |
|
15 |
| - * [Issues](https://github.com/qmk/qmk_configurator/issues) |
| 20 | +- [Issues](https://github.com/qmk/qmk_configurator/issues) |
16 | 21 |
|
17 | 22 | ## Development
|
18 | 23 |
|
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. |
20 | 27 |
|
21 | 28 | ### Select node version
|
| 29 | + |
22 | 30 | ```shell
|
23 | 31 | nvm use
|
24 | 32 | ```
|
25 | 33 |
|
26 | 34 | ### Project setup
|
27 |
| -``` |
| 35 | + |
| 36 | +```shell |
28 | 37 | yarn install
|
29 | 38 | ```
|
30 | 39 |
|
31 | 40 | ### Compiles and hot-reloads for development
|
32 |
| -``` |
| 41 | + |
| 42 | +```shell |
33 | 43 | yarn run dev
|
34 | 44 | ```
|
35 | 45 |
|
36 | 46 | ### Compiles and minifies for production
|
37 |
| -``` |
| 47 | + |
| 48 | +```shell |
38 | 49 | yarn run build
|
39 | 50 | ```
|
40 | 51 |
|
41 | 52 | ### Run your tests
|
42 |
| -``` |
| 53 | + |
| 54 | +```shell |
43 | 55 | yarn run test
|
44 | 56 | ```
|
45 | 57 |
|
46 | 58 | ### Lints and fixes files
|
47 |
| -``` |
| 59 | + |
| 60 | +```shell |
48 | 61 | yarn run lint
|
49 | 62 | ```
|
50 | 63 |
|
51 | 64 | ### Run your end-to-end tests
|
52 |
| -Start the server separatly |
53 |
| -``` |
| 65 | + |
| 66 | +Start the server separately |
| 67 | + |
| 68 | +```shell |
54 | 69 | yarn run test:cypress
|
55 | 70 | ```
|
56 | 71 |
|
57 | 72 | ### Run your end-to-end tests like CI
|
58 |
| -Start the server separatly |
59 |
| -``` |
| 73 | + |
| 74 | +Start the server separately |
| 75 | + |
| 76 | +```shell |
60 | 77 | yarn run test:cypress:ci
|
61 | 78 | ```
|
62 | 79 |
|
63 | 80 | ### Run your unit tests
|
64 |
| -``` |
| 81 | + |
| 82 | +```shell |
65 | 83 | yarn run test:unit
|
66 | 84 | ```
|
67 | 85 |
|
68 | 86 | ### Customize configuration
|
| 87 | + |
69 | 88 | See [Configuration Reference](https://vitejs.dev/config/).
|
70 | 89 |
|
71 | 90 | ## Docker
|
72 | 91 |
|
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. |
74 | 94 |
|
| 95 | +```shell |
75 | 96 | docker run -p 8080:80 qmkfm/qmk_configurator:latest
|
| 97 | +``` |
76 | 98 |
|
77 | 99 | You can specify a different backend URL by setting `VUE_APP_API_URL`:
|
78 | 100 |
|
| 101 | +```shell |
79 | 102 | docker run -e VITE_API_URL=http://localhost:8080 -p 8080:80 qmkfm/qmk_configurator:latest
|
| 103 | +``` |
80 | 104 |
|
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: |
82 | 107 |
|
| 108 | +```shell |
83 | 109 | docker run --mount type=volume,source=.,target=/qmk_configurator -p 8080:80 qmkfm/qmk_configurator:latest
|
| 110 | +``` |
84 | 111 |
|
85 | 112 | ### Building The Docker Image
|
86 | 113 |
|
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. |
88 | 116 |
|
89 | 117 | If for some reason you do need to build it yourself, you can use this command:
|
90 | 118 |
|
| 119 | +```shell |
91 | 120 | docker build -t qmk_configurator .
|
| 121 | +``` |
92 | 122 |
|
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: |
94 | 125 |
|
| 126 | +```shell |
95 | 127 | docker run -p 8080:80 qmk_configurator
|
96 |
| - |
| 128 | +``` |
| 129 | + |
97 | 130 | ## Internationalization Guide
|
98 | 131 |
|
99 | 132 | Please refer to [this document](internationalization_guide.md)
|
0 commit comments