{"action":"created","issue":{"url":"https://api.github.com/repos/jarednova/timber/issues/542","labels_url":"https://api.github.com/repos/jarednova/timber/issues/542/labels{/name}","comments_url":"https://api.github.com/repos/jarednova/timber/issues/542/comments","events_url":"https://api.github.com/repos/jarednova/timber/issues/542/events","html_url":"https://github.com/jarednova/timber/issues/542","id":77721672,"number":542,"title":"problems deploying on production environment - executable code in /lib/cache?","user":{"login":"gustavolanzas","id":1471172,"avatar_url":"https://avatars.githubusercontent.com/u/1471172?v=3","gravatar_id":"","url":"https://api.github.com/users/gustavolanzas","html_url":"https://github.com/gustavolanzas","followers_url":"https://api.github.com/users/gustavolanzas/followers","following_url":"https://api.github.com/users/gustavolanzas/following{/other_user}","gists_url":"https://api.github.com/users/gustavolanzas/gists{/gist_id}","starred_url":"https://api.github.com/users/gustavolanzas/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/gustavolanzas/subscriptions","organizations_url":"https://api.github.com/users/gustavolanzas/orgs","repos_url":"https://api.github.com/users/gustavolanzas/repos","events_url":"https://api.github.com/users/gustavolanzas/events{/privacy}","received_events_url":"https://api.github.com/users/gustavolanzas/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-05-18T16:41:19Z","updated_at":"2015-05-26T20:43:16Z","closed_at":null,"body":"Hello, first of all - thanks to Jared and everyone else that has contributed. Timber is amazing. I'm trying to use it to extend a complex Roots theme customization for my company. I have it working beautifully locally, but ran into some issues on our staging and production environments. \r\n\r\nOur production configuration doesn't allow any modifications to the file system outside /wp-content/uploads. Also, any cache folders are skipped from deployment - I am not able to change this policy.\r\n\r\nThere's three executable files inside lib/cache:\r\n-KeyGenerator.php\r\n-TimberKeyGeneratorInterface.php\r\n-WPObjectCacheAdapter.php\r\n\r\nDeploying my timber project results in php errors and KeyGenerator.php not being found, since its inside the cache folder - which can't get copied to production. I don't have filesystem access to production so I can't add it in - but it can't be written into anyways.\r\n\r\nI would really hate to redo all my work to date in porting templates to timber, so any ideas how to work around the above limitations would be appreciated. Can the executable code inside that cache folder be moved somewhere else and the references changed? Can the caching be directed elsewhere? Ideally inside the uploads folder?"},"comment":{"url":"https://api.github.com/repos/jarednova/timber/issues/comments/105659168","html_url":"https://github.com/jarednova/timber/issues/542#issuecomment-105659168","issue_url":"https://api.github.com/repos/jarednova/timber/issues/542","id":105659168,"user":{"login":"gustavolanzas","id":1471172,"avatar_url":"https://avatars.githubusercontent.com/u/1471172?v=3","gravatar_id":"","url":"https://api.github.com/users/gustavolanzas","html_url":"https://github.com/gustavolanzas","followers_url":"https://api.github.com/users/gustavolanzas/followers","following_url":"https://api.github.com/users/gustavolanzas/following{/other_user}","gists_url":"https://api.github.com/users/gustavolanzas/gists{/gist_id}","starred_url":"https://api.github.com/users/gustavolanzas/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/gustavolanzas/subscriptions","organizations_url":"https://api.github.com/users/gustavolanzas/orgs","repos_url":"https://api.github.com/users/gustavolanzas/repos","events_url":"https://api.github.com/users/gustavolanzas/events{/privacy}","received_events_url":"https://api.github.com/users/gustavolanzas/received_events","type":"User","site_admin":false},"created_at":"2015-05-26T20:43:16Z","updated_at":"2015-05-26T20:43:16Z","body":"Well, I figured a workaround for myself that might be useful to anyone else that might run into a similar situation. I renamed the cache directory, and then updated  ~/vendor/composer/autoload_classmap.php to point at the renamed directory. I followed directions elsewhere to redirect the cache to the theme cache folder. Now, everything is working fine."}}