Better explanation on Symlinks configuration #9

Closed
dclowd9901 opened this Issue Apr 19, 2012 · 3 comments

Comments

Projects
None yet
2 participants
@dclowd9901

Item 6 in your Gotchas page notes:

To make your app Live, make a symbolic link from your webroot to the current folder like this:

ln -s /[deploy here]/current/webroot /var/www/html/[sitename]

In my setup, /srv/www/showhopping.com/app/webroot, /srv/www/showhopping.com/ uses .htaccess to point to (successively) /app, then /webroot. This is, what I feel, a very common setup for cake applications. The suggestion seems to be that I have another folder residing elsewhere on the server that my Name Server points to, and that, in turn, symlinks to /current/webroot/, is that correct?

If it is, can it be written more explicitly, since this is outside the norm for Cake applications?

@jadb

This comment has been minimized.

Show comment Hide comment
@jadb

jadb Apr 19, 2012

Owner

dclowd9901, I can how this can be mis-leading.

The deployment setup depends on how you repo looks like.

Capcake, out of the box, is configured to deploy a repo that looks like this:

Config/
Console/
Controller/
...

Basically, only the content of the app folder. That is because cake's core is deployed separately (during setup) in /shared/ outside of current.

I have a feeling that your application's repository looks like:

app/
lib/
plugins/
vendors/
...

In which case, you can't really rely on the wiki.

Owner

jadb commented Apr 19, 2012

dclowd9901, I can how this can be mis-leading.

The deployment setup depends on how you repo looks like.

Capcake, out of the box, is configured to deploy a repo that looks like this:

Config/
Console/
Controller/
...

Basically, only the content of the app folder. That is because cake's core is deployed separately (during setup) in /shared/ outside of current.

I have a feeling that your application's repository looks like:

app/
lib/
plugins/
vendors/
...

In which case, you can't really rely on the wiki.

@dclowd9901

This comment has been minimized.

Show comment Hide comment
@dclowd9901

dclowd9901 Apr 19, 2012

I just wanted to clarify that the repo is based in /app: http://i.imgur.com/u2Q6r.png

It sounds like I should just tweak the current folder structure to accommodate pointing to the /current folder, so I'll do that. I don't use the capcake cakephp deployment because I'm maintaining my 1.3 version I'm currently utilizing.

I just wanted to clarify that the repo is based in /app: http://i.imgur.com/u2Q6r.png

It sounds like I should just tweak the current folder structure to accommodate pointing to the /current folder, so I'll do that. I don't use the capcake cakephp deployment because I'm maintaining my 1.3 version I'm currently utilizing.

@jadb

This comment has been minimized.

Show comment Hide comment
@jadb

jadb Apr 19, 2012

Owner

Ok - in that case, it's pretty simple.

In deploy.rb, deploy_to should be /srv/www/showshopping.com/current.

And your webserver (i.e. apache configuration) should point to /srv/www/showshopping.com/current/webroot.

Owner

jadb commented Apr 19, 2012

Ok - in that case, it's pretty simple.

In deploy.rb, deploy_to should be /srv/www/showshopping.com/current.

And your webserver (i.e. apache configuration) should point to /srv/www/showshopping.com/current/webroot.

@jadb jadb closed this Jan 29, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment