pub/setup missing in 0.1.0-alpha103

[Vinai]

If the magento2/pub/ directory is set as the webserver document root, installation via browser fails because a redirect loop to /setup/.

The problem is there is no setup directory within /pub/.
As a result the browser request is rewritten to pub/index.php again, which in turn triggers another redirect response to /setup/.
This finally results in a endless redirect loop.

For reference please see

\Magento\Framework\App\Http::redirectToSetup()
\Magento\Framework\App\Http::getInstallerRedirectPath()
and there $urlPath = self::NOT_INSTALLED_URL_PATH;

[alankent]

I don't have specific details, but one aspect is we are trying to make "setup" separate from the "store front" (/frontend). Right now the recommendation is to use the command line install process (not web access). The web front end will be available, but I don't think its 100% stable yet.

If you look at the new root README.md file (https://github.com/magento/magento2/blob/master/README.md) it contains the recommended installation process for Magento 2 (at least for now!).

[Vinai]

Making the setup a separate application is great, and using the setup/index.php cli script works like a charm.
The current redirect loop in /pub/ isn't a big deal, just a little surprising, especially if folks are used to Magento 1.

If the application detects the setup needs to be executed, I think it should check if the /setup/ path is present before redirecting there to avoid the redirect loop.
It could check if the document root is set to /pub/, or simply check if /setup/ is not present.
In that case a informative message would be more appropriate then the redirect.

Setting the document root to match the magento root, the regular setup is callable but seems to be broken currently once the actuall installation starts.

Thanks for the pointer to the README, there actually is a lot of useful information in there!

[safwkhan]

Thanks for bringing up this issue, Vinai. We have recorded this one as an issue to look at.

[antonmakarenko]

We have fixed the issue and the fix is on the way to next weekly release. Now, if setup wizard is unavailable from current document root, it will not attempt to redirect, but throw an exception indicating this. In default mode, such an error results in displaying HTTP 503 crash page with "error report". In dev mode, it will just display the exception as plaintext.

[tanya-soroka]

@Vinai thank you for reporting the issue.
It has already been resolved and available in the 0.1.0-alpha108+ release.