Yesterday I downloaded the new Agile Toolkit 4.3 and found that the licensing and subscription model has been changed. Additionally a "developer sandbox" has been included which launches when the toolkit is first run and requires me to login with a registered account.
While I understand the reasons for these changes, and I'm fully supportive, the sandbox appears to be unnecessarily restrictive. However, there seems to be no easy way to bypass the sandbox, and logging in to the sandbox in a vanilla install of 4.3 leads to a screen where you are forced to choose between a pre-canned Admin or Frontend site.
The key reason for me to upgrade from 4.2 to 4.3 is the introduction of an Application class to support RESTful services. I have no need for either an Admin, nor a Frontend web user interface and yet the sandbox does not provide this option.
Is it possible to bypass the sandbox setup process and, if so, how would one go about doing this?
Looking at this in a different way, the folder structure of the ATK4 library seems to have changed under 4.3. Version 4.2 included documentation on the folder structure and how a developer should setup their application in relation to that structure. I have been unable to find corresponding documentation for Version 4.3 which would give clear guidance on how to build an application around the toolkit without relying on the included sandbox.
Hi Tim (i'm author of Agile Toolkit)
Agile Toolkit framework will continue to be available on github. You will find link to github on the bottom of the page, simply select branch 4.3. All of the documentation still applies and you can use the framework (you still need to respect the license). Github does not contain "admin" or "frontend", it is included for the convenience of new users.
The licensing terms has slightly changed, Agile Toolkit has always used AGPL and Commercial licensing. The reason to introduce the sandbox is because developers were not respecting the license terms. I also wanted to give easier ability to deploy projects for new PHP developers and for security it can only be done through sandbox.
Here is a blog-post outlining all of the changes: http://www4.agiletoolkit.org/blog/rebooting-agile-toolkit
The folder structure have changed, but it must still be compatible with the 4.2 branch. I've adopted the usage of "public" folders for improved security, but please do look into PathFinder documentation on how to customise folder structure.