Read the statement by Michael Teeuw here.
Use npm for module installs
-
@Beh Maybe a setup page for the MM config file,
basically just a script that runs just like the MM page (maybe could be started with npm start config?)
where you could access a list of modules (retrieved from an “official” module list that has the right format),And when the module is selected and “install” is clicked the page does the git clone process, npm install and adds the configuration fields to the config.js file according to the instructions gotten from the module list. (all default settings except for location which the user should select before he is able to install the module).
Since the format of the config for all modules are more or less the same it shouldn’t be that difficult to have the page retrieve the different config variables from the modules and display it in a more userfriendly way (ie input fields on a html page instead of sorting out the “code”).
Because let’s face it, most of the “troubleshooting” for new users are config file related errors (a comma missing or using wrong quotation marks, placing the module code outside the module list etc etc)
Shouch a solution would probably not require a rewrite of any MM base code, it would just be a standalone addition.
But it would require a compatible modules list with a strict format. -
@broberg so whats the difference on what you described to the remote module?
-
@strawberry-3.141 I have no bloody idea, haven’t tried the remote module.
but first off, not remote, second it could fetch a list (database) of modules and execute the git clone commands directly. or is that included in the remote as well?
-
@broberg it is
-
@strawberry-3.141 Great, the code is done! All left is just to include it as a startup page so new users can get started easily as eating a strawberry pie!
