Web application admin generators [closed] - php

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Questions asking us to recommend or find a tool, library or favorite off-site resource are off-topic for Stack Overflow as they tend to attract opinionated answers and spam. Instead, describe the problem and what has been done so far to solve it.
Closed 9 years ago.
Improve this question
Since Symfony 1.x's admin generator, I found this kind of tool really useful to prototype applications, show something very quickly to customers etc.
Now for Symfony2, admin generator does not seems to be a priority (see here and here)
Django's admin generator seems very interesting...
Which web application admin generator (any language / technology) would you recommend (pros / cons)?

Django's automatic admin app is excellent. Once you've written your models, it automatically creates a full-featured admin app around them where you can create, update and delete records. It's also extensible and customizable for just about whatever you need.
Here's a pretty good overview about it. Django (and python) is intuitive and satisfying to work with -- I highly recommend that you set it up and play with it and see how well it works.

Updated 2017
Agile UI (a successor of atk4.3) is an MIT based PHP UI Component library. It gives your application nice looking, consistent User Interface without you have to write any HTML and works with any PHP framework or application.
Demo: http://ui.agiletoolkit.org/demos/index.php
The reason I think this is better than a built-in generator:
Almost no dependencies, works with any framework or PHP app.
Can work with SQL or NoSQL, relies on Agile Data.
Stylish, modern and responsive. (Semantic UI)
Interactive. "Form" uses JS to submit, display in-line validation. "CRUD" uses modal windows, pagination and QuickSearch.
Extensible. Need charts? https://github.com/atk4/chart.
Open-source
To build a minimalistic application admin you only need 15 lines of PHP code:
<?php
$app = new \atk4\ui\App('My App');
$app->initLayout(new \atk4\ui\Layout\Admin());
$db = \atk4\data\Persistence::connect($DSN);
class User extends \atk4\data\Model {
public $table = 'user';
function init() {
parent::init();
$this->addField('name');
$this->addField('email', ['required'=>true]);
$this->addField('password', ['type'=>'password']);
}
}
$app->layout->add(new \atk4\ui\CRUD())
->setModel(new User($db));
Result:

Personally, I have found Yii's scaffolding is the best there is. Quick First Application
What I truly loved:
Controlled creation of files. Yii provides an interface to create all required files, called Gii.
You have the ability to generate your model classes based on the database model.
You have the ability to generate CRUD operations for all your model classes (Action methods for your controller class).
The generated scaffolding includes: Pagination, Searching, Advanced Searching, Listening, Inserting and Updating includes validation out of the box, Deleting. And all of the interface is ajax driven.

For Ruby on Rails: Here is some discussion on SO
But ActiveScaffold's home page at the moment is still talking about Rails 2.3, so you may want to read past the accepted answer and check the others to see if there are newer ones.
Rails Admin looks to be actively developed and has good pedigree (having been a Google Summer of Code project mentored by big names in the Rails community, so I'd start there if I were looking.

I can recommend CakePHP scaffolding, where you can also add admin routing. Nice for you is that you can stay on PHP, which you also used for Symphony. Be warned, you might get addicted to Cake ;)

something a lot more powerful for CakePHP is https://github.com/josegonzalez/cake_admin, little bit of a Django rip-off :)

I like sprox, for Python. Although I have not found it particularly useful for production, it can help a lot in terms of prototyping and testing -- its simplicity is its strength here, enhancing Python's own strengths.

Padrino has "Padrino Admin":
http://www.padrinorb.com/guides/padrino-admin
While not as popular as Rails, it's built around the excellent Sinatra DSL.

For Rails applications, Rails Admin with CanCan is the best solution as of now. These are very actively maintained and supports Rails 3.0. With CanCan, you can customize access on models. So that you can easily set multiple level of admins/authors. Previously I have used ActiveScaffold for 2.0 application but it doesn't seem to support newest Rails.

Related

