winter VS Metabase

Beside Symfony there is Laravel Framework , I will not go into deep difference between this frameworks as it really is just taste of what your team likes more (active record vs datamapper, facade/helpers vs dependency injection, blade vs twig, ...), as already mention above this kind of CMS make sense if Website is just one part of your application and you have to build more then just a simple digital business card / website. In Laravel world there are CMS like October CMS / Winter CMS, which target the same providing a CMS based on the Full Stack Larave framework and give you all features of that framework. Another already mention CMS in Laravel world is Statmatic.

Chances are a lightweight CMS already exists. Winter CMS is one such option.

Or Winter CMS (https://wintercms.com/) ;)

As someone who dabbled in PHP but is mostly a self-taught JS hobbyist dev, I have been using and loving Directus (https://directus.io) since around the time they switched to Node. Development velocity is exceptional with new features released every couple of weeks and bugfixes/enhancements even more frequent, the community and core team is fantastic, and I like the fact that if I ever decide to switch to another CMS for some reason, there's no real import/export process, I just delete the directus_tables in my database, and done.

Pocketbase (https://pocketbase.io/) piqued my interest after seeing it here and on ProductHunt, but I don't think it would be the right call for a client before it hits a stable release.

I also very much enjoyed OctoberCMS (although it has its quirks), but there was a fairly acrimonious split in the community there, and OctoberCMS is no longer open source, and I haven't used the fork (WinterCMS: https://wintercms.com/)

I enjoyed using Apostrophe (https://apostrophecms.com/) for a while, but ultimately I felt like I was doing a lot of stuff in a way that didn't come naturally to me, and although Mongo seems a logical choice when you look at Apostrophe's page model, it worried me a bit that the data would not be easy to move if I ever wanted to.

I'm biased, but it might be worth taking a look at Winter CMS. It's built on Laravel, so you get everything you would with Laravel but it also has some pretty powerful features on top of what you get out of the box with Laravel. Its plugin system and extensibility is also second to none. It's different from a few of the other options though in that you don't add it to an existing project, you build your projects from the start in it.

Winter CMS is an open source fork of OctoberCMS. They've just put Laravel 9 support in place as well.

If you're looking at October I'd give Winter a look too (https://wintercms.com), October is no longer open source and Winter is the open source fork of October. (Disclaimer: I'm the lead maintainer for Winter CMS)

Winter CMS? Laravel based and very developer friendly! https://wintercms.com/

If you're thinking of using Bolt but would also like to have access to the power of Laravel, I'd recommend taking a look at Winter CMS (open source fork of October CMS, built on Laravel / Symfony): https://wintercms.com

Have you ever looked at Winter CMS? https://wintercms.com it's a CMS built on Laravel that's super easy to customize and add your exact needs to.

Remote Code Execution via H2

We've used it for about a year - Blazer is okay if you need a quick SQL query console, but we found it lacking as an actual business intelligence tool. The support for graphs and dashboards is limited, for graphs it requires you to structure the query in an exact way as you can see in the Blazer readme.

After some research on available alternatives that don't break the bank, we decided to deploy a self-hosted instance of Metabase[0]. This took only a few minutes to set up using their Docker image[1] and it has much better graphing capabilities and you can easily put a custom layout together for dashboards. Upgrading is similarly easy (just redeploy). Also easy to configure: data sources, hiding or changing the data type of a column, G Suite sign-in for our domain. Highly recommend it if you need anything more than Blazer's table output.

[0]: https://github.com/metabase/metabase

I've never used Tableau, but heard a lot of hate about it. However, in my previous role, we were big fans of Metabase (https://metabase.com). You can also self-host it, which was a huge win for us.

It seems folks want a working example. Here's one in prod:

Metabase is a BI tool, backend written mostly in Clojure. Like basically all BI tools they have this intermediate representation language thing so you write the same thing in "MBQL (metabase query language)" and it theoretically becomes same query in like, Postgres and Mongo and whatever. End user does not usually write MBQL, it's a service for the frontend querybuilding UI thing and lots of other frontend UI stuff mainly in usage.

Whole processing from MBQL -> your SQL or whatever is done via a buncha big-ass transducers. Metabase is not materially faster than other BI tools (because all the other BI tools do something vaguely similar in their langs) but it's pretty comparable speed and the whole thing was materially written by like 5 peeps

https://github.com/metabase/metabase/blob/master/src/metabas...

(nb: I used to work for Metabase but currently do not. but open core is open core)

They haven't released the source, and the compiled versions are non-trivial to diff (e.g. there are nondeterministic numbers from the clojure compiler that seem to have changed from one to the other, and .clj files have been removed from the jar).

The old version has `hash=1bb88f5`, which is a public commit: https://github.com/metabase/metabase/commit/1bb88f5

We are unsure about the right license to use, so this is a great feedback. We had a MIT license one week ago that we know that we cannot hold on long term and we felt we were lying to the community by keeping an MIT license and changing it in one year.

By using AGPL, we feel it's the right level of restriction. It's the license used by Metabase for example (https://github.com/metabase/metabase) that many companies use internally.

The solution really depends on what sort of problems you are trying to solve and who your customers are.

There are a fair few low-code solutions out there for reporting and data visualisation that are great for finance and marketing teams for example. e.g. https://metabase.com/ , https://evidence.dev/

For multipurpose SMB workflows and organisational processes, I have used n8n in the recent past and found it was quite good and incredibly easy to maintain. https://n8n.io/engineering-resources/

For enterprise processes I'd go with Camunda (solely based on recommendations and not first hand experience). Although only parts of their platform are OSS https://github.com/camunda

Bear in mind that some of these are not suitable if you want to build something that competes with them while taking their OSS code. But are perfectly fine otherwise.

Anyway, I have a collection of scripts that merge ActivityWatch data from all my machines and WakaTime exports to a PostgreSQL database which I then query with a project called Metabase. If you're curious, the scripts are in a repository called sqrt-data. I've been playing with this for ~4-5 years already I think.

Metabase | https://metabase.com | REMOTE | Full-time | Backend, Frontend, Full Stack, and DevOps engineers

Metabase is open source analytics software that lets anyone in your company rummage around in the databases you have. It connects to a number of databases / data warehouses (BigQuery, Redshift, Snowflake, Postgres, MySQL, etc).