PikaPods looks like an interesting idea. I invested some time setting up account, and trying to create Baserow pod. I was greeted with "Failure while adding container. Our team has been informed."
Yeah, still in public beta and multi-container apps like Baserow are pretty new and marked as "experimental". Already looking into the error.
Edit: Should work, but takes several minutes before the web UI becomes available. We do provide the logs for such cases. Most other apps are easier to deal with. :-)
Baserow dev who worked on our new multi-container single image (baserow/baserow on dockerhub) here. I assume you are using the baserow/baserow image for pikapods (but perhaps not?).
- `SYNC_TEMPLATES_ON_STARTUP=false` to turn off the initial load of example Baserow templates. Our template collection is growing and the loading of this into the database is probably what is causing the several minute startup. This will be optimized in the future.
- `BASEROW_RUN_MINIMAL=true`. This will combine two of the backend async queue processes into a single one. This might result into higher priority async tasks getting stuck behind slower tasks (an large import/export might slow down the broadcast of realtime events for example). But this tradeoff is perfectly reasonable in most small self hosted environments.
- `BASEROW_AMOUNT_OF_GUNICORN_WORKERS=1` to reduce the number of concurrent backend api processes from the default of 3. Once again this might cause a degradation in performance for higher volumes of traffic, but a tradeoff worth considering if memory etc is a concern.
This image is brand new and because of it's multi-process nature is hiding some interesting complexity. We are still working out the kinks and a sensible set of defaults. It's also very easy for us to offer different variants of this image with different defaults set. Any feedback, suggestions or questions are very welcome here or at http://community.baserow.io.
Wow! Thanks for the tips! Will look into adding those during the next review.
Using docker.io/baserow/baserow:1.9.1 currently.
For now the image is marked as "experimental". And I'm looking into channeling future issue reports from apps in a more structured way and maybe keep app settings on Github for editing and reporting issues against. Without duplicating upstream efforts of course. Still lots of work to do here.
Thanks for looking into it. It's a missed opportunity; this application failure quite possibly cost you a customer loss. I am not sure when I'll be able to test it again.
I think you should cross-promote PikaPods more, and prominently, based on the popularity of your BorgBase. I noticed the following in my backup report, and that raised PikaPods' profile in my opinion; so I might cut PikaPods some slack, and try it again.
> The team behind BorgBase is launching a new container hosting service for open source apps...
It’s a trade-off between adding new apps quickly and testing them very well. Currently I tend to add more apps and just monitor for failures in Sentry. Mostly to see which categories are used and to provide enough choice.
Thanks for sticking around for now. I still have many improvements planned, like making it easy to report deployment bugs and suggest changes to settings. Like new env vars, ports, images, etc.