My Content Management System [closed]

Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 6 years ago.
Improve this question
I intend to develop a Content Management System (CMS) like shown in the figure below;
Figure: Intended CMS design
Is it possible to completely develop it using PHP's standard library?
Do I need to use a PHP web framework? If so, why and what framework is ideal?
I hope to use MySQL as backend.
I hope to use below technologies as front end;
HTML5 and CSS3 - hard code by myself (Is there any framework or something make it easy? I heard something lesscss.org)
jQuery - to make HTML elements functional
Ajax - to avoid page refreshing
Bootstrap - to make my CMS responsive
Are there any technologies I do use, or any suggestions?
I prefer to improve my HTML, CSS, PHP and other technologies by learning and hard coding. So I hope not to use CMS like
joomla, WordPress, etc. Am I right?
Please note: I've already searched Google extensively before I put my questions here. But I am unable to confirm what I do next. Your comments are appreciated.
Your questions really look well researched and I think everybody with the intention of building a custom-made CMS has come to this point where they ask themselves these fundamental questions (in other words: good questions!). Now to some answers:
1) Yes it is possible.
2) Although building a CMS in pure, native, hard-coded PHP is possible, I wouldn't recommend it for production. You could do it, and you would largely profit from the experience, but there are many little problems (like Routing / User-Management / Authentication / Communicating with Database / Form-Building (like in your screenshot) / etc.) that are already solved by a good Framework.
Also as you are a beginner, you are naturally overwhelmed by the problems and decisions you have to solve/make. This is also a good point why a framework would be a good starter. Although some solutions are sometimes a little too opinionated, they still give you a good structure to start with and most of the times follow best practices of our industry.
Which framework is the most ideal for your project, you'll have to decide on your own, based on your requirements, but some common ones are:
Symfony (probably the most known and most used php-framework, but also very abstract / I would recommend this on a really big project, where you work in a team and you are aiming for flexible maintainability)
Laravel (excerpt from their website: An amazing ORM, painless routing, powerful queue library, and simple authentication give you the tools you need for modern, maintainable PHP.)
Silex (the little brother of Symfony, info from their website: Silex is a PHP microframework for PHP. It is built on the shoulders of Symfony2 and Pimple and also inspired by sinatra.)
FatFreeFramework (from their website: A powerful yet easy-to-use PHP micro-framework designed to help you build dynamic and robust web applications - fast!)
As I used Silex myself many times and also when I began with best-practice PHP, I recommend to start with it, if you decide to write your own CMS. I pretty fast did some Management-CMS similar to your screenshot with it (with their Form-Builder) and was happy with the result.
3) Again this is up to you. For the backend you will probably use MySQL anyway, if you just need a database. In the frontend using HTML5/CSS you could try jQuery and Bootstrap (and then here their less or sass implementation).
If you really don't have too much logic for your JavaScript, you could also try to just use native JS, without jQuery. This way you will also learn more about the language and have less vendor-dependencies the user has to download.
4) If you are really up to learning a lot, then yes, you should probably hand-code everything yourself. This way you also have total control of what code gets delivered to your user. That's a problem with most common CMS: they pollute your code through some other plugins or something and you quickly loose control over your output.
But if you need to be fast there are also CMS that address this issue by giving you total control over your output and giving you creative freedom, like MODX does.
In the end it is up to you and especially the needs of your project. If it's a simple website and you conveniently want to edit the content and also have some starter-help, then I recommend to use a CMS.
If you really want to learn about all this stuff and you have some special needs, then go on and code your custom-coded application. In any way: good luck! :)

