Archived
2
0
This repository has been archived on 2024-06-24. You can view files and clone it, but cannot push or open issues or pull requests.
neko-custom/.docker
Miroslav Šedivý ba3368a3eb
Replace nordvpn with sponsorblock. (#144)
* replace nordvpn with sponsorblock.

* update changelog.
2022-03-01 19:32:17 +01:00
..
base rename to .docker, fixes #95. 2021-11-27 14:23:33 +01:00
brave Replace nordvpn with sponsorblock. (#144) 2022-03-01 19:32:17 +01:00
chromium Replace nordvpn with sponsorblock. (#144) 2022-03-01 19:32:17 +01:00
firefox Replace nordvpn with sponsorblock. (#144) 2022-03-01 19:32:17 +01:00
google-chrome Replace nordvpn with sponsorblock. (#144) 2022-03-01 19:32:17 +01:00
microsoft-edge Replace nordvpn with sponsorblock. (#144) 2022-03-01 19:32:17 +01:00
tor-browser rename to .docker, fixes #95. 2021-11-27 14:23:33 +01:00
ungoogled-chromium Replace nordvpn with sponsorblock. (#144) 2022-03-01 19:32:17 +01:00
vlc rename to .docker, fixes #95. 2021-11-27 14:23:33 +01:00
vncviewer rename to .docker, fixes #95. 2021-11-27 14:23:33 +01:00
xfce rename to .docker, fixes #95. 2021-11-27 14:23:33 +01:00
.env.default rename to .docker, fixes #95. 2021-11-27 14:23:33 +01:00
build rename to .docker, fixes #95. 2021-11-27 14:23:33 +01:00
README.md doxc fix mistake. 2022-01-19 18:47:01 +01:00
rebuild-server rename to .docker, fixes #95. 2021-11-27 14:23:33 +01:00
serve-client rename to .docker, fixes #95. 2021-11-27 14:23:33 +01:00
start-server rename to .docker, fixes #95. 2021-11-27 14:23:33 +01: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.default 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.