Add a Google Drive Connector

[MODSetter]

Adding a Google Drive Connector will be awesome.

It will require a file selection UI as I don't want to just add everything in Google Drive.

@Adamsmith6300 have already created Git Repo Selection UI, it would be good start if anyone want to take this.

I expect myself to do this but LMK if anyone want to try this

What to Do

You can follow the below PR examples to see how to add new connector https://github.com/MODSetter/SurfSense/pull/125 https://github.com/MODSetter/SurfSense/pull/37

[byuly]

@MODSetter Hey, could I get this assigned? I'll try working on it :)

[MODSetter]

@byuly Sure would love to get this done. LMK any way I can help.

[MODSetter]

@byuly Are you still working on it or I should reopen it to other contributors?

[byuly]

@MODSetter Yes slowed down on it but will work on it again now since the repo is back!

[MODSetter]

@MODSetter Yes slowed down on it but will work on it again now since the repo is back!

Thanks for confirming I will keep it assigned to you. LMK if you face any issues regarding the implementation.

[big14way]

Hi, my name is Godswill Idolor also know as Gwill. I am a blockchain engineer with 2 years of experience in backend and frontend. I am a contributor of projects like vitecare, harmony, mediano, Flare and Kindfi focusing on Smart Contracts using Rust, Python, Frontend and Backend. I also have experience with Cairo. StarkNet bootcamp graduate 12. I am passionate about smartcontract, which is why I enjoy designing the logic, and I have a natural ability to think critically and effectively. Along with my team, I won first place in OD hack13 as one of the top contributors. My experience in both frontend and backend enables me to carry out a wide variety of tasks to achieve set goals. I would really love to participate in the project with this issue.. please assign me

[MODSetter]

@big14way Thanks for your interest. Assigning it to you 👍

[suzy-g38]

Hi,

Saw this issue open. I would like to work on this issue.

Recommended by OnlyDust for outstanding experience and quality contributions.

[MODSetter]

@suzy-g38 Thanks for your interest assigning it to you now 👍

[byuly]

Sorry got caught up with other stuff. Other developers can pick this up, will pick up some other simpler issue when I'm more free!

[suzy-g38]

Hi @MODSetter, as I said in the other issue, due some personal issues, I don't think I can finish this task anytime sooner. Thank you for the opportunity. You can assign this task to anyone. Sorry for the delay.

Would love to comeback and contribute to this project meaningfully in the future.

Thanks again.

[MODSetter]

@suzy-g38 NP thanks for your efforts. Hopefully you comeback and contribute as we would love to have you 🙂🙌

[OVECJOE]

Hi @modsetter, is this still open and unassigned? I am willing to take it up if you don't mind.

[MODSetter]

Hi @MODSetter, is this still open and unassigned? I am willing to take it up if you don't mind.

Thanks for your interest 🙏 Assigned it to you 🙌

[OVECJOE]

@MODSetter I need to clarify something.

@OVECJOE ➜ /workspaces/SurfSense (main) $ docker-compose up --build
WARN[0000] /workspaces/SurfSense/docker-compose.yml: the attribute `version` is obsolete, it will be ignored, please remove it to avoid potential confusion 
WARN[0000] /workspaces/SurfSense/docker-compose.override.yml: the attribute `version` is obsolete, it will be ignored, please remove it to avoid potential confusion 
[+] Running 32/32
 ✔ pgadmin Pulled                                                                                                                                                                    35.1s 
 ✔ db Pulled                                                                                                                                                                         34.7s 
[+] Building 0.1s (1/1) FINISHED                                                                                                                                                           
 => [internal] load local bake definitions                                                                                                                                            0.0s
 => => reading from stdin 778B                                                                                                                                                        0.0s
unable to prepare context: path "/workspaces/SurfSense/ghcr.io/modsetter/surfsense_backend:latest" not found

I guess it is called docker-compose.override.yml because I need to change ghcr.io/modsetter/surfsense_backend to ghcr.io/<MY_USERNAME>/surfsense_backend, right?

[MODSetter]

@MODSetter I need to clarify something.

