We have custom build of OpenWRT with specific functions for same remote devices based on ARM. Now we try extend OpenWisp functions: - "heartbeat" detailed status info of devices (almost done) - simple packet management - firmware upgrade Last two functions need from openwisp only delivery functions. I've researched work of config-archive generation and how upgrade/update work on client side. I noticed if we could add any file to archive (hypothetically) then openwisp-config can place even binary files at needed place and then our client-side cron script will do other actions.
2018-03-28 0:14 GMT+05:00 Federico Capoano <[email protected]>: > The OpenWISP backend contains logic that is needed for backward > compatibility with the old legacy version of OpenWISP Firmware (which was a > heavily customised OpenWRT based firmware). > > The generic file functionality in the OpenWRT backend allows you to add > any file you need. If you could specify what you are trying to accomplish > maybe I could point you in the right direction. > > I'm haven't understood what you are trying to do, nor I have understood > what do you mean for "client-side scripts". > If you help me understand you better I may be able to give more detailed > answers. > > Fed > > On Tue, Mar 27, 2018 at 1:34 PM Артур Скок <[email protected]> wrote: > >> Federico, thanks for reply. >> I've researched this manual earlier, but this one about >> creating/modifying plain files. But, as i undestood it, script >> netjsonconfig/backends/openwisp/openwisp.py contains logic for >> operations on specified files ts_script, install, etc: execution, >> installing, schedule tasks. >> But i did not find suitable logic in client-side scripts. >> >> 2018-03-27 21:22 GMT+05:00 Federico Capoano <[email protected]>: >> >>> You can add any file/script in the OpenWRT backend by using the "files" >>> section. >>> >>> Read this section: http://netjsonconfig.openwisp.org/en/stable/ >>> backends/openwrt.html#including-additional-files >>> >>> I hope it helps. >>> >>> Fed >>> >>> On Mon, Mar 26, 2018 at 2:57 AM BlancLoup <[email protected]> wrote: >>> >>>> Hello. How scripts generating for client side works? >>>> I found that openwisp backend module >>>> (netjsonconfig/backends/openwisp/openwisp.py) >>>> can generate special files for client: install.sh, uninstall.sh, >>>> ts_script.sh and has additional workaround for crontab files. But i cannot >>>> find any processing of these on clientside in openwisp-config scripts. Is >>>> these all for future implementations? >>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "OpenWISP" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to [email protected]. >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "OpenWISP" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "OpenWISP" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/d/optout. >> > -- > You received this message because you are subscribed to the Google Groups > "OpenWISP" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "OpenWISP" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
