Releases: GladysAssistant/Gladys
Releases · GladysAssistant/Gladys
v3.7.4
3.7.4
v3.7.3
3.7.3
v3.7.2
3.7.2
v3.7.1
3.7.1
v3.7.0
3.7.0
v3.6.3
3.6.3
v3.6.2
3.6.2
v3.5.2
3.5.2
Gladys 2.1.6
- This version update md5 package and change bcrypt to bcryptjs ( bcryptjs does not need compilation, and we only sign into Gladys like 1 time per week so we don't need the extra performance of native bcrypt implementation )
- It's now possible to set a roomID to a LifeEvent. That mean that we can say "This event took place in this room". This offers new possibilities : Saving a temperature of a room, a humidity value at a given time, or any new "state" of a room. Incredible ! :)
- This version add a footer in the dashboard with the version of Gladys, and links to the website & Gladys Github, thanks to @VonOx pull request
- This version avoid flooding GitHub with refresh of LifeEvents in development mode. Now, Gladys only update LifeEvents in production mode at startup (if you restart gladys 10 times in 2 minutes when developing and each time it syncs with Github, you are losing time and flooding Github )
Loading hooks services in sandboxed scripts
Hooks services are now loaded in scripts ! It means that you can use in your scripts your favorites module's services :)
Important
Introducing gladys global variable.
Gladys is an event emitter, replacing sails.config.Event, now deprecated ( but still included )
If you want to test when Gladys is ready, you now have to do :
gladys.on('sailsReady', function(){
});
Be careful, many people still have old Gladys, so in your modules, 3 possibilities :
- Keep old sails.config.Event
- Test if gladys variable exist, if not give it sails.config.Event value
- Ask people in your installation guide to update Gladys to version >= 2.1.4 before installing your module