Put back lightweight dashboard

[frankrousseau]

Lightweight dashboard is useful for newcomers. It would be nice to see it back and add an option to not set it up for people who don't want it.

The dashboard should reload automatically if it's added again.

[maboiteaspam]

How about creating a new module to take care of the setup sequence ? A kind of cozy-light-install which would install cozy-ligh standalone server, cozy-dashboard, cozy-homepage.

I think about this solution becasue IMHO there is a missing app, cozy-catalog. A sort of application catalog that helps user to browse and manage his apps/plugins. Such kind of app could not fit into the standalone server, it must be an app, in the same time in terms of user exeperience i believe it s a must have and it should be available out of the box.

[frankrousseau]

Nice idea, I have to think more about it. We could also imagine plugin/app packages.

Ex

Personal cloud:

• dashboard
• auth
• file app

Personal website:

• html5-apps
• docker-apps
• domains

Video game console:

• dashboard
• html5-apps
• pouchdb-api

...

[maboiteaspam]

yes exactly. Sort of distro which would include human check of the integration and quality of the selected components.

[frankrousseau]

I think I have the answer. When CL starts, it checks the content of the config file. If there is nothing installed or no config file, it runs a wizard proposing to install one of the distribution. It would require extra work but won't break the flow of the newcomers. What do you think about it?

[maboiteaspam]

I have two remarks on that proposal, 1/ i wonder if it is not too much 'not strictly related' code in CL main server 2/ Can this solution let someone else create it s own recommended setup ?

I think, somehow, it goes against the philosophy i understood of the project that is to provide a platform, and then let plugins / apps do all the jobs to fill in the user needs.

Should we not continue to pluginize/appinize (?) most of the tasks ?

[frankrousseau]

What I call a distribution is a set of plugin distribution. The only action performed would be to install a preset list of modules. That way the user would start with the right modules for a given task.

[frankrousseau]

I'm working on it. What I'm going to do:

• Provide a new command install-distro that allows you to install a distribution in a given list
• Add information in the README
• A json file containing distro descriptions

[frankrousseau]

Done!

[maboiteaspam]

looks good !

[maboiteaspam]

I d like to have some standards controller on it. /install, /uninstall. So that from github, we could provide a 'link to install' IE : http://localhost:19104/dashboard/install#some-app-name

Things is, if we have many dashboard, and they don t share a base, this funtion won t work well for end user, it s going to be messy.

[frankrousseau]

I prefer we add it via a plugin.