This way, users can modify includes/config.php without git pull or upgrades complaining about local changes. The file config/config.php is copied during the installation to includes/config.php and ignored by Git. The interface itself, default Linux file paths and so on may be changed by modifying the project's configuration file config.php. For this reason, manual edits to this file will not be preserved.īaseline configurations for dhcpcd, dnsmasq (described below) and bridged AP configurations are contained here. Relative to other services managed by the project.
This is due to the complexity of this configuration The exception to this is nf which is managed by includes/hostapd.php and effectively rewritten depending on user input. In this way, the user may modify RaspAP's baseline application settings without touching code. The networking defaults, DNS servers, wireless regulatory data and so on are found here. To every extent possible, RaspAP's default settings are contained within the project's /config folder. While this project handles every facet of this process for you, it's still recommended that users familiarize themselves with the steps involved in building a software AP from start to finish. You will have a functional AP that you may then administer with RaspAP's web interface. When the manual or quick installation is completed, More importantly, it eliminates guesswork that can lead to conflicts down the road. This facilitates a faster setup by not prompting the user for various network RaspAP uses a known-good default configuration as a starting point. Creating a software routed access point (AP) requires the installation and setup of several related Linux services.
0 kommentar(er)