Toolbox/framework to construct lightweight public-facing web site [closed]

Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I am aware of full-blown content management systems (CMS) such as SugarCRM and TikiWiki... where content is typically stored in a database... and edited through the same interface as it is published. While I like many of the features, the product is clearly aimed at enterprise-wide use rather than to be public-facing.
What I'd like to establish are potential alternatives that fill the space between full-blown CMS and hand-coded bespoke site. I like the way that I can add modules to my CMS... allowing me to quickly introduce new functionality, and I'd like an analogous feature in a system for public web-content. Modules I know I'd like include moderated comments; web-form-to-email gateway; menus/tabs... in future, perhaps mapping or diaries or RSS integration - etc.
Where my requirements differ from a CMS, I don't need (or want) most content to be editable through the main site... and, somehow, I do want to be able to preview how updates will be presented to the public rather than to make live changes. For these purposes, in contrast to those where a typical CMS would be ideal, presentation is of paramount importance - and trumps any desire to immediately disseminate information.
I realise that this is a very high-level question... (suggestions of additional tags welcome) - I mentioned PHP only as - ideally - I'm looking for an open source solution and a PHP deployment is an easy option.
What are my options?
I don't need (or want) most content to be editable through the main site...
So you don't need (or want) a CMS.
You need to code the thing that you want yourself. You can, however, get help from existing tools. There are lot of API, frameworks, microframeworks... that can help you to do such things.
At first, do you accept to write your code with MVC. If not, the only tool I know is CakePHP.
If yes :
I noticed you wanted :
I like the way that I can add modules to my CMS... allowing me to quickly introduce new functionality, and I'd like an analogous feature in a system for public web-content.
So a framework with an easy "plug-n-play like" architecture would be fun. My experience with Symfony makes me say it is good for you.
for Symfony you have lots of bundles already written. Have a look at KNPBundles and FriendOfSymfony Bundles. FOSUserBundle, KnpBlogBundle are well known
But I also see that :
A framework might well be what I want... Zend is one possibility - though it is lower-level than I had hoped for.
So I can tell you about Silex, a microframework that is based on Symfony core (so it is a high level with no greedy extension) and its bundles architecture.
I also heard about hoa_project (because I follow its creator on twitter) but never used it so I can't tell you more.
The requirements you list are, in fact, those of a CMS. Correct me if I'm wrong, but you want:
Content-oriented modules (article, comment, moderation, web forms etc.)
WYSIWYG preview prior to publish
The ability to create (or re-use) modules
A high degree of control over the presentation layer.
What you don't want is:
"in-page" editing of content
There are many PHP content management systems which meet these requirements; I'm personally familiar with CMS Made Simple which has pretty much all the above. Drupal is a more fully featured (and complex) option which also offers this. Wordpress is a big favourite with those who need to build nice-looking sites in a hurry.
All these CMS solutions are focused at producing public-facing websites, rather than intranet knowledge sharing applications (they're pretty useless at that). Drupal provides workflow which allows you to manage the content publication workflow. The key thing they provide which is non-trivial to build from scratch is a way of providing "WYSIWYG" previews of content.
The major drawback with these options in my view is that they are great for content driven sites, but if you want to integrate functionality into the application, or tinker with the layout, you have to work through the CMS layer which wants to control the user interface; this can become a little tiresome.
This question is the sort that can spark religious wars. Since you aren't asking a coding or programming question, it can't be answered with fact, only with opinion.
In my experience, Symfony has always done well as a framework, following MVC architecture. As with any framework, developing a site using Symfony requires greater commitment and a lot more programming than would be required with a CMS.
I see you want a preview option. While you could do that yourself with Symfony, you might want to take advantage of that functionality within Drupal instead, using its workflow module. Of course, using Drupal's roles, you can make certain pages (or types of page) unavailable for modification.
There are many many ways to implement your requirements. The more research you do, the less likely you'll be to have to backtrack and re-write things.
UPDATE:
The best resources for learning Symfony are found on Symfony.com. Visit the Documentation section. "The Book" is a general resource on All Things Symfony, and I believe it's the most authoritative and complete resource you'll find.** I find it clear and well-written. "The Cookbook" contains examples and strategies for particular types of applications, and is more useful once you're comfortable using Symfony.
** When you're selecting books from Symfony.com, on the right-hand side of the page, you'll see a Select box saying "2.0 version". While 2.0 is the latest "release" of Symfony, you might want to change this to "master version", which will include references to features to be included in the upcoming 2.1 release. Symfony releases tend to be pretty radically different from previous version, so it will be good to develop for what will be "release" by the time you finish your project.
Each of the books can be downloaded as a PDF. All the books from Sensio Labs (creators of Symfony) are licensed under Creative Commons.
As for add-on software, Sensio has released a number of add-ons (called "bundles" in Symfony-speak). These are documented on the same site, but third-party bundles, of which there are many, have documentation generally provided by their authors. You can find a library of open source bundles at http://knpbundles.com/.
As for Drupal, I must admit that I generally implement things in Drupal more than Symfony these days. With command-line management using drush, it's extremely easy to keep up-to-date, and the Drupal software and module maintainers are friendly and easy to find in IRC (on FreeNode). Drupal has a HUGELY extensive collection of online documentation. It can be a bit daunting, actually, but things tend to be pretty well organized. There are a number of books that have been published on Drupal, and may be listed at http://drupal.org/books ... but I haven't ready any, so I can't make specific recommendations.
Without knowing more about your requirements, I can only recommend both Drupal and Symfony. :)
You are almost describing CodeIgniter. See this the video demonstrations and decide if this is what you need. CodeIgniter is not a CMS but rather a framework in which you can easily build a CMS that suits your exact needs.
I would like to add Yii (http://www.yiiframework.com/). A great framework with all sorts of lighten-your-programming features. A preview feature is not on-board, but not hard to add (http://www.yiiframework.com/doc/blog/1.0/en/post.create#implementing-preview-feature).

Lightweight PHP/MySQL CMS for HTML5 [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Questions asking us to recommend or find a tool, library or favorite off-site resource are off-topic for Stack Overflow as they tend to attract opinionated answers and spam. Instead, describe the problem and what has been done so far to solve it.
Closed 9 years ago.
Improve this question
So far I've build my websites with Typo3 but it's a bit of a heavy beast for smaller sites. I've also done some projects with Drupal and Wordpress but my impression is that they mess up the HTML a lot and it is too much effort to "correct" them.
I like to build some smaller websites with HTML5 now and was wondering which PHP/MySQL-based CMS could be right for that.
In the end I went with Concrete5 as it was recommended to me by various people and seems to be very well-written! http://www.concrete5.org
Unfortunately, every publicly available stock CMS system will, ultimately, have the downfall of messy output. This stems from the fact that they attempt to be something for everyone, rather than a targeted product.
Rolling your own CMS is not that big of a challenge with a little PHP knowledge. If you're familiar enough to know what you want and how you would lay it out, there are a ton of great resources for developing your own CMS, including:
http://www.ssdtutorials.com/premium-tutorials/series/cms-dreamweaver.html
http://www.developphp.com/view.php?tid=322&t=Intro_How_to_Build_Custom_PHP_and_MySQL_CMS_Website_Software
http://www.packtpub.com/cms-design-using-php-and-jquery/book
http://www.packtpub.com/php-5-cms-framework-development-2nd-edition/book
Essentially, a simple CMS boils down to dynamic page generation with a server-side scripting language and templating, a database to store content, and a backend for management. At it's simplest, you have one page template (your content always is output to a simple template, as in a blog or something where you rarely have different types of output), and your backend consists of a log-in to password protect a form that updates your database.
To get back to the main point, however, HTML5 will only be involved in the output for client-side rendering. That is, if your template is HTML5, your site is HTML5 (for all intents and purposes, at least to your visitors).
A question like this will generally get a lot of opinionated, debate type responses because every developer has different opinions and different tool sets.
For smaller projects, I prefer to use some light weight components and build it rather than using a packaged CMS.
Me personally, for smaller projects:
HTML5 Boilerplate, it gives you a great starting point, and once you
have used it and are familiar you can quickly customize it to your
preferences. http://html5boilerplate.com/
FlourishLib, is a great no framework library, it is quick, easy to use and the documentation is great. http://www.flourishlib.com
jQuery, is a great tool for your JS needs.
I spent so much time playing around with other packaged CMS that I found I could have already had the project up and out the door by the time I tweaked the CMS to get what I wanted out of it.
And using this tools you can easily create your own boilerplate to get your project started quickly.
Again, this is just an opinion based on my preferences.
You can check out glFusion at http://www.glfusion.org with all the features it has right out of the box. Unlike allot of other CMS's glFusion is free, including the plugins. Latest version 1.3.0 as of the time of this posting, will have html5 and also be w3c validated.
If you are looking for a lightweight and fast cms build on HTML5 and CSS3 then Gecko should be the right one for you!
Check CouchCMS - i think it is the best one for your purpose www.couchcms.com
Perch CMS (not free but very cheap) is very lightwight, may want to take a look. http://grabaperch.com/
I really like GetSimple CMS. I use this on a majority of small projects because it is incredibly easy to set up. It is PHP powered, and does not require an SQL Database. Instead it uses XML files to store content.
http://get-simple.info/
As a previous poster mentioned, HTML5 Boilerplate and jQuery provide a quick way to get set up and I often use these in conjunction with each other.

php framework help [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 3 years ago.
Improve this question
Ok so before anyone states the fact that the php framework question has already been answered, note that I am asking questions specifically on which framework would be best given the requirements that I am providing. I am currently in the proccess of building a large project. I will be in the future working on several medium/large and a few small projects. I am an experienced php developer and fully know OOP inside and out and have a great knowledge of mysql database so learning a system is not a problem.
Now that is out of the way down to what I am actually looking for. I have currently been using a "framework" that is not so great and was provided to me for my projects. I would like to get rid of the "framework" and actually start using an actual framework. I was thinking of building my own framework but was considering (and really leaning towards) using an already preexisting framework. I have looked at a bunch of frameworks and even played with a few of them out there. Once I choose a framework I am going to want to keep using it and not have to switch 6 months down the road so before I choose I will be doing some thorough testing before making the final decision. I would like to get some input from some users as to which ones would fit my needs best.
In a framework I am looking for the following items:
Speed - because of being larger projects I will need to keep speed in mind. I can write efficient code but if the framework is slow it really wont matter now will it :)
Authentication - I would like to be able to use some built in authentication if possible through the framework. I dont necessarily need granular permissions based on users but more or less through groups (granular permissions is not a turn off just not a requirement).
Ajax - I like to use ajax in my applications so I would like some kind of ajax implementation in the framework and personally I prefer jquery. It doesnt necessarily need to have built in ajax features but a way to kill the page with the ajax output before anything is output for efficiency.
Forms - I have seen that alot of frameworks have built in features for managing forms but just thought I would mention it here to save myself the headache.
Administration - This is possibly one of the most required features that I really need. I need to be able to create a backend to manage the site. I dont want to have to hack something together to make this work.
Api - I will be in need of an api for accessing/modifying data that I will be allowing.
Database - Built in database methods. Doesnt necessarily need to do it automatically, just give me access to be able to retrieve/update the data that is need.
These are not neccessarily requirements but more or less nice features:
I would like to be able to encase all of my data that goes with a certain item into a "module" of a sort. So that I could easily copy it to another site and have it all ready to go.
An easy to navigate structure. I would like to be able to go into controllers and not see 50 files but instead see maybe 10 folders with the files encased in the folders so that it is better separated.
I cant really think of anything else at this time but if I think of anything else I will update the post. I would really like to get feedback from people who are using any frameworks out there. If you havent messed with a framework please do not recommend it as you have no experience with it and will not know if it would suit my needs. Any help is appreciated.
EDIT:
I just wanted to edit this post to clarify some stuff. In the requirements/features that I am looking for I do not necessarily need all of the features to be built into the framework. From some of the responses it seemed as if people were thinking that all of this stuff has to be pre-ready. I more or less am looking for a framework that supports all of the features that I am looking for that is easily accomplished with the components in the framework. For example the administration, it does not have to have a default administration area but allow for me to create an administration easily from the components that I will be adding to the site.
From my own experience ( CodeIgniter , Zend Framework ), but realy all major frameworks will allow you to do everithing you asked .
Speed - CodeIgniter is the fastest i worked with , this is not the strongest feature of ZF , in fact where i work we all got to the conclusion that ZF is slow .
Auth - Zend Framework handles auth better than what i saw in other frameworks
Ajax - All major Frameworks will allow you do disable the layout/view , Zend is slightly better here , as you can have special json views.
Forms - CodeIgniter framework handles forms easyer than ZF , however all frameworks should deal with this problem with ease . Symfony needs to be mentioned here with it's form generator .
Administration - Symfony just becouse it has a nice crud form generator based on the tables you're passing ( "admin generator" how they are advertising it ) , witch will speed development quite a bit .
???
Database - ZF handles databases nicer in my opionion , however i've heard good things about Symfony too . CodeIgniter here is not that strict witch is not a good thing in my opinion .
Modular App - Building modules in ZF is realy easy , and the feature that i like most is that a module structure looks like the whole app itself ( eg. the whole app is a module ... )
Easy to navigate structure - All of them once you are used to it , however i don't like the fact that CodeIgniter keeps all it's controllers in one place , when in ZF you can add modules and separate things from one and another .
Well, I worked with several PHP frameworks in the past and there aren't many good frameworks. You could risk a look at Zend Framework
ok
ok (but not enterprise level)
ok, but dojo
complicated
no, its a framework, not an application
ok, but not really a ERM
encapsulates PDO in an ugly way (bad implemented factory pattern)
ZF is developed by Zend itself, but I wasn't really happy with that too, because it has a lot of shortcomings (cruel DBAL, complicated form handling, supports dojo instead of jQuery) and if you are used to Java/JBOSS or .NET it just sucks (only mentioning this because you are planning a big project).
If you have some time until your project needs to be deployed and if you dont need to start immediately, you could also try FLOW3 (still alpha) which is developed by the TYPO3 Team. I've played a little bit with FLOW3 and can say that it is the only PHP FW which has at least a good architecture and some good ideas/paradigms (AOP e.g.).
If I understand you in the right way you would need something like a CMS for your backend. Maybe it would be a good idea to evaluate exiting CMS's and check out if you could extend them (use the CMS as framework (TYPO3 e.g.)).
You wont find a FW that matches exactly your needs, therefore you should consider choosing a CMS/FW and customize it in the way you need it. If the project is as big as I imagine there should be enough resources for such task.

Scaffolding for PHP [closed]

Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
Is there any thing in PHP to create basic scaffold, like in Rails?
EDIT: I need something to prototype quickly..
Some frameworks like Symfony, CakePHP, Akelos, CodeIgniter and others have support for scaffolding.
However if you don't want to use a framework you can try phpScaffold which generates CRUD scaffold pages based on phpMyAdmin table exports...
I also wanted some fast prototyping, but I wanted it to generate the code, so it's easy to update it. I made many improvements on phpScaffold (HTML5, nice CSS, many models at once, etc) which are published on http://github.com/tute/phpscaffold.
Phreeze makes this simple and easy. http://phreeze.com/
QCodo is another great option. And since it uses reflection to do Code Generation instead of reflection at runtime, you'll likely see better performance.
First, Rails is a framework. PHP is a language. PHP does not have built-in scaffolding support, just as Ruby--the language Rails is build on--does not. A framework like CakePHP, however, does support scaffolding.
Second, I see that you raised an objection to CakePHP because "you still have to do a bunch of stuff." That's true--with any framework, you're going to have to learn new conventions, configurations etc.
CakePHP got plenty of scaffolding options
If you throw Crud + API plugin on top, you basically got everything you need, with tons of nice additions
cakephp-crud: The active successor of the two projects below. Provides both Crud actions, API, Scaffolding, Searches and more
Crud Plugin: https://github.com/nodesagency/Platform-Crud-Plugin
API Plugin: https://github.com/nodesagency/Platform-API-plugin
They all utilize CakePHP events, so its really simple to extend and modify the default behavior
For myslef I Use CodeIniter for development, sure they have scaffolding, but only in terms of a "simple scaffolding" which mean you're not gonna use it in live product (i dunno about everyone but i'm only using it as some tools) .
but if you need some like CRUD generator you can use SparkPlug , or Ignition both of them can be used on Codeigniter
This was asked quite some time ago, but if it's still relevant check out this nice scaffolding class (check the demo)
Yiiframework has a good code scaffolding system called Gii. It's web based. Once you create the tables, you can generate the CRUD classes from within the browser. No command line needed. I like this scaffolding.
If you use CakePHP as the web framework it supports scafalding. See this link for more info. http://book.cakephp.org/2.0/en/controllers/scaffolding.html
I'm not sure what the SO policy is for dead thread revival but I figured I would add my own two cents in case none of the above solutions were satisfactory. If you're looking for a PHP-based MySQL scaffolding tool, check out AMPLE Scaffolder. The entire package is contained within a single PHP file (less than 200k) that can simply be dropped into a web accessible directory whereupon you have immediate access to local and remote MySQL databases based on the internal database permissions. No schema exporting, configuration files, or other hassles. Plus, there's a whole lot of other capabilities to offer as well. Just thought I'd share it in case you were looking for another option. Feel free to check it out and post feedback if you have any questions.

Categories