Active Admin VS PocketBase.io

Rails is absolutely fantastic for projects below 10,000 lines with 1 or 2 contributors, especially if you want a classic forms-based UI. And you can get a huge amount done under those constraints in Rails. But as of couple of years ago, Rails came with a number of drawbacks: 1. There was no really viable system of static typing that a significant number of people were enthusiastic about. See... - Source: Hacker News / 9 days ago

Can you clarify what's the "tremendous value" you're getting out of the Django admin? At Heii On-Call https://heiioncall.com/ we are using Active Admin https://activeadmin.info/ for Ruby on Rails, which seems quite similar to the Django admin. In my experience, it's mostly useful as a fairly basic read-only view of what's in the database. In Rails, it's so easy to whip together a custom view that we tend to do... - Source: Hacker News / 7 months ago

For those who know [https://activeadmin.info/](https://activeadmin.info/) it uses a file format [https://github.com/activeadmin/arbre](https://github.com/activeadmin/arbre). Source: over 1 year ago

Very neat! My first thought was that this was a competitor to https://bullettrain.co/. Looking into it a bit more, it seems more aimed at building admin panels than whole apps. I guess it competes against tools like https://activeadmin.info/? - Source: Hacker News / almost 2 years ago

We briefly considered migrating to a full-grown Rails admin interface, such as ActiveAdmin, RailsAdmin, Administrate or Avo. We especially liked Avo which is built on a very modern stack similar to ours (Tailwind + Hotwire + ViewComponents). In the end, we didn’t go this route as we found some of the options a bit too restrictive (even though Avo is very flexible) and we did not feel like trying to amend it to our... - Source: dev.to / almost 2 years ago

Solutions like pocketbase and coolify come close to solving these problems. However, I wouldn't choose either as I fear architecture lock-in as much as vendor lock-in. Especially in the case of pocketbase, I may be forced to rewrite my application if it were to scale overnight. - Source: dev.to / 5 days ago

Now, I've released the Gowebly CLI v2.5.0 which includes PocketBase framework/backend support. - Source: dev.to / 6 days ago

Pocketbase [0] is a possibility. It offers a way to subscribe to collections, meaning the client will be notified if any of the records in that collection change. [1] Should be quite efficient too, the FAQ claims that 10k realtime connections on a small hetzner VPS is no problem [2] [0] https://pocketbase.io/. - Source: Hacker News / 29 days ago

I'd like to plug PocketBase [0] for a similar use case. Last week I was looking for a place to store random data with API access, and was looking at making a Google Sheets backend, but PocketBase was easy and didn't have a 60 rpm quota. Deploying to a cheap VPS was very easy with CapRover. [0] https://pocketbase.io/. - Source: Hacker News / about 1 month ago

I wonder if it is inspired by [1], looks very similar including the "realtime" blurb. -- 1: https://pocketbase.io/. - Source: Hacker News / about 2 months ago