3 ms·
We’re considering it for a use case at work. In our case, it’s to allow a team of analysts to be more or less self sufficient in publishing some data for extern
by arnsholt 4y ago
We’re considering it for a use case at work. In our case, it’s to allow a team of analysts to be more or less self sufficient in publishing some data for external consumption without needing to deal with deployments and the like. This way, changing requirements can be handled by the analysts themselves by updating the tables or views published by PostgRest, without needing to think about changing a REST service and such.
- maerF0x0 4y agoSounds like a security nightmare, highly recommend pairing them with a dedicated security minded person to ensure correct configurations of access control (networklayer/hosts, row level, resource denial of service etc) at the very least have a read of https://postgrest.org/en/stable/admin.html https://postgrest.org/en/stable/admin.html