silverstripe-framework: Unable to flush manifest from CLI

At the moment manifests are built seperately depending on how (or who) you make requests against projects.

For example GET http://example.com/ will build a manifest inside the cache folder called “unknown”.

using CLI and doing framework/sake / will build a manifest as your current CLI user.

This means it’s not possible to flush frontend template caches via CLI. So automated deployments are a pain because template changes need to be flushed by an HTTP request.

About this issue

  • Original URL
  • State: closed
  • Created 10 years ago
  • Comments: 16 (15 by maintainers)

Most upvoted comments

This is entirely a problem with deployment scripts running as a different user from the web user and the permissions problems related to it. There is nothing that SilverStripe can do here without making the manifest and other caches world writeable, which is a rather bad idea. Simply run your deploy scripts (or that part of it) as the same user that runs PHP.