Last active
August 8, 2023 15:35
Star
You must be signed in to star a gist
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
=================================================================== | |
Google doesn't allow using Chrome's API keys in Chromium builds and | |
strongly recommends against doing so. These OAuth 2 credentials are | |
taken from publicly available sources, but their fitness for use in | |
Chromium builds is not warrantied. | |
=================================================================== | |
!!! Use these keys to reactivate Sync in Chromium at your own risk; | |
they are extremely likely to stop working in the (near) future. | |
$ grep oauth2 ~/.config/chromium-flags.conf | |
--oauth2-client-id=77185425430.apps.googleusercontent.com | |
--oauth2-client-secret=OTJgUOQcT7lO7GsGZq2G4IlT | |
Note: The above works on Arch Linux because of its custom launcher, | |
plus a patch to reuse --oauth2-client-{id,secret} for setting | |
GOOGLE_DEFAULT_CLIENT_{ID,SECRET} similar to environment vars. | |
https://wiki.archlinux.org/index.php/Chromium#Making_flags_persistent |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello All,
I'm doing the setup on a mac, and global imports don't work on mac as they should on a normal unix system, so I thought I could prevent some headaches:
/etc/default
or~/.profile
variable imports are not passed to applications ran with spotlight or aqua/finder, so you should pass the variables to launchd to be able to inherit variables within applications ran with aqua/finder/spotlight.You have multiple ways of setting global variables using launchd:
Setting environment variables using a launchd unit : see the link
You can add global variables to launchd within your shell's
.profile
or/etc/default
with adding the following lines: