Supabase
Connect Supabase to your Softr apps to interact with your data.
Connecting Supabase to Softr
1. Select the project you want to connect to Softr from your Supabase dashboard
2. Select Project Settings at the bottom of the side menu
3. Click on Database in the left-hand menu to bring up the settings for your database
4. Find the Configuration Parameters section and copy the credentials to a safe location or write them down
Copy down the follow values and save them to a safe location:
- Host
- Database
- Port
- User
- Password
5. Login to Softr and select Data sources on the left-hand menu
6. Click on Connect Data Source in the upper-right corner
7. Click on Supabase, then click Continue
8. Copy the parts of your credentials into the appropriate blanks.
These can be put into the corresponding blanks in the Softr setup. The Name field can be anything you like and the Port defaults to 5432 for Supabase. The rest of the fields can be filled in with the corresponding info from Supabase. When finished, click Connect.
You should end up with something like this:
Re-authenticating, removing, and renaming your Supabase data source.
As with all data sources in Softr, you can always rename, remove, or edit your data source’s connection by clicking the ellipses (three dots) on the data source itself:
Restricting IP access
If you need to restrict IP addresses inside of Supabase, you can add Softr’s IP addresses to your list of allowed IPs:
3.120.79.212
3.123.159.186
52.58.246.121
Current limitations
- No auto-sync options: We currently do not support auto-syncing dropdown or quick select options.
- No field compatibility mapping: We don’t currently specify which fields can and can’t be mapped to which field types in Softr. For instance, if you map a string/text field from Supabase to a rating type field in Softr, you may get unintended results or no results at all. It’s generally best practice to try and map the Supabase field type with the Softr field type that most closely matches it.
- No auto-mapping: Fields will not be auto-mapped when connecting a block to BigQuery.
Last updated on August 30, 2024