Hi Matteo and welcome, On Monday, September 17, 2018 at 11:55:21 AM UTC+2, matteo fedeli wrote: > > Hi at all, > > by reading this tutorial (https://github.com/openwisp/ansible-openwisp2) > I don't understand how can I do to install and configure the "Production > Server". Instead the "local machine" need only to complete the installation > of production server? > ansible-openwisp2 is basically a deploy script. You launch it from a laptop, workstation or a continuous integration server like jenkins or gitlab, we refer to these as the "local machine". The script targets another machine, usually a server, which in the tutorial we refer to as the "production server".
You need to install ansible on your local machine, create the playbook file and the inventory file (a filed called hosts). Ensure you correctly configure authentication so the SSH agent can authenticate successfully into the production server. Regarding the access point, what the difference between the explanation on > the documentation ( > http://openwisp.io/docs/user/configure-device.html#install-openwisp-config-on-your-openwrt-instance) > > and the luci-openwisp? (https://github.com/openwisp/luci-openwisp). With > luci I resetted the ap because the login page redirected to a blank page... > > Regarding how to connect OpenWRT to OpenWISP, refer to this page: http://openwisp.io/docs/user/configure-device.html Luci-openwisp is used for a different purpose, as written in its README: *The goal of this project is to provide a limited web interface for LEDE / OpenWRT so that users can configure only the bare minimum in order for their device to connect to the OpenWISP 2 Controller.* *Use this web interface only if you have a similar use case, otherwise you should keep the default LEDE / OpenWRT interface (luci-mod-admin-full).* Luci-openwisp is useful if you want to preinstall your firmware on devices, then give the device to somebody who is in charge of placing it into a building or on a rooftop and they only need to configure a couple of things, nothing more. I don't think this is your use case. > Finally, one more question, The web Interface about server allow to edit > everything type of configuration or something by terminal or code? > I don't understand this last question well. I'll try to reply anyway according to my interpretation. The web interface of OpenWISP allows you to change the configuration of the devices and/or prepare configuration templates for recurring configurations. The web-interface allows a limited set of configuration options to be defined, but you can still go into advanced mode and overcome this limit, so with OpenWISP you can potentially prepare any type of configuration which is supported by OpenWRT and one of its packages. Check the videos on our website to see some examples <http://openwisp.org/whatis.html#openwrt-controller>. I hope this helps! Federico -- 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.
