Easy to use API to configure everything
Support for foreign-key table relationships experimental
Query Builder GUI coming soon
More to come...
Supports MySQL, SQLite (PostgreSQL and SQL Server coming soon)
No Framework/ORM Needed
Support for MVC Frameworks like Laravel/CodeIgniter coming soon
Full security against SQL Injection/CSRF/XSS
Supports custom authentication (you will have to build authentication logic) coming soon
How does it work?
Step 1: Create a PHP file
Step 2: Open the file in your browser
Here’s what you get:
A “summary table” which allows users to browse a summarized version.
A form to edit and create new rows of data.
All SQL queries, fully escaped and sanitized handled on your behalf.
How is this better than PHPMyAdmin/Adminer/etc?
PHPMyAdmin/Adminer are great for administering and managing a database. If you are comfortable enough with that, CrudKit will likely be not of much use to you but however there are some distinct advantages.
CrudKit lets you define field names and descriptions for all items, so you’ll get a more human friendly Favorite Banana Brand instead of fv_bnn_brnd.
CrudKit performs validation and lets your users know if something went wrong.
CrudKit has more functionality when working with table relationships, and will help your users deal with direct records and not worry about the primary keys.
Generally, CrudKit is simpler, easier and more pleasant to use, especially on mobile - because it focusses on the tables and records, not of the actual database itself.
Why do we have to configure it with code, why not detect database info?
There are similar tools that automatically detect database info and builds up an interface, but as a fundamental decision, CrudKit will not do this. In order to illustrate why, consider the following situation:
You have to generate an interface to edit a database. You install a tool which reflects out the columns of all your tables and builds a nice GUI for it. This works well until you start to try and modify something. Maybe some fields aren’t needed they are still included. You have to manually remove them, then in order to change validation rules or field names, you have to keep editing the generated info.
On the other hand, CrudKit doesn’t start with something and ask you to modify it for what you want. Instead, CrudKit gives you a clean slate and tools to build exactly what you need, so you know exactly what’s happening.
Built by Anirudh Sanjeev. CrudKit is distributed under the MIT/X11 License.