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

port-to-go: Finish getCredentials() implementation, and document usage #11

Open
vorburger opened this issue Jan 5, 2023 · 5 comments
Open
Labels

Comments

@vorburger
Copy link
Contributor

In the context of #10, I had a brief try at the port-to-go, but realized that its getCredentials() method does not appear to be fully implemented? @jamesread or am I just really dumb and not understanding how to use it? Perhaps this issue could track the implementation, and then document how the credz have to be obtained.

@jamesread jamesread added the go label Jan 5, 2023
@jamesread
Copy link
Owner

Hey @vorburger , indeed this is still work in progress - I pushed the work I had done so far.

@glynternet
Copy link

glynternet commented Jan 13, 2023

Hi all,

I was following this repo from when looking for a gmail exporter myself a couple of years ago. I wasn't very good with python back then so implemented this go version: https://github.com/glynternet/gmail-exporter/tree/main

I didn't realise I hadn't open sourced it yet, so did so this morning. Added an MIT license.
Feel free to use, reuse, adapt, contribute to etc. 😄

It has a bit of a strange build system that I tried to start templatising for all of my projects but you should just be able to build and use it using go build cmd/gmail-exporter

@jamesread
Copy link
Owner

Hey @glynternet , wow, that's funny timing! :-) Thanks for sharing - will take a look at your codebase.

Are you interested in contributions? Maybe this project makes more sense to stay as python then, rather than re-inventing the wheel?

At the moment, with the last few days of updates I think this python version has become a lot more stable / usable for other people (it's been running fine for just me for quite some time) - so probably no need to throw the python version away now (which I was going to do). However, I do find go to be far more maintainable, if people start asking for more features.

@glynternet
Copy link

I'd be very open to contributions.

Admittedly the state of the repo is one I quickly whipped together so I'd probably look at improving it a bit more if people wanted to contribute.

Feel free to file issues over there if you ever want to discuss it 👍🏻

@jamesread
Copy link
Owner

Sounds great - probably won't be any time soon, it'll probably be if / when I get frustrated with this python implementation! But I won't try and re-invent the wheel if I decide a Go version is the way to go - will contribute back. Thanks for commenting here!

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

No branches or pull requests

3 participants