Changelog

Recoded toybox application N01A.  This application is dependent on population JSON files originally generated by eLMS.  Deployment of internal application N01 will at the time when the eLMS codebase is migrated to N01.  

Recoded toybox application N01B.  

Recoded Drupal pages in N01 in order to accept toybox applications.  

N01 still needs a theme.  N01 contingent on full eLMS conversion.

Recoded toybox source code for LPFM.APP. 

Did a full migration of the Drupal site FMtranslator.com to Sys40.

Did a full migration of lpfm.wiki to Sys40.

Drupal preparation for lpfm.app.

Drupal preparation for wide-fm.com.

Drupal preparation for internal application N01.

Recoded the API for CountyWAR as well as ran some initial testing on the game.  Despite yesterday's update, we plan to commence CountyWAR Game #11 on its normal schedule.  

Recoded and staged in a test environment, the System40 version of LPFM.US.   The DNS cut over will be delayed until the weekend of 10/5~10/6, 2024.   The data source will remain in Legacy for now.

Transitioned dingers to work completely off of Sys40 data.  Dingers will remain in a freeze on new data until after the full transition is completed as FCCdata still depends on dingers data that resides on Legacy.

Moved over several database tables that are needed for the morning run applications.

Reduced operations today due to family priority.

Repaired a post-transition issue with the interface that receives reports of payments from PayPal.

Developed a new function and process that will permit programs to write updates to both the Legacy and Sys40 databases simultaneously.  This opens some potential new flexibility including possibly allowing us to cut over databases with very minimal outage time and address some of the issues we were concerned about for eLMS dual operation. 

Transitioned 21 more tables.

Updated CDBS database on System40 with the data from the last FCC CDBS data release on January 10, 2024.

Recoded a program that checks the latest LMS raw data for new application versions that were not processed by eLMS in order to assign an RECid to that application. This program will not be transitioned until later in the project.

At this time, we are reconsidering our transition strategy for the database including when to cut databases over to Sys40 and the eventual cut over of eLMS and the web applications.  

Installed LMS into the System40 data environment. 

Modified programs that are used to read LMS raw data to write changes to the REC database.

Set up morning update scripts for weekdays, Saturdays and Sundays.  Added the LMS updater into that script.  Other items will be added later.

Complete rewrite of the process and programs used to update Mexico broadcast data (AM, FM and TV). The new programs automate many of the steps in the process we use to retrieve this data from the IFT, parse it and present it.  While recent system changes at the IFT still make this a manual process in one way, we have automated the rest and reduced the need to run 6 programs down to 2.  The new programs also substantially reduce the number of calls made to FCC resources for FM and TV during these updates.

Migrated and deployed internal system N10.

Converted three perl command line scripts into a single PHP script to support the updating of frequency schedules from the High Frequency Coordination Committee (HFCC) to support the display of frequency and language schedules for domestic international broadcast stations in FCCdata.  The new script reduces the updating process from 5 steps to 2 steps.

Updated table mexico.mex_folios to include new columns:

Deleted and restarted certificate for mylpfm.com.  

Modified DNS and migrated files of the main recnet.net domain to System40.

Transitioned University of North Texas display for FCC Record.  

Repaired FMMAP. 

Recoded and transitioned internal application N12.

Recoded and transitioned internal application N11.

Recoded and transitioned MX Window Mapper (used by FWATS for showing MX application relations).

Updated September 21, 2024 6:15 AM EDT

As a part of the REC System40 transition project, there will be work that will be performed during the weekend of September 21 & 22, 2024 which may disrupt the user experience.

Established a new third-level domain calls.recnet.com.  Copied the code from recnet.net/calls to this new virtual server directory.  Placed redirects on both legacy and Sys40 to the new site.  This is a part of the System40 objective to remove public facing applications from recnet.net in favor of recnet.com. 

Upon reconsideration, we will be transitioning recnet.net API endpoints to api.recnet.net.  The recnet.net/api endpoints will be depreciated and eventually removed with the change of the recnet.net domain to System40.

As a part of REC's System40 Project, we have migrated the REC Spare Callsign List application from the current legacy server to the new System40 server.  

A part of the project plan is to migrate public facing services that are on the recnet.net domain to recnet.com.  

With this, we are making the following URL change:

NOTE: Going forward, you may see items referenced as "Internal App" with an identifier.  These are for applications and sites that are used internally by REC and do not have general public access.

Recoded, transitioned and reset certificates for the web UI related command line scripts for the functionality used to define, build and make visible, the log files used by Playout ONE Pro  for Delmarva FM & FM Riverton.  Changes were made to Playout ONE File Copy to reflect the new location of generated log files. 

In preparation for the next major phase (recnet.net services), we have identified all of the various directories, files and subdomains that are associated with recnet.net services and have developed a project plan for the disposition of each of those resources. 

The plan is that all human usable functions will be transitioned over to the recnet.com domain with redirects from the current recnet.net URL.  

recnet.net will be used mainly for utility purposes, machine to machine (API) and future data offerings.