Use Google Cloud Storage Instead of S3

Contribuer Fonctionnalité
1

I saw another post about this from '14 - but no answer and it seemed like they were making this harder than it should be…

I would like some pointers to see if there is an AWS endpoint configuration within app.yml which could be changed to allow use of google cloud storage instead of s3 - GCS has a compatability mode where all - as I understand it - would need to happen is to change the AWS endpoint:

In your existing tools or libraries, make the following changes:
Change the request endpoint to use the Google Cloud Storage request endpoint.
Replace the Amazon Web Services (AWS) access and secret key with the corresponding Google Cloud Storage access key and secret key (collectively called your Google developer key).

This could be added as an option under /admin/site_settings/category/files and option for AWS endpoint along with the access keys? or can it be done in the app.yml? [AWS_ENDPOINT = “/xxxx/xxx”] already?

Thanks!

2 « J'aime »
2

I ended up doing this, just to get it working:

/bin/bash
 This script will copy the latest discourse backup to google cloud
 Then it will remove the previous backup from google cloud

LATESTBACKUP=`ls /var/discourse/shared/standalone/backups/default/*.gz -t1 | head -n1`
PREVBACKUPWDIR=`ls /var/discourse/shared/standalone/backups/default/*.gz -1tr | head -1`
PREVBACKUP=`find $PREVBACKUPWDIR -exec basename {} \;`

/home/user/gsutil/gsutil cp $LATESTBACKUP gs://yyh-community-backups
/home/user/gsutil/gsutil rm gs://your-backup-bucket/$PREVBACKUP

Which works, but I still think greater use of google cloud storage could be used with the s3 compatibility mode as described above. But maybe I’m the only one who wants to use non amazon tools.

3 « J'aime »
3

It’d be great to have a few options “out of the box”!

4

Bonjour

Je teste la sauvegarde GCS avec la configuration par défaut.

DISCOURSE_S3_BACKUP_BUCKET: falcoland-files/backup
DISCOURSE_BACKUP_LOCATION: s3

et j’ajoute une politique spéciale sur GCS

policy = {
    "serviceAccount:${google_service_account.discourse.email}" = [
      "roles/storage.legacyBucketOwner"
    ]
  }

Cela a réussi à envoyer la sauvegarde vers GCS.

J’espère que cela aidera quelqu’un comme moi qui a passé une semaine à l’appliquer.

Stockage GCS

6 « J'aime »
Set up image uploads to Google Cloud Storage
Configure an S3 compatible object storage provider for uploads
5

C’est probablement à la limite de la paranoïa, mais je stocke les sauvegardes de Discourse sur AWS S3 (ce qui est pris en charge nativement), puis je synchronise les sauvegardes de S3 vers GCS en utilisant :

Aucune programmation n’est requise. Cela augmentera légèrement vos coûts de stockage, donc cela ne vous aide pas si vous cherchez à économiser de l’argent. Je conserve les 10 dernières sauvegardes, chacune faisant 10 Go, et cela me coûte 3 $ par mois chez Google.