The challenge is to get the most urgently needed campuswide LMS-like apps working well enough for campus-like environments (rather than perfectly in all situations, not possible!)
Typically these server apps fail when accessed over the WAN side of an Internet-in-a-Box, but work well over the LAN side or internal-WiFi of an Internet-in-a-Box.
Many tricks exist to overcome these common failures, e.g.:
- WordPress must be configured from the 1st moment using the correct network — as it locks in all future URL's to that FQDN or IP address, such as http://hogwarts/wordpress or whatever you-as-administrator use during your 1st visit to the site — whereupon http://box/wordpress and others will not work from that point onwards :-(
- Nextcloud also blocks campuswide access in its own way, but this can sometimes (?) be overcome using:
- /etc/apache2/sites-available/nextcloud.conf (commenting out Line 9 (that begins with "Require" was not enough!)
- /opt/nextcloud/config/config.php
- /opt/nextcloud/config/.htaccess
- ETC...PLZ HELP ADD TO THIS LIST !
The challenge is to inventory -> document at http://FAQ.IIAB.IO all these annoying-yet-magical tricks so implementers can work with developers to truly deliver!
The challenge is to get the most urgently needed campuswide LMS-like apps working well enough for campus-like environments (rather than perfectly in all situations, not possible!)
Typically these server apps fail when accessed over the WAN side of an Internet-in-a-Box, but work well over the LAN side or internal-WiFi of an Internet-in-a-Box.
Many tricks exist to overcome these common failures, e.g.:
The challenge is to inventory -> document at http://FAQ.IIAB.IO all these annoying-yet-magical tricks so implementers can work with developers to truly deliver!