neko/.m1k1o
2021-11-21 14:55:58 +01:00
..
base add japanese characters support. 2021-11-04 20:12:14 +01:00
brave change stopsignal. 2021-11-17 18:05:38 +01:00
chromium change stopsignal. 2021-11-17 18:05:38 +01:00
firefox change stopsignal. 2021-11-17 18:05:38 +01:00
google-chrome change stopsignal. 2021-11-17 18:05:38 +01:00
tor-browser change stopsignal. 2021-11-17 18:05:38 +01:00
ungoogled-chromium Update uBlock Origin to v1.38.6 (#101) 2021-11-21 14:55:58 +01:00
vlc change stopsignal. 2021-11-17 18:05:38 +01:00
vncviewer change stopsignal. 2021-11-17 18:05:38 +01:00
xfce change stopsignal. 2021-11-17 18:05:38 +01:00
.env.default easy development tools. 2021-04-01 23:18:50 +02:00
build Build by github actions (#70) 2021-06-13 14:13:19 +02:00
README.md add Google Chrome. 2021-06-07 20:00:55 +02:00
rebuild-server dev: -i flag is deprecated. 2021-04-03 15:17:50 +02:00
serve-client easy development tools. 2021-04-01 23:18:50 +02:00
start-server easy development tools. 2021-04-01 23:18:50 +02:00

How to contribute to neko

If you want to contribute, but do not want to install anything on your host system, we got you covered. You only need docker. Technically, it could be done using vs code development in container, but this is more fun:).

You need to copy .env.development to .env and customize values.

Step 1: Building server

  • ./build - You can use this command to build your specified SERVER_TAG along with base image.

If you want, you can build other tags. base tag needs to be build first:

  • ./build base
  • ./build firefox
  • ./build chromium
  • ./build google-chrome
  • etc...

Step 2: Starting server

  • ./start-server - Starting server image you specified in .env.
  • ./start-server -r - Shortcut for rebuilding server binary and then starting.

If you are changing something in the server code, you do not want to rebuild container each time. You can just rebuild your binary:

  • ./rebuild-server - Rebuild only server binary.
  • ./rebuild-server -f - Force to rebuild whole Golang environment (you should do this only of you change some dependencies).

Step 3: Serving client

  • ./serve-client - Serving vue.js client.
  • ./serve-client -i - Install all dependencies.

Debug

You can navigate to CLIENT_PORT and see live client there. It will be connected to your local server on SERVER_PORT.

If you are leaving client as is and not changing it, you don't need to start ./serve-client and you can access server's GUI directly on SERVER_PORT.

Feel free to open new PR.