@OVECJOE ➜ /workspaces/SurfSense (main) $ docker-compose up --build WARN[0000] /workspaces/SurfSense/docker-compose.yml: the attribute version is obsolete, it will be ignored, please remove it to avoid potential confusion WARN[0000] /workspaces/SurfSense/docker-compose.override.yml: the attribute version is obsolete, it will be ignored, please remove it to avoid potential confusion [+] Running 32/32 ✔ pgadmin Pulled 35.1s ✔ db Pulled 34.7s [+] Building 0.1s (1/1) FINISHED
=> [internal] load local bake definitions 0.0s => => reading from stdin 778B 0.0s unable to prepare context: path "/workspaces/SurfSense/ghcr.io/modsetter/surfsense_backend:latest" not found I guess it is called docker-compose.override.yml because I need to change ghcr.io/modsetter/surfsense_backend to ghcr.io/<MY_USERNAME>/surfsense_backend, right?

@cubxxw Is this the case ?

[OVECJOE]

@cubxxw Hi... Any update?

[MODSetter]

@MODSetter I need to clarify something.

@OVECJOE ➜ /workspaces/SurfSense (main) $ docker-compose up --build WARN[0000] /workspaces/SurfSense/docker-compose.yml: the attribute version is obsolete, it will be ignored, please remove it to avoid potential confusion WARN[0000] /workspaces/SurfSense/docker-compose.override.yml: the attribute version is obsolete, it will be ignored, please remove it to avoid potential confusion [+] Running 32/32 ✔ pgadmin Pulled 35.1s ✔ db Pulled 34.7s [+] Building 0.1s (1/1) FINISHED
=> [internal] load local bake definitions 0.0s => => reading from stdin 778B 0.0s unable to prepare context: path "/workspaces/SurfSense/ghcr.io/modsetter/surfsense_backend:latest" not found I guess it is called docker-compose.override.yml because I need to change ghcr.io/modsetter/surfsense_backend to ghcr.io/<MY_USERNAME>/surfsense_backend, right?

@Utkarsh-Patel-13 @CREDO23 @anshul7665 Any help over this will be appreciated as I am also not sure.

[CREDO23]

I had that issue as well , @MODSetter , @OVECJOE ! Actually it is trying to look for those images from your local which is not ideal ...

For now , you can tell docker to consider the docker-compose.yml with docker compose -f docker-compose.yml up -d

Then you can run your backend and frontend without any issue

[CREDO23]

The next step could be to use image instead of context , so docker will pull the image from the github regidtry. Something like :

services:
  backend:
    image: ghcr.io/modsetter/surfsense_backend:latest

@MODSetter , what do you think ?

or we can use :

services:
  backend:
    context: './surfsence_bakend'

if we want to build the image locally

[OVECJOE]

The next step could be to use image instead of context , so docker will pull the image from the github regidtry. Something like :

services:
  backend:
    image: ghcr.io/modsetter/surfsense_backend:latest

@MODSetter , what do you think ?

or we can use :

services:
  backend:
    context: './surfsence_bakend'

if we want to build the image locally

I think I prefer the second, since it accommodates when there is a change in the folder locally and you want to build the image from it. Or what do you think 🤔?

[CREDO23]

It depends on what you want @OVECJOE ! But in dev mod, i prefer to do not build images on every change .

[MODSetter]

The next step could be to use image instead of context , so docker will pull the image from the github regidtry. Something like :

services: backend: image: ghcr.io/modsetter/surfsense_backend:latest @MODSetter , what do you think ?

or we can use :

services: backend: context: './surfsence_bakend' if we want to build the image locally

We do want to pull image from the github registry. Building locally will just waste time for everyone. We already have its workflow to build and publish here : https://github.com/MODSetter/SurfSense/tree/main/.github/workflows

[anshul7665]

Agree with @MODSetter , its easier for everyone to get started if we can just pull image from repo . You can just do docker build command and build locally or , keep a local copy of override file and build it from there instead changing it to your ghcr.io/<MY_USERNAME>/surfsense_backend

[OVECJOE]

Okay, understood 🙌