Skip to content

Conversation

@nemoinho
Copy link
Contributor

Q A
Bug fix? Yes
New feature? No
BC breaks? No
Deprecations? No
Fixed tickets #575

As described in ticket #575 the cache is not writable after the deployment of symfony if the deployment-user is not the httpd-user. Therefore we would make the cache-directory writable again after the
cache-warmup. This is necessary because symfony may not do that and the deploy user should know who is able to write into the cache. You can finally define this by using set('writable_dirs', […]) and
set('http_user', '…').

As described in ticket #575 the cache is not writable after the
deployment of symfony if the deployment-user is not the httpd-user.
Therefore we would make the cache-directory writable again after the
cache-warmup.  This is necessary because symfony may not do that and the
deploy user should know who is able to write into the cache.  You can
finally define this by using `set('writable_dirs', […])` and
`set('http_user', '…')`.
@antonmedv
Copy link
Member

I think ok. @oanhnn? @deployphp/maintainer ?

@antonmedv antonmedv added the bug label Mar 12, 2016
@sidz
Copy link

sidz commented Mar 23, 2016

I think you don't need to duplicate deploy:writable task. We only needed deploy:writable after 'deploy:cache:warmup'.

I tested and everything is ok.

@antonmedv
Copy link
Member

@nemoinho it's looks like @sidz is right. Can you test it and update PR?

@nemoinho
Copy link
Contributor Author

You are totally right, so I changed the task as suggested.

@antonmedv antonmedv merged commit 67ed8d8 into deployphp:master Mar 24, 2016
@nemoinho nemoinho deleted the feature/fix-cache-access-rights branch March 24, 2016 20:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants