Typebot seems to require S3 compliant storage, something like object storage, in order for you to accept files / uploads from your typebots. For example, if your typebot asks, "Please upload a screenshot" you need a place to store the file.
How do we configure this? The documentation is here, but it is not obvious what to do.
Here is an attempt (which doesn't work) at getting the typebot to use object storage on Vultr.
# Add custom ENV configuration in this file # https://docs.typebot.io/self-hosting/configuration # I have replaced the variables with **** # Unsplash export NEXT_PUBLIC_UNSPLASH_APP_NAME = **** export NEXT_PUBLIC_UNSPLASH_ACCESS_KEY = **** #GIPHY export NEXT_PUBLIC_GIPHY_API_KEY = **** # Object storage on Vultr S3_ACCESS_KEY = **** S3_SECRET_KEY = **** S3_BUCKET = typebot S3_PORT = 443 S3_ENDPOINT = **** S3_SSL = true S3_REGION = ****
Do you have any error for context and make sure to use
exportstatement for each line, to actually make the variable available for the app.
Hey, @nebulon, thank you very much for looking at this.
This is beyond me. I tried a completely fresh installation of Typebot to resolve it. There are still some problems.
Even if I enter the line for giphy on its own, I am unable to successfully stop and restart Typebot. I have managed to get giphy to work with Typebot though.
The same thing if I try with the two lines needed for unsplash.
I am forgetting about the object storage, as I can't even get the typebot to work at all unless everything is removed with commenting.
This might well be due to me and not understanding something. Somebody with more skills will be needed to resolve this, if it happens to them.
Here's a working config sample for Digital Ocean Spaces. Add the following entries in the env.sh and restart the Typebot app:
export S3_ACCESS_KEY=<YOUR DO ACCESS KEY> export S3_SECRET_KEY=<YOUR DO SECRET KEY> export S3_BUCKET=<YOUR BUCKET NAME> export S3_ENDPOINT=nyc3.digitaloceanspaces.com export S3_REGION=US export S3_PORT=443