Read the statement by Michael Teeuw here.
Something I'm working on ...
-
Its great. With this, I was thinking is possible create a installer system, its somethings i was thinking from time ago.
Using the API and the parameters of configuration per every module its possible create the section of module for add into the config.js
-
By the way, this project is in a horrible raw early alpha stage … buttt, if someone is interested to contribute, the source code is available here: https://github.com/MichMich/MagicMirror-Website/tree/develop
Be advised: the code needs a lot of refactoring and misses a lot of commenting.
The frontend is a SPA based on Vue.js and a bit of Vuex. The Backend/Api is based on Laravel.
If you clone the repo, take the following steps to get it up and running:
- Run:
composer install
- Run
npm install
- Create an environment configuration:
cp .env.example .env
- Run php artisan key:generate`
- Modify the database and github settings in the
.env
file. (You need to create a github app for testing.) - Run
php artisan migrate --seed
to setup the database.
If you make any changes to
/resources/assets/js
or/resources/assets/sass
, make sure to rungulp
to compile. - Run:
-
@roramirez Installer system is a great idea, however this is something that @strawberry-3-141 will implement as a mobile app, from what I hear plus I am building something like this into my remote control (a website - currently on the develop branch). So maybe have a look at it, before you start something completely new. Although, if there is a good reason for building this again or in a different way, count me in.
-
Very nice, MichMich. I like the integration with github pulling almost all data and as such removing the need to enter description and all that over and over again. I added my modules
-
Thanks @MichMich the information. I will take a look of code :)
Hi @Jopyth , do you know where I can find some code or design about the @strawberry-3-141 app?
I think we can bootstrap a app for install apps (modules) into a MagicMirror with API provider by modules section of web. The idea it’s most like a packages manager + configuration.
-
If you work on such an installer. Make sure it’s based on the module infrastructure where possible. That we you can develop and test is, without the need of directly integrating it in mm2. If It’s fully up and running and tested, we can integrate it by adding it to the list of default modules.
-
@MichMich I noticed that format of table markdown is not optimal. The rows should be alternating color. A good example that current format is bad is here: http://beta.magicmirror.builders/module/29/motioneye. Notice that it’s difficult to see what configuration value belongs to which description…
-
Hey,
another problem with tables:if you use html-tables in your GitHub README.md it’s not displayed the right way.
Example: http://beta.magicmirror.builders/module/33/soccerlivescore -
It is only an idea. In Wordpress the themes have all the same style at the beginning in the css file for the declaration of the theme:
/*
Theme Name: Tutorial
Theme URI: http://wordpress.lernenhoch2.de
Description: Template zum WordPress Tutorial auf http://wordpress.lernenhoch2.de
Author: Christian Strang
Author URI: http://lernenhoch2.de
*/https://codex.wordpress.org/Theme_Development#Theme_Stylesheet
maybe it is something for you to use?
-
@LukeCodewalker It seems the html is malformed and thus the markdown parser in unable to parse it correctly. It looks like the table contains white lines which are not allowed. If you run your markdown thru a markdown linter, you’ll see there is an issue with the markdown of that readme file.