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.
