Please have composer available globally in your path.
- Start shell and cd into your localhost's root
- Fire the command
bash -c "$(curl -fsSL http://git.io/AEPfRg)"
- There is no other step, the blog is good to go under your localhost!
How it works
Don't expect too much here. It's all done the easy way!
Some templates are in mustache and are loaded by using a special controller trait. This is true for example for the post-listing template. Please do not ask why, I just want to play around. I learned that there is not use in a templating language without support for inline php as it kinda kills using any external php helpers. Maybe another templating language eludes this issue.
Post-handling, music-listing etc. is all accomplished by using index-files in
*.json-format. They can be found in the index-files directory as their internal folder structure follows the view's folder hierarchy. Loading these index-files or also fairly easy by using yet another controller-trait.
Listing some posts can therefore be done by some code like the following.
Actually, there is not much more to it - apart from the usual lmvc stories.
In Production (pushing to live TLD)
The Git Way
The easiest way is mostly the best, therefore having
git on your remote live system helps to ease the way. Just activate a
post_recieve-hook checking out into the
The hook's code shell-script might look like:
git checkout -f sh /htdocs/scripts/cache.sh clear /htdocs/app
Simply running a
git push origin master would therefore update your running site as needed.
The FTP Way
I recommend having a look at git-ftp for this. A great tool handling all the logic of only uploaded changed files to a specified remote ftp-host.
After installing (
brew install git-ftp) and setting it up simply running
git ftp push would do all the works but will leave you with dirty cache directories. In case you have the stage on the Asset Pipeline in the state-directive at 'prod' which will omitt checking for modified files and therefore aggressively force caching for performance. Leaving it at its default in 'dev' will obviously be a bit more forgiving in that regard.
There's not more to add...