Rpi with Apache2 PhP nginx webserver newly installed.
I have all files according to the documentation and pointing to my local software repository /var/www/html/arednSoftware
I have followed the documentation https://docs.arednmesh.org/en/latest/arednHow-toGuides/local-software-source.html up until the point where I should run the collect.py script to update the local path.
la9ky@aredn:/var/www/html/arednSoftware $ ls
afs firmware messages releases
la9ky@aredn:/var/www/html/arednSoftware $ ./afs/misc/collect.py . ./afs/www/
write: ./afs/www/config.js
la9ky@aredn:/var/www/html/arednSoftware $
Running the above script it returns "write: .afs/www/config.js" I assume that is correct.
The config.js
In nginx I set the root path by editing the /etc/nginx/sites-available, from the default to the top level directory of the repository, to :
/var/www/html/arednSoftware
But all this does not make it work, if I go to la9ky-aredn.local.mesh/arednSoftware it does not open the index file. That file is in /afs/www/ and for test I pointed my nginx root there and the page for selecting firmware shows up, but nothing is selectable.Running the above script it returns "write: .afs/www/config.js" I assume that is correct.
The config.js
/* exported config */
var config = {
// Show help text for images
show_help: true,
// Path to were overview.json can be found
versions: {},
// Pre-selected version (optional)
default_version: "0.0.0.0",
// Image download URL (optional)
image_url: "http://la9ky-aredn.local.mesh/arednSoftware/",
// Info link URL (optional)
info_url: "https://openwrt.org/start?do=search&id=toh&q={title} @toh",
};
In nginx I set the root path by editing the /etc/nginx/sites-available, from the default to the top level directory of the repository, to :
/var/www/html/arednSoftware
--
I am not experienced, so I can not see the obvious clue here. I could paste more configs here, but I will see if someone can jump in, or if someone could tag a person with knowledge to help me out.
Frank
LA9KY
This deviates from the instructions on the site, but I find nginx is often difficult to work with compared to available alternatives. Caddy is a good one and has a lovely built-in file browser.
For now, I would try stripping out the automation aspect and just work on getting the files manually copied to/served from the desired default directory.
https://caddyserver.com/docs/quick-starts/static-files