On this page, we will go into the various project elements, describe them and provide current status.
Revised 08/30/2024 11:30PM EDT
Underlying build | Building the necessary software that will be needed for the operation of the system. | 100% |
Drupal 10 install. | Install Drupal 10 core, determine theme and install necessary modules. | 100% |
Drupal 10 (RECnet.com) | Adding RECnet.com to Drupal 10 multisite. | 100% |
Interim database connection | Establish an interim database connection between System 40 and the legacy database. | 100% |
Drupal 10 (RECnet.com) repair | Determining aspects of Durpal 10 that did not properly import from Drupal 7 and facilitating fixes to implement as many features as possible from the previous Drupal 7 build. | 95% |
PHP8 database interaction | Construct functions that will be used by REC to interact with the database. | 100% |
Development Standards | Develop standards for re-coding all PHP scripts to be compatible with PHP8 | 100% |
Toybox application conversion | Modify the source code in Toybox applications (those that reside on the recnet.com Drupal 10 server) to work with PHP 8 and System 40 Development Standards. This also includes the import and creation of any required elements not previously moved over. | 100% |
GIS server | Move GIS services, DNS and certificates to Sys40. | 100% |
Icecast | Establish Icecast server and perform operational testing. | 100% |
Icecast transition | Transition authorized Icecast clients to the new server. (NOTE: REC does not provide streaming services to the general public. There are other choices out there such as Aiir and Cirrus Streaming.) | 100% |
Perl retirement - phase 1 | Identify all internal back-end applications that were written in perl for conversion to PHP 8. | 50% |
Lime Survey | Install Lime Survey in the System 40 environment. | 0% |
Prepare Drupal 10 | Conduct final testing on the recnet.com and prepare to cut over. | 98% |
Deploy Drupal 10 | Redefine recnet.com DNS and certificates to transition CMS traffic to System 40. | 100% |
Legacy Drupal 7 availability. | Establish new domain (legacy.recnet.com) to continue to point to the legacy. Until 100% | 100% |
Obsolete content | Identify web folders with obsolete content which will not be carried over to Sys40. | 100% |
Copy website content | Copy all website content from Legacy to Sys40 except for Drupal. | 90% |
Relay servers | Set relay servers to receive requests from Sys40. (Relay servers are how we talk to the FCC public systems.) | 100% |
Legacy server audit | Review Apache configuration files on legacy to identify obsolete records and plan for overall site map for Sys40. | 80% |
recnet.net recoding | Update the recnet.net apps (public apps include the spare call sign list) to be compatible with the PHP8 and the new database procedures. | 0% |
recnet.net cutover | Set DNS and certificates for recnet.net services to Sys40 | 0% |
FCCdata test environment | Prepare test environment for FCCdata on Sys40 | 0% |
FCCdata development | Recode FCCdata for PHP8 procedures | 0% |
FCCdata cutover | Set DNS and certificates for FCCdata.org services to Sys40. | 0% |
FCC.today | ||
LPFM.us | ||
myLPFM.com | ||
J1 API services | 90% | |
Delmarva FM/FM Riverton schedule services | ||
Client A (private services) | ||
Drupal 10 conversions for fmtranslator.com and wide-fm.com | ||
Conversion of remaining perl back-end products to PHP 8 (REC and J1 sides) | ||
Conversion of PHP5 back-end applications (except eLMS parse and bot) to PHP8 code. | ||
Set advisory on the FCC message page to prepare for increased eLMS usage for a temporary period. | ||
Conversion of eLMS parse and bot code to PHP8. | ||
Identify databases and tables with static data. | ||
Install databases and tables with static data on Sys40. | ||
Declare a system outage across the REC universe. With the data frozen, copy the dynamic data to Sys40's SQL database. | ||
Deploy eLMS bot and eLMS parse on Sys40. Change schedule to 6 minute headway (12 minutes from each server) for a temporary period. | ||
Enable cron updates on Sys40 in parallel with Legacy. | ||
Declare weekend outage for FCCdata. Transition FCCdata to Sys40's database. Validate results. If validated, reopen FCCdata wiith Sys40 data, otherwise roll back to Legacy. | ||
Validate that all dynamic data is properly being handled in Sys40 SQL. | ||
Declare complete weekend outage. Change all database source from migrated applications from Legacy to Sys40. | ||
LPFM.app. Move this application to Sys40 unless 90 days has lapsed between today and the final LPFM points decision. If all 90 day windows are over, LPFM.app would have reached mission competion and can be retired. If premature, install LPFM-app (a Drupal based site) to Sys40. | ||
Identify files on the Legacy server that, while not published, may have historical significance. Preserve them through copy to System 40 | ||
Shut down SQL services on Legacy | ||
Verify one last time that no historically valuable has been left behind. | ||
Conduct additional final tests on Sys40. | ||
Retire Legacy. | ||
Move RadioDNS, LPFM Wiki and other public facing applications to Sys40. | ||
Complete System40 project | ||
ALL AGENDA ITEMS AND THE ORDER OF THE SUB-PROJECTS THEY MAY BE HANDLED IN MAY BE DIFFERENT THAT WHAT IS ABOVE. |