StriverGuy

I've found myself repeating code, and often relying on the same vendor every time (AWS S3) for file management. I have yet to find a good approach to file search or permissioning without a lot of boilerplate.

I am curious what patterns other dev teams are using to manage files within their saas product to allow for multi-tenancy, permissioning, sharing, searchability etc.

Looking for good alternatives to local API development tools like Postman and Insomnia.

Postman has gotten bloated and slow, while Insomnia just rolled our the requirement of maintaining an account with the platform to use the tool.

Ideally something light weight, no account needed, and can export/import OAPI specs.

Our team has been struggling with a good release process for our browser extensions. With Chrome Extensions, every build needs to be reviewed by the chrome team. This can sometimes take 5-6 days and has never taken less than 24 hours. If a version is published, there is no way to revert to an old version in the event of bugs/issues that make it through the testing cycle.

True CI/CD is out of the question since we have no way to automatically release. Additionally, because of the extension architecture, automated testing is limited almost exclusively to unit level testing the client code.

How has your team overcome this? Any advice welcome here.

Our team has been struggling with a good release process for our browser extensions.

With Chrome Extensions, every build needs to be reviewed by the chrome team. This can sometimes take 5-6 days and has never taken less than 24 hours. If a version is published, there is no way to revert to an old version in the event of bugs/issues that make it through the testing cycle.

True CI/CD is out of the question since we have no way to automatically release. Additionally, because of the extension architecture, automated testing is limited almost exclusively to unit level testing the client code.

How has your team overcome this? Any advice welcome here.