.htaccess

[KevinWaterson]

One of the biggest draw-cards of Slim, has always been that 'it just works out of the box'. The removal of .htaccess prevents even the most basic of routing requests given in the index.php file. This raises the bar for the level of entry into the Slim framework. Whilst old hands will work it out, those new to the framework only see that it is broken, without knowing why.

[geggleto]

:+1: PLEASE FOR ALL THE NOOBS, just so they can copy paste it somewhere else ;)

[silentworks]

Send a PR and will get this re-instated.

[ximex]

:+1:

[rivetchip]

Everything is indicated in the doc on how to use rewriting on different web-servers ;)

[tuupola]

I think it is more of documentation issue. Might be good idea to mention rewrite rules already in installation page. That is the only page most people with problems read.

[KevinWaterson]

This is not a documentation issue. This is a deployment issue. The application no longer works out-of-the-box. Many who use Slim are new to API/PHP and have little to know idea of configuring htaccess or even that it exists. Quite simply, when the application is first installed, it seems to be broken.

[piotr-cz]

This repository is a library (installed into /vendor/slim/slim folder), not a deployable application with a public folder. While one don't have to use composer and can put everything into a public folder, it should be considered is a bad practice. I see no reasons to expose metadata files like composer.json, CONTRIBUTING.md to public access other than to show which architecture that was used to build an app.

But I think that the slimphp organisation should have own Slim v3 skeleton app repository, similar to @akrabats work, like it has for Slim v2

[KevinWaterson]

If it is not a deployable application,  why is there an index.php? Sent from Samsung Mobile

-------- Original message --------

From: Piotr notifications@github.com

Date:21/11/2015 12:19 (GMT+00:00)

To: slimphp/Slim Slim@noreply.github.com

Cc: Kevin Waterson kevin.waterson@gmail.com

Subject: Re: [Slim] .htaccess (#1601)

This repository is a library (installed into /vendor/slim/slim folder), not a deployable application with a public folder. While one don't have to use composer and can put everything into a public folder, it should be considered is a bad practice. I see no reasons to expose metadata files like composer.json, CONTRIBUTING.md to public access other than to show which architecture that was used to build an app. But I think that the slimphp organisation should have own Slim v3 skeleton app repository, similar to @akrabats work, like it has for Slim v2 — Reply to this email directly or view it on GitHub.

[silentworks]

Fixed. You can now find this in a example directory.