search

m1k1o / neko-rooms

Selfhosted collaborative browser - room management for n.eko
Apache License 2.0
462 stars 63 forks source link

Change scroll sensitivity using neko api. #99

Closed Armrisch1 closed 1 year ago

Armrisch1 commented 1 year ago

Is there a way to change scroll sensitivity using neko open api, now we can change scroll sensitivity from neko settings manually but I need to do it from api. Because scroll is very fast by default.

Thanks for advance!

m1k1o commented 1 year ago

Hello, that is currently not possible because that information is never stored on backend. It is only available in client therefore it is not configurable from API.

Armrisch1 commented 1 year ago

May be it is possible to set some default sensitivity for all rooms? For example when n.eko is building or do it in some other way. Default scroll is too fast now and it is not comfortable to use.

m1k1o commented 1 year ago

You could change it in client store here and build custom image that can be used in new value.

But I agree with you that the default sensitivity is not optimal (and as well dependent on OS and browser) and could be reconsidered.

Armrisch1 commented 1 year ago

Thanks but I am using n.eko rooms, how can I do it with neko rooms, as I know each room is a new docker container bulit by n.eko, what I need to change in n.eko rooms?

m1k1o commented 1 year ago

You don't need to change anything, neko rooms picks your new image. It does not matter if that image is pulled from registry or locally built as long as it's named the same.

Unfortunately this all is not available from API or GUI. You just clone neko repository, change your stuff, go to .docker/ folder and run ./build base and then ./build chromium or whatever browser you would like.

That creates local image with your changes named the same as the remote image. Just be sure to not pull image because it would be overwritten.

Armrisch1 commented 1 year ago

Sorry for so many questions. But where I need to clone neko and build that neko-rooms starts using my local neko?

m1k1o commented 1 year ago

Anywhere on your system, e.g. your $HOME directory /home/user or /opt or /tmp.

git clone https://github.com/m1k1o/neko
cd neko
# ... do your changes
cd .docker
./build base
./build chromium

Now you have successfully build your custom m1k1o/neko:chromium image. Everytime there is update just do git pull origin master and rebuild again.

Don't worry that it is named the same as the official image but it contains your changes. Of course, only on that server where you built that.

Armrisch1 commented 1 year ago

Thanks a lot.