What:
This updates the default view cache path to storage/frameworks/views.
Why:
Issue #6 - changes in views not reflected in a newly built version of the application, because the build looks at the cached views and not the latest view when building the application. The change in this PR allows cached views to be saved in a space that is readily viewable, and deletable, and when deleted, allows changes to views be reflected in new builds.
View changes are important to be reflected in new builds of the application, because the Dockerfile template is a view. And it is this template that is used by this project to generate a Dockerfile
Closes #6
What: This updates the default view cache path to storage/frameworks/views.
Why: Issue #6 - changes in views not reflected in a newly built version of the application, because the build looks at the cached views and not the latest view when building the application. The change in this PR allows cached views to be saved in a space that is readily viewable, and deletable, and when deleted, allows changes to views be reflected in new builds.
View changes are important to be reflected in new builds of the application, because the Dockerfile template is a view. And it is this template that is used by this project to generate a Dockerfile