It does also create a self-signed certificate for nginx and redirect http traffic to https by default. Note that even when using nginx, exposing the LuCI interface to the Internet or guest networks is not recommended.
Currently LuCI on nginx is fully supported maybe only in master snapshots for now, as of Feb If any problem is found, report them to the support forum. LUCI works fine but you'll need some manual configuration. Also this setup is not widely used and tested. Download the following packages from the package repository using your platform and release version:. Or use this script bellow. Note, the script assumes you have internet access through the router where you are installing LuCI.
If you do not, then you will need to either manually download required. First part till the last done statement to be executed when connected to the internet:. Show pagesource Old revisions Backlinks Back to top. Basic installation 2. Providing encryption 3. Native language support 4. Additional web applications 5.
LuCI essentials. Managing configurations. Managing packages. Managing services. Install the required packages. You need to install one of this 2 variants of the LuCI meta-package: luci-nginx - Autoinstall nginx, uwsgi-cgi and the default config file to make luci work on nginx.
Thanks for your guide. I was able to build my first OpenWrt image flawlessly at very first try. I feel it must be quite easy but I only start to understand building process. Removing LuCI is easy, just don't select it in the first place. Getting rid of uci is harder, either learn to live with it or rewrite the init scripts to suit your needs.
The developers put pretty much thought into the init scripts and uci integration, it's hard to just replace that. You have to redo the firewall, hotplug handling, wireless configuration, network config and switch setup. Many packages won't be compatible anymore etc. Good luck with that. Jow, thank you for your reply. I think I have to live with uci till I gain more experience with building images.
Hi, Seems there isnt carl I have just successfully built OpenWRT backfire I want to edit network. I assume they are built from some source files but don't know which ones.
I have browsed the web and found no positive results. I won't try to port the kexec-tools to mips on my own, but if somebody can point me to a patchset, that is claimed to actually work, then i'll happily apply it.
It doesn't make sense to me to have an option M in Menuconfig. The compiled package isn't going to go anywhere useful to the router, and you're likely then to download, install and configure the module s from the internet via the OPKG utility anyway. OK, I suppose you could be sourcing the packages locally, in which you would need them compiled, but I am sure not many of us are doing that. However, I am stuck at the very first step of it.
Updating '. Create index file '. Last edited by Yanira on 11 Aug , Thanks for writing this little HowTo! Yanira you state to build the luci stuff in "y", but the instructions I followed from the wiki say to build them as modules? M makes no sense here as they won't get included in the image then. So then everything listed as a Module should be changed?
Last edited by CyrusFF on 9 Oct , Thanks for your guide Yanira I have compiled successfully the 8. If feeds. Thanks for the guide, it is working quite well for me. Hello Yanira, Thanks for your guide.
0コメント