We have moved at community.getvera.com

Author Topic: openLuup: dev folder  (Read 614 times)

Offline vosmont

  • Beta Testers
  • Hero Member
  • *****
  • Posts: 687
  • Karma: +60/-8
openLuup: dev folder
« on: May 13, 2016, 05:19:57 am »

is it possible, as "/etc/cmh-lu", to have a folder dedicated for development (e.g. "/etc/cmh-ludev") ?

It will help to identify the files of a plugin in development.
(There's just 3 minor changes in "init.lua", "loader.lua" and "server.lua")

Offline akbooer

  • Moderator
  • Master Member
  • *****
  • Posts: 6387
  • Karma: +292/-70
  • "Less is more"
Re: openLuup: dev folder
« Reply #1 on: May 13, 2016, 05:30:27 am »
Well, it's certainly possible.  Indeed, it sounds like you've done it already.

My personal approach has been to use /cmh-ludl for development and have everything else in /cmh-lu, however it's not ideal, since an AltUI update will put all its files into /cmh-ludl again, because the presence of /cmh-lu is optional.

It's also not a perfect solution, since, alas, several plugins, your own included (?) actually play with reading and writing device files in /cmh-ludl.  The modifications you suggested above won't address that problem.

Further thoughts anyone?
3x Vera Lite-UI5/Edge-UI7, 25x Fibaro, 23x TKB, 9x MiniMote, 2x NorthQ Power, 2x Netatmo, 1x Foscam FI9831P, 9x Philips Hue,
Razberry, MySensors Arduino, HomeWave, AltUI, AltHue, DataYours, Grafana, openLuup, ZWay, ZeroBrane Studio.