Skip to content

Renaming app directory to 1234 breaks Auth #99

mehlah opened this Issue Aug 29, 2011 · 4 comments

4 participants

mehlah commented Aug 29, 2011

Howdy folks,

I'm opening a ticket while digging deeper, 'cause maybe someone will have a clue faster.

The problem, as I see it

Taken a fresh app and directories layout, and renaming the main app/ directory to 1234 (or any integer), break Auth.

Environment details

I'm using PHP 5.3.6, nginx, and all tests are green


I'm deploying an app using Capistrano and a home made gem for Lithium easy deployments.
Capistrano, by default, creates a directory layout as follows:

[deploy_to]/current -> [deploy_to]/releases/20100819001122

Each time you deploy, a new directory will be created under the “releases” directory, and the new version placed there. Then, the “current” symbolic link will be updated to point to that directory. (For now, don’t worry about the shared directory; we’ll get to that eventually.)

The web server's document root should be set to the [deploy_to]/current directory.

That means, the app/ directory name is a timestamp, which break things right now.

A "maybe" related ticket:

Union of RAD member

This todo might be the cause for the problem you are seeing. Can you verify this, manually by changing those values and/or providing a test case against the session auth adapter?

@gwoo gwoo closed this Sep 9, 2011
Union of RAD member
gwoo commented Sep 9, 2011

set in Session::config()

Union of RAD member

@gwoo: Should Session throw an exception if that happens?

Union of RAD member
gwoo commented Sep 14, 2011

Probably better to change the behavior so it uses a static string like 'lithium-app'.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.