You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had a look at this, and it seems we're using django storages in the normal way, so there's nothing stopping GCS from being used.
The only thing missing is that the provided settings file doesn't pull any GCS config, but that is easily solved by providing your own settings file, or if you want to create a PR that adds those to the provided settings file.
On Wed, 13 Mar 2024 at 14:54, Rudi ***@***.***> wrote:
I had a look at this, and it seems we're using django storages in the
normal way, so there's nothing stopping GCS from being used.
The only thing missing is that the provided settings file doesn't pull any
GCS config, but that is easily solved by providing your own settings file,
or if you want to create a PR that adds those to the provided settings file.
Is there anything else stopping support for GCS?
—
Reply to this email directly, view it on GitHub
<#287 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB4LMYSCXC2KHSTRLX3ZEWLYYBEAHAVCNFSM6AAAAABETTZC5KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOJUGM2DANBSGE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
No description provided.
The text was updated successfully, but these errors were encountered: