Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] Persistent browser data & ability to login to browser (google chrome) #76

Open
DJKenzoDE opened this issue Jun 24, 2021 · 8 comments
Labels
documentation Improvements or additions to documentation enhancement New feature or request

Comments

@DJKenzoDE
Copy link

good day everyone

how it is possible to login in google account on the google chrome browser?

best wishes from berlin

@m1k1o
Copy link
Owner

m1k1o commented Jun 24, 2021

Hi, yes it is possible. Although, in order to keep it persistent between container recreates, browser data must be mounted as a volume.

EDIT: However, also preferences might need to be updated.

"BrowserSignin": 0,

@DJKenzoDE
Copy link
Author

how to make is persistent? and is this solution good for the neko-rooms that mounted in the new room window?

@m1k1o
Copy link
Owner

m1k1o commented Jun 24, 2021

You can mount volume to this folder inside container /home/neko/.config/google-chrome. Although, as i mentioned, preferences would, there would need to be adjusted. I am not sure right now, what everything needs to be changed (allowing cookies, allowing gistory etc.) but you can, again, mount custom policy file to /etc/opt/chrome/policies/managed/policies.json.

Yes, also neko-rooms supports volumes. Private mount would be best fit for your browser data and template mount would be good for preferences file. I have this on my roadmap in neko-rooms to allow having persistent rooms. First step - mounts - is already done. Just some frontendwork is missing, to make the UX better.

@DJKenzoDE
Copy link
Author

how to make it possible on neko-rooms? only link the volume to your path?(etc/opt/...) and then is all done?

@m1k1o m1k1o changed the title Login to Google Account Persistent browser data & ability to login to browser (google chrome) Jun 24, 2021
@m1k1o m1k1o added documentation Improvements or additions to documentation enhancement New feature or request labels Jun 24, 2021
@m1k1o
Copy link
Owner

m1k1o commented Jun 24, 2021

Yes, you only need to mount volume that you want to keep persistent. Explained in your other issue here: m1k1o/neko-rooms#22

@m1k1o m1k1o changed the title Persistent browser data & ability to login to browser (google chrome) [Feature Request] Persistent browser data & ability to login to browser (google chrome) Jul 23, 2021
@m1k1o m1k1o mentioned this issue Nov 27, 2021
27 tasks
@bladecell
Copy link

I am trying to make logins persistent after container restart and I have /home/neko/.config/vivaldi/ and policies.json mounted on host and in policies.json I have these lines
"DefaultCookiesSetting": 1, "BrowserSignin": 1, "RestoreOnStartup": 1
but on every restart I lose logins.

@m1k1o
Copy link
Owner

m1k1o commented Mar 23, 2023

Can you check if path is mounted correctly for policies at /etc/opt/vivaldi/policies/managed/policies.json, that it contains valid JSON (so no mistake has been made, like leaving , at the end of array). Also can you check in settings if thats allowed, because default preferences as well deny it.

@bladecell
Copy link

When I open file:///etc/opt/vivaldi/policies/managed/policies.json in neko browser, the .json is there and no trailing comma. In the settings, cookies are set on session only and there are some saved cookies from sites, that logged off.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants