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

Provide instructions for headless systems/servers #69

Open
yurikoles opened this issue Jun 30, 2019 · 2 comments
Open

Provide instructions for headless systems/servers #69

yurikoles opened this issue Jun 30, 2019 · 2 comments

Comments

@yurikoles
Copy link
Contributor

In my case I had opened login link on my desktop, but OAuth redirect is failed, because client was running on different machine. Simple wget -q <redirect-url> in other terminal window on server machine finished login successfully.

Please also examine insync-headleass, which allows login with auth code, which is generated by Google OAuth flow, from any machine.

@harababurel
Copy link
Owner

I think the issue you're describing is already covered by an option that can be set in gcsf.toml:

# If set to true, Google Drive will provide a code after logging in and
# authorizing GCSF. This code must be copied and pasted into GCSF in order to
# complete the process. Useful for running GCSF on a remote server.
#
# If set to false, Google Drive will attempt to communicate with GCSF directly.
# This is usually faster and more convenient.
authorize_using_code = false

This doesn't involve any redirects and works well for headless setups.

I might have misread your comment, please let me know if this is the case.

@yurikoles
Copy link
Contributor Author

Yes, this is it, sorry for noise. But I still think it should be better documented.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants