old one works too (but should not be used anymore)
Read the statement by Michael Teeuw here.
Posts made by karsten13
-
RE: Git Hub requiring username and password
-
RE: Git Hub requiring username and password
tested it, no auth needed:
❯ git clone https://github.com/MagicMirrorOrg/MagicMirror.git Cloning into 'MagicMirror'... remote: Enumerating objects: 26723, done. remote: Counting objects: 100% (112/112), done. remote: Compressing objects: 100% (71/71), done. remote: Total 26723 (delta 53), reused 82 (delta 35), pack-reused 26611 Receiving objects: 100% (26723/26723), 22.56 MiB | 12.26 MiB/s, done. Resolving deltas: 100% (16643/16643), done.
-
RE: Module for MagicMirror forum
the use of a csrf token is restricted to admins (as already mentioned by @bugsounet), there is a hack described here to open this for all users but I don’t think we should do this.
For accessing the read(-only) api you can use a cookie from your browser, e.g.
curl --cookie "express.sid=xxxxxxx" https://forum.magicmirror.builders/api/unread
but this would be challenging to use in a module for mm …
-
RE: Module for MagicMirror forum
some api urls seem to work without authentication, e.g.
❯ curl -s https://forum.magicmirror.builders/api/recent/posts/day | jq -r '.[].topic.title' Default Weather Module Icon Position Module for MagicMirror forum MMM-Formula1 updates MMM-Formula1 updates MMM-Formula1 updates Live phone location Refresh Magic Mirror after custom css changes Module for MagicMirror forum Refresh Magic Mirror after custom css changes MMM-QuotesFromReddit Refresh Magic Mirror after custom css changes
-
RE: MMM-CalendarExt3
@flemmingss said in MMM-CalendarExt3:
The “CX3_Shared” folder is empty
this is the problem which is caused by the strange installation procedure in the used docker image.
The module installation is done via
npm init -y npm install request --save
You have to ask the author of this script why he is doing this.
With this construction the postinstall/postupgrade scripts defined in the
package,json
ofMMM-CalendarExt3
are never called so theCX3_Shared
folder is empty. -
RE: module.js mismatch error and good by os
I think the fetch errors are related to https://github.com/MagicMirrorOrg/MagicMirror/issues/3329
you can try the newest electron version or disable ipv6
-
RE: auto recovery from mirror freeze
maybe the freezing of the client is caused by a restart of the server, e.g. if the server changes the node.
In mm v2.25.0 we implemented an automatic browser reload if the server was restarted, so maybe this helps here (see https://github.com/MagicMirrorOrg/MagicMirror/pull/3188/files)
-
RE: ISS tracker
for this we need a free public api which provides these info’s depending on the position (longitude/latitude), so if you find one …
-
RE: Automatic checking of all MagicMirror² modules
@KristjanESPERANTO said in Automatic checking of all MagicMirror² modules:
@Jalibu wrote:
are there plans to make this the official linked modules store on the project‘s page?
I’m definitely open to the idea of turning it into an official part of the project and moving it to MagicMirrorOrg, for example.
However, I have not yet sought dialogue with the core developers in this regard. It it would be very interesting to hear if the core developers are open to that idea. @karsten13 , @rejas and @sdetweil, what do you think?
I‘d also vote for making this the source of truth without dependency to the old page as a datasource
The current solution (the list in the wiki) works and does not cause any additional work for the core developers.
However, as soon as we automate the process of creating the new module webpage, a vandal could provoke ugly effects. That’s why a different approach to maintaining the list, one that provides more protection against (intentional and unintentional) vandalism and includes a simple quality check, would make sense.
My concrete suggestion would be to create a pull request template for this purpose.
If we decide that “my” list should become an official part of the MM project, I would spontaneously suggest these rough milestones in the following order:
- moving the repository to MagicMirrorOrg.
- finding a better way to maintain the source of truth (currently the wiki page).
- replacing/redirect references to the old module list.
- automating the creation of the module list website.
I’m fine with this. The Wiki stuff should not stay the source of truth, this construction is horrible. Maybe we have to wait until we have full control over MagicMirrorOrg …