I like to throw together small tools to automate things. Most involve Crud screens. Simple Crud screens are all very similar but seem to take a lot of time to throw together. Are there good tools that allow you to throw these up quickly?
I have been deferring another show hn since the last one, since I am always in the middle of adding one more feature :p
my overall goal in daptin is to build something reliable which can run for years without needing any maintenance. Some things to show this is that its written in golang and I build static targets for all target hosts, the thing is open-sourced and licensed to be used without fear.
As for the features, I will try to list some here:
I haven't planned mssql, mostly because the library which covers most sql dialects in golang currently supports just those 3(mysql, postgres, sqlite) .
I can look into it but I don't know what's the fastest way to get a mssql instance right now :) it might not actually be a huge task.
If you want No Code solution, AirTable and Coda. On one hand I sort of wish more business knew about it as it would likely simplify most of their work load. On the other hand I dont want that to happen as it gives current businesses advantage.
For Coding Solution, ( Incoming Unpopular opinion ) if you dont mind modern PHP, ( which is a lot better than old PHP) Laravel [1] is to my mind undoubtedly the king of CRUD framework. The whole ecosystem is, and continue to be outpacing and growing faster than Rails ecosystem. Which makes me very envy.
I am a long time fan of Laravel.
A tool that I find to be extremely useful for building out CRUD front ends in Laravel is the product Nova[1] which has been developed by the core maintaienrs of Laravel.
Really fast for building maintainable admin/back office UIs quickly.
It was very well deserved back in the pre-7.0 days, when it was common to have horrific spaghetti projects with zero structure, global variables/functions everywhere, and all kinds of logic (including database calls) mixed into view templates. Modern PHP is a whole different world, but most people will simply choose something else now because that stigma is impossible to lose, and finding dedicated PHP developers is increasingly uncommon.
I disagree. You can't slap on features on a bad language and make it good language. You can only make it more palatable.
Good languages start good because the people who designed and built them had good idea of what they wanted to achieve and did not have existing users to compromise with.
A great developer will write great code in any language/framework. A bad developer will write bad code in any language/framework. I have seen this so many times in my 25+ years of developing software and don’t expect this to change anytime soon.
I still dont like PHP in any sort of way, as a programming language it really is the bottom of my list. At least modern php is easier to swallow.
But Laravel, the amount of things that could get done in so little time. I think laravel took all the good ideas from Rails and ran way further ahead with it.
Combine React Admin with Hasura (automatic GraphQL on top of PostgreSQL) and you can build an entire back office admin suite (API endpoints and admin front end) in a matter of hours.
I really like React admin have used it for several projects now. Really fast to just knock out a back end admin system for managing users, roles, settings etc.
What's the backwards compatibility/breakage story? I think that's a critical question for any tool that wants to be the go to place for this kind of task. It has to be the kind of project you can run for years, making small changes to, and still be secure/deployable/upgradable.
Hasura allows you to use a pre-existing Postgres database as its source. Alternatively, you can either build a schema from scratch in SQL, with some other tool, or use Hasuras web console which has a visual schema-building and relationship-building UI.
The team takes pretty good care of upholding backwards compatibility -- as it stands, most of the new features they have been working on are niceties outside of the scope of basic CRUD functionality and permissions/authorization (which they have pretty much nailed at this point).
Hasura Engine instances are versioned, and if you like, you could also opt to just never upgrade.
Thanks, but isn't that just the backend/API? I should've stated this, but what really triggered the comment was the React frontend. There's a lot of churn in the JS/React world.
So for example, you could start with Hasura back end (GraphQL) and later swap to a custom JSON API without changes to the UI code. As for the react-admin framework, it's been around for a while and has regular frequent.
If you want a database-backed CRUD with extra business logic then it's hard to beat the Django admin. You get support for common cases out of the box and extending/overriding the normal behaviour is fairly straightforward.
It looks fairly presentable and has a non-awful UI. Certainly not state of the art but good enough for non-public facing stuff.
I have used the Django admin as a way to get non-technical users entering data for basic CRUD, which is pretty much what it was developed for originally as I understand it. Its appearance sends the right message (non-threatening, but obviously not public-facing), and they seem to take to it readily.
For Django, the trick is to implement an MVC pattern: let a class sit in-between a model and its set of views and pilot the views from there, like the admin, drf and others.
However, the admin does not leverage the Django ecosystem, django-tables2, django-filter, and so on. Also, it's kind of moving slowly because they must try to respect backward compatibility.
I maintain CRUDLFA+ and I love it:
- lets each view define its own url generation method: the controller will use that to generate the urls for a model
- each controller defines a get_queryset method which has a request parameter, allowing you to define what objects a user may see
- each view defines a has_perm method, as such a user may see a bunch of objects, but not necessarily execute all views on it,
- the default list view wraps django-tables2, django-filter, django-search, and generates a per-object menu, by iterating over each view of the controller and testing it with has_perm, as such a user will see an object menu with each view it can execute on an object, with no overhead
- allows you to override views in many ways
- works with non-managed models (models that are not backed with a database table)
- can be used for frontend pages too (admin is really limited to being a back-office),
Clearly, CRUDLFA+ goes beyond "basic crud", but I would never code a Django view without it ever again though.
However, so far I make it for my personal use and even though it's been in use on governmental production for a couple of years now, I wouldn't recommend it for beginners. If you're a Django expert and get your kicks out of trying new patterns then you might spend some good times with it.
We're in the (slow) process of replacing Jinja2 in it with Ryzom ( https://yourlabs.io/oss/ryzom ) , a component-based HTML renderer which supports data-binding and that we are looking forward to integrate or isomorphic research (from https://yourlabs.io/oss/chp ) into. When that's over we will release v1.
To me it's still surprising that nobody has done something like MS Access or VB6 for the web. They were easy to learn but had enough power to create really complex solutions. The only downside were scaling and multiple user support. These problems shouldn't be that hard to solve.
- Plug-in integration with Python code running anywhere else on the internet. You import a library, it connects via websocket to your hosted app, you get two-way RPC between your code any your app
(https://anvil.works/learn/tutorials/jupyter-notebook-to-web-...)
I love access, and pushed it at many jobs that I have been at. Many times you have small teams who just are not worth the investment of enterprise systems while they are still growing that part of the business. Access allowed them to solution their needs while the requirements are still in flux. Once a department becomes big enough the access solution serves as a working prototype to generate requirements to build a proper system. It is a shame that Access has fallen out of favor and there really are no web tools that compare to how well it enabled users.
One could argue that Microsoft PowerApps (Dynamics 365 CDS model apps) is the enterprise equivalent of Access. It's extremely easy to build a CRUD app without writing any code.
Access has always been relatively easy to build an app with close "to no code". The problem is that you still need to understand the principles of a relational database to use it properly and that is usually taught after basic coding.
https://apex.oracle.com is a solution for most of the use-cases similar to MS Access and VB6. But useful only if you have an Oracle database.
I mentioned OpenXava as a development tool in another post. They had their own 0 programming hosted environment with similar ease of use as APEX, but I can't find the link now.
Same. I'm building the foundations with a relational lang (https://github.com/Tablam/TablaM), because where Access/Excel "fail" was to have a huge disconnect between how use it and how program it. Also because I think the lang could make everything else easier (for example: transform datasources).
Where some tools in this space ALSO fail is to be ONLY for cloud. I think nothing will displace access/excel if don't have a native/local experience.
We're working on a new VB6 for the web platform, and would love your feedback :). Good for quickly spinning up CRUD apps with a few new features such as embedded BI and simple ML tools.
It's still in early access, but if you'd like to play around with it, please don't hesitate to message me at verygoodtool1@gmail.com.
Also, pro-tip: host it on Heroku for ease if you're not anticipating a ton of traffic. Literally minutes to set up and almost no maintenance overhead going forward.
Django has everything a simple CRUD needs built-in, and migrations, which you don't need now, but will need if your project is successful. Highly recommended.
+1 for Django. It is well structured, battle tested and highly scalable. You get all the simplicity and "batteries included" features of Rails with much better performance and RESTful API support.
I think the meta-answer is to pick the CRUD framework for the language that you already know well; e.g. if you know Python, use Django. But if you know PHP already, just use Laravel or whatever, rather than learning Python to get access to Django.
While there are features in some of these frameworks that will give you a productivity boost in certain use cases, none of them are worth taking the productivity hit of learning a new language.
For non-web, give the Red programming language a try. Java is also another good one. I am afraid there just isn't a good, robust, free and open source system when it comes to client-server stuff. Rapid development tools also tend to be less mature on Linux, compared to OS X and Windows (Mac and Windows have a rich tradition of business/enterprise rapid prototyping e.g. FileMaker, HyperCard, Visual FoxPro). If you are on the Microsoft stack (and don't need gimmicks like multiple screen size support, Material-style shadows and animations), the standard WinForms system is also quite productive. I heard that the new SwiftUI system is starting to bring back the spirit of rapid development too though I have no tried it myself. These days "no-code" systems are also making a comeback with half a dozen new SaaSes showing up on HN every other week.
Red is cross-platform and works pretty well on distros that support 32-bit libraries, GTK backend is also fully functional [1], so I don't get why Linux is excluded from your list.
Red author also plans to port Cheyenne web server at some point after 0.7.0 release. [2]
Remake - a server-rendered framework for building CRUD web apps [0]
This is an open-source framework I've been working on for the past year to try and solve this problem. I was tired of building the same back-end over and over again and wanted to be able to define my data all in one place.
It works kind of like Vapid[1], in that it allows you to define back-end logic with front-end syntax. But it goes a step further and has more built-in web app capabilities like support for each user owning their own application, nested elements and pages, sorting elements, and inline edit areas.
I just posted a Show HN[2] in another thread. I love for you to read more about it there. You can also see some code examples and a simple demo application here: https://docs.remaketheweb.com/
Reach out to me with any questions. I'm always available to talk: david@remaketheweb.com
One piece of feedback, I had to go into the docs, under (A Simple Example App) to get a sense for what it was/how exactly it worked.
In place of the video that is the first piece of media content on the landing page, I would have much preferred some snippet of code and a visualization of its result. That way as soon as I come to the site, I get a feel for what exactly it is.
I think this would markedly improve your ability to communicate what Remake is. As the old adage goes:
I agree, however, something short and sweet showing off the code and how to build something is sorely needed on the home page. I'll brainstorm about it and update the page soon.
Jhipster if you want to do it in Java. Do check it out if you want a lot of options. For example angular or react frontend, SQL or nosql, monolith or microservices. Warning: it relies heavily on spring framework. So that may be an entry barrier too.
OpenXava (https://openxava.org) is an platform that is open source and automatically generates user interface based on CRUD operations (+ much more). Even for one-to-many or many-to-one associations, it creates look up lists and master-detail user interfaces. It also creates interface for searching, for printing reports, for custom queries, for group-by and similar aggregate queries and much more. All automatically.
How? It uses information that you provide which Java class corresponds to which table, Hibernate style JPA ORM annotated classes, either in XML or as plain java classes with annotations (one class per table).
If you have a large database, with multitude of tables, you can use the Hibernate / JBoss reverse engineering tool to generate the mapping classes directly from the database structure. See this: https://eugencovaciq.wordpress.com/2016/02/01/hibernate-tool...
There are other tools that could help. Why OpenXava? Because it is very easy to customize the generated user interface and it is very flexible. You just add @view annotations to the classes that modify how the interface is generated. For example, when you need to drop out some attributes, or not show a link to another table, or when the table is used as a lookup for the foreign key in another table, you can configure how the lookup will look like in one situation, and how in another. You can reconfigure the layout of complicated forms for tables with many attributes, also using view annotations.
I am not involved with OpenXava, but have used it to make an administration interface for several apps. I have a maven script that can be run from the command line, that uses hibernate reverse engineering library to generate the mapping classes and i have the initial app in minutes.
Are you looking for a framework or a more complete tool? Django or Ruby are good for putting together CRUD tools very quickly. If you make use of their ecosystem of libraries you'll be able to put a Bootstrap CRUD app together in no time (assuming you have webdev experience).
DaDaBIK (https://dadabik.com) is a no-code low-code platform that can generate a Web CRUD app in minutes starting from your existing DB (but you can also design the DB in DaDaBIK itself).
It has been around since 2001, CRUD generation has been its main aim since the beginning, with the last versions you can also generate very complex applications injecting some custom code (php, javascript) to implement your business logic.
There are a lot of nocode/lowcode tools with batteries included if you do not mind paying a monthly fee (although some do not even require that; only a one-off fee). Airtable, Bubble and many others make it really easy to create CRUD apps. There are also open source solutions (I did not try so no idea how good they are) like [0].
Low-code solutions are great for this. I worked at Mendix in the past, which I still really like. Competitors are outsystems, Google appmaker, Microsoft powerapps and more.
Counterpoint, I started using SQLite with Python and after less than a day of writing SQL manually I decided just to learn SQLAlchemy. Its cut the amount of code down a lot and the learning time has paid itself back quite quickly.
Grocery CRUD is a CodeIgniter/PHP library that lets you quickly create a CRUD with views. Officially it only supports MySQL but some third-party patches let you use it with other databases.
You shouldn't overlook Orbeon Forms, it has history going back to 2007 (it seems quite mature).
I believe it can just be used like a robust black box to do both CRUD and HTTP web front ends.
Yes, Form Builder, in Orbeon Forms, allows you to create a page with form fields, use the provided values to call a REST/CRUD API, and show the result on that page. You can try that out for yourself on demo.orbeon.com, or download the software and run it locally.
There is an open source (LGPL) Community Edition, but the services & actions feature you need for this is only available in the Professional Edition. This being said, if you just need this for your own local testing, you can get a trial license (automatic process, valid 3 months, no limit on number of licenses you get), and have fun with it.
Bias: I'm one of the Orbeon Forms developers ;). ‑Alex
If you are looking for something proven I would use django. It is easy to add new models and generate crud-UIs with django-admin. Django has many useful modules for extension.
Django's migrations are a nice way to take care of database changes. The NoSQL crowd should try this out before ranting about the benefits of "schemaless".
Try CakePHP. The `bake` tool allows you to create CRUD functionality quickly. Just create your database and run `bin/cake bake all` and it creates everything from models, controllers, views (templates) and even tests!
I have been using it since 1.3.x days and it's just got better over the years - migration between versions was relatively painless.
I really don't know the answers to that, but I did do a bit of testing on my old Mac Mini (late 2009, 8GB ram).
I wrote a script that created 1000 documents that were pretty small just a few k at most.
The app I wrote using pouchdb to use find and edit them started choking when Safari had about 5000 documents stored in it.
If you install CouchDB on your local box, or a remote server, and configure PouchDB to use your CouchDB to store and access those docs you can probably have 10s of 1000s and I know you can scale that up to millions of documents with the right hardware.
You can get industrial strength remote CouchDBs from IBM and CouchBase for a pretty reasonable fee too. And you can run PouchDB with Node,js on a server and store your docs on it. So there are a lot of ways to use it.
If its for internal use then Django's admin interface is pretty good. It's limited in some aspects (you will need to login to use it) so better suited to internal use than public facing websites, but for many tasks it's amazing.
There is always swagger codegen, which I have not used in a while. I believe you just give it your json swagger spec and it can generate server stubs of about 20 or so different languages/frameworks.
https://github.com/daptin/daptin
I have been deferring another show hn since the last one, since I am always in the middle of adding one more feature :p
my overall goal in daptin is to build something reliable which can run for years without needing any maintenance. Some things to show this is that its written in golang and I build static targets for all target hosts, the thing is open-sourced and licensed to be used without fear.
As for the features, I will try to list some here:
- YAML/JSON based data declaration
- CRUD api implementing https://jsonapi.org/
- GraphQL api
- Definable actions, for custom apis
- Integration to any 3rd party api based on swagger/openapi spec
- Runs on mysql/postgres/sqlite
For more advance features:
- SMTP server, IMAP server
- Self generated cert/ Acme TLS generation support
- Encrypted columns
- Asset columns (file/image/binary store)
- Asset columns backed by cloud storage (like ftp/disk/gdrive/s3/bb and many)
- Native OAuth/3rd party login support
- Exposing cloud store folders as static websites
I have built a lot of apps on daptin over some time now and I love that it has become what I envisioned it to be.