Last updated: July 23October 22, 2019
inLeague Architecture Update (Summer 2019) Announcement
As part of a years-long architectural update, the development team at inLeague replaced the back-end software "engine" that runs the inLeague application. Some of the background for this change is described in more detail in our Founder's Blog (item #3); the short explanation is that inLeague is retiring the Adobe server software that has been in place since 2003 in favor of a more modern, open-source alternative that runs much of the same code. This is the largest single change to inLeague's technology stack in the company's history and required small-to-medium updates to nearly every piece of code.
The following regions have completed the transition to our new infrastructure:
...
Why are you making this change?
Our theme for 2019 is borrowed from part of a keynote address presented by inLeague's chief architect in April: "Modernize or die." These changes will enable inLeague's development team to build better software without destroying the development investment that our regions and our team have made over the past fifteen years. In addition to better development practices, our new software engine also enables better deployment practices, allowing us to take advantage of modern, cloud infrastructure in areas like caching and API development.
Will this change be disruptive?
inLeague (the company) has been through this process with other applications prior to undertaking the update to inLeague (the software) and the bulk of the transition is already complete. inLeague conducted a public beta test for most of July 2019 in parallel with the legacy architecture. Nevertheless, because these changes touch every corner of the software, some disruption is likely. Based on our previous experience, the bulk of the issues that users will encounter can be fixed rapidly.
What should users look out for?
Unexpected behavior. Crashes will be reported to inLeague automatically. Be on the lookout for functions that don't crash but don't perform in the manner you would expect: for instance, if you make a change to a user, a player, a game, or a roster assignment, and some or all of the changes do not persist.
Are there any changes in functionality between the old system and the new one, or is it all "under the hood"?
...
Version 3.1.0: Fall 2019 ("Invoices") Update
- Merchant Services: Added support for Authorize.net Payment Gateways.
- Invoicing System: All-new system for invoice templating, assignment, payment plans, and responsive, mobile-friendly email receipts.
- Volunteer Points Assignment: Re-written points assignment tool with new competition-level option to restrict volunteer points to teams with players from the volunteer's family.
- Referee Scheduler: Updated display for referee self-scheduler and administrator views to use space more efficiently and improved mobile device responsiveness.
- Referee Statistics: Display date of non-game credits (e.g. clinics) on statistics page
- Referee Statistics: Group teams by division.
- Game Scheduler: Added option to bulk-change game fields and a confirmation box when bulk-deleting games.
- System Log: Improved load times for master system log displays with very large numbers of log entries.
- Volunteer Queue: Added a 'check underway' status visible in the volunteer queue and the report center to reflect volunteers who have completed their Sterling background check orders but whose results have not yet been adjudicated.
- AYSOU Login Sync: Added AYSOU Login button to family profile to re-synchronize login credentials with AYSO.
Version 3.0.0: Summer 2019 ("Lucee") Update
...