Last updated: July 2, 2019

inLeague Beta (Summer 2019) Announcement

As part of a years-long architectural update, inLeague is launching a short-term public beta for some production league systems to facilitate the replacement of 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 requires small-to-medium updates to nearly every piece of code.

Does this mean that our inLeague site has two sets of data?

No – all inLeague instances are connected to live, production data and a message on the login page will indicate this. Changes made on one site will impact the other, with the exception of control panel changes (e.g. 'current season') – these changes require the inLeague application to be reset, and so will not "take" between the regular and beta instances for up to a day unless the change is made in both places. 

The best way to use the beta site is to do everything you would ordinarily do on the live site but use the beta URL instead. 

Who should use the beta site and where should they send comments or feedback?

Administrators, registrars, and any board members that are comfortable doing so. You do not need to be technically savvy to use the beta site. Feedback can go to our support address: support@inleague.io

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. Nevertheless, because these changes touch every corner of the software, we would rather have our power users kick the tires for a few weeks. Based on our previous experience, the bulk of the issues that users will encounter can be fixed rapidly, but as with any major system change, there will be some interruptions. Our goal is to get these out of the way during July of 2019 prior to the start of the Fall 2019 season.

What should beta 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. 

How do I access the beta site?
Region #LeagueBeta URL
20Santa Monica AYSOhttps://beta.inleague.ayso20.org
76Beverly Hills AYSOhttps://ayso76.inleague.io
223Mt Diablo AYSOhttps://inleague-beta.mdsoccer.org
300Western Springs / AYSO Region 300https://beta.ayso300team.org
362Glenview AYSO (currently inactive)https://beta.inleague.glenviewayso.org
473Brooklyn AYSOhttps://beta.brooklynayso.net
611West Side Soccer Leaguehttps://wssl-beta.inleague.io
What if my league isn't listed? 

The initial beta rollout does not include every league. Since the beta system is run in parallel with the live, legacy site, we have provisioned separate hardware and need to balance the load against the desire for a larger testing pool. If you would like to participate, please contact inLeague Support.

Are there any changes in functionality between the production and beta sites, or is it all "under the hood"?

There are several changes, including some new features. The new features are documented below under "Version 3.0.0". 

Version 3.0.0: Summer 2019 ("Lucee") Update (Beta Only)

Version 2.3.0: Spring 2019 Update

Version 2.2.1: Fall 2018 Update

Version 2.2.0: Spring 2018 Update

Version 2.1.3: Fall 2017 Update

Version 2.1.2: Summer 2017 Update

Version 2.1.1: Spring 2017 Update

Version 2.1.0: Fall 2016 Update 

Version 2.0.2: Spring 2016 Update

Version 2.0.1: Fall 2015 Update 

Version 2.0: Fall 2015 (inLeague 'NEXT' / inLeague USWNT Edition)


Version 1.3.2 Spring 2015 Update

Version 1.3.1 Fall 2014 Update

Version 1.3.0 Winter 2013/2014 Update

Version 1.2.9 Fall 2013 Update

Version 1.2.8 Summer 2013 Update

Version 1.2.7 Winter 2012/2013 Update

Version 1.2.6 Fall 2012 Update

Version 1.2.5 Summer 2012 Update 2

Version 1.2.4 Summer 2012 Update 1

Version 1.2.3 Spring 2012 Update

Version 1.2.2 Winter 2011/2012 Update

Version 1.2.1: Fall 2011 Update

Version 1.2.0: Summer 2011 Update

Version 1.1.9: Spring 2011 Update

Version 1.1.8: Winter 2010/2011 Update

Version 1.1.7: Fall 2010 Update

Version 1.1.6: Summer 2010 Update

Version 1.1.5: April/May 2010 update

Version 1.1.4: February 2010 Update

Version 1.1.3: January 2010 Update

Version 1.1.2: September/October 2009 Update

Version 1.1.1: August 2009 Update

Version: 1.1.0: July 2009 Update

Version 1.0.9: June 2009 Update

Version 1.0.8: May 2009 Update

Version 1.0.7: April 2009 Update

Version 1.0.6: March 2009 Update

Version 1.0.5: November/December 2008 Update

Version 1.0.4: October 2008 Update

Version 1.0.3: August 2008 Update

Version 1.0.2.: July 2008 Update

Version 1.0.1: June 2008 Update

Version 1.0 Release: May 2008

Before 1.0: Before May 2008, the inLeague system was known as 'AYSO-Online'. 'Version 1.0' refers to a near-complete rewrite that was done on the older system. The 'AYSO-Online' system was in use and under active development from 2002 until 2008.