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
{{ message }}
This repository has been archived by the owner on Aug 1, 2023. It is now read-only.
Related to our discussion and forum post
I'd propose the following:
adding a function that will upload the resultant data to a cloud storage bucket (i.e. s3), through some config settings - either hardcoded file, or preferably with env variables like this:
BUCKET_NAME
CLOUD_PROVIDER
CLOUD_USER
CLOUD_KEY
and then, in blockstack-core, a new endpoint is exposed to use this public readable bucket to retrieve the data.
initially, the vars would need to be hardcoded (which could result in drift), but i have ideas on how to resolve that in the future.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Related to our discussion and forum post
I'd propose the following:
adding a function that will upload the resultant data to a cloud storage bucket (i.e. s3), through some config settings - either hardcoded file, or preferably with env variables like this:
BUCKET_NAME
CLOUD_PROVIDER
CLOUD_USER
CLOUD_KEY
and then, in blockstack-core, a new endpoint is exposed to use this public readable bucket to retrieve the data.
initially, the vars would need to be hardcoded (which could result in drift), but i have ideas on how to resolve that in the future.
The text was updated successfully, but these errors were encountered: