Separate Dashboard application

[tomjanssens]

Idea

I would create a single 'application' to manage the box. The application would consist out of different specific components build solely on top of Joomlatools Framework, in combination with Joomlatools Platform and could re-use some of our re-usable components if need be.

Name

We need to decide on a name for the application, possible names that come that to mind are : admin, administrator (to follow Joomla convention) and manager.

The name as such will not have much impact as it will not be used at all. In a single application the name does not need to be referenced in object identifiers, as we do not jump between apps. It would just be the global folder under which we would put the code.

Structure

Proposing the following repo structure (which is a mix of Joomla and Nooku conventions)

• /application
  • /cache
  • /config
  • /component
  • /public
  • /vendor

We would build a com_application to act as the front controller and dispatcher in a similar way as we do with Nooku, for the template we would use Bootstrap 3. based on the new template we added to the box.

Notes

• Build it as a seperate repo eg joomla-vagrant-dashboard to eep things separated? joomla-vagrant repo is configuration management, joomla-console and joomla-vagrant-dashboard are applications and should be kept separately. Also makes it easier to install (using Composer/git clone) so we don't have to introduce another mount point.

Repo Name : joomla-vagrant-dashboard Description : Joomla Vagrant Box Dashboard, build on Joomla Platform

Conceptually I think the OpenStack Dashboard comes very close to what we are doing : http://www.openstack.org/software/openstack-dashboard/

• The dashboard application a frontend for the console itself. Down the road you will want to be able to also create new sites through the dashboard easily, that logic already sits in the console, then we would need to replicate it in the dashboard. Adding a joomla site:list makes total sense in that context.
• Instead of calling the repo for this joomla-vagrant-dashboard, we could also just use joomla-dashboard. If we build this as a separate app, we can ensure that it also runs outside of a vagrant environment, much like the console does. This would allow people to install the dashboard anywhere, like they can install the console anywhere.

[johanjanssens]

@yiendos this is Related too #114 which you assigned to yourself

[yiendos]

@johanjanssens check thanks for this information, seems they have killed that page. This seems quite similar:
https://github.com/openstack/horizon

[johanjanssens]

An idea could be instead of running a complete Joomlatools Platform App, we actually only run Pages + an even lighter version of Platform that no longer requires a database and has no admin (which we already do for Joomlatools.com)