-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Implement paperclip or other way to upload to Google Cloud Storage #9760
Comments
What exactly are we storing on Google Cloud? Images and attachments? I don't understand the part about mounting the volume... |
I think Here, i guess it was just too much of a beta, or something -- so agreed, let's look at how Paperclip and Google Cloud's storage options can interact! |
It seems as though Paperclip has been depreciated. The official Paperclip GitHub repo advises us to use ActiveStorage. The RoR docs give instructions to use ActiveStorage along with Google Cloud storage, along with lots of other services, like AWS and Azure. They can be found here: https://guides.rubyonrails.org/active_storage_overview.html#google-cloud-storage-service We'll have to see how much time and effort it takes to use ActiveStorage to use Google Cloud |
Thanks @anirudhprabhakaran3 -- we had tried switching to ActiveStorage a while back but it didn't yet support very many backends. Looking at it again now, but... my preference would be to try using Paperclip for a relatively quick fix on this, then scheduling a bigger switch to ActiveStorage later. But let's see what's possible. Thanks! |
Google storage is supported through Fog Storage: https://github.com/thoughtbot/paperclip#storage |
And we're on Paperclip |
We'll probably change the storage here: https://github.com/publiclab/plots2/blob/main/config/initializers/paperclip.rb#L1-L10 |
OK - @icarito i started the changeover here: #9807 My questions/thoughts:
Thank you!! |
In order to migrate to Google Cloud Storage, we've had to mount our storage bucket with
gcsfuse
. This solution seems not stable enough as it sometimes locks the mountpoint (#9758 is an instance of this). This happened recently and we didn't notice until today, and it may have caused more problems in the past week.Please describe the desired behavior.
Ideally, we would not have to mount this volume, but the app would upload the data directly to the Google Cloud Storage API.
The text was updated successfully, but these errors were encountered: