Igor Kromin |   Consultant. Coder. Blogger. Tinkerer. Gamer.

NOTE: This article is 3 years or older so its information may no longer be relevant. Read on at your own discretion! Comments for this article have automatically been locked, refer to the FAQ for more details.
I've started working on a new project that runs on Google's App Engine. I'm using PHP in the standard environment and for my templating engine I've decided on Smarty since that's something I've used in the past and was familiar with. It's not the cool new templating engine like Twig but it gets the job done and can be made to work on App Engine pretty easily.

So to start, the easiest way to get Smarty into your project is to add it to the composer.json file like so:
 composer.json
"require" : {
"smarty/smarty" : "^3.1"
}


Afterwards follow the usual steps for adding a new dependency with Composer. I've written a separate article about that here.

Then create a file called php.ini in your applications directory at the same location as your app.yaml file. Add the following contents to that file:
 php.ini
allow_url_include = "1"
google_app_engine.allow_include_gs_buckets = "#default#"


What the above does is instruct App Engine to allow cached template files to be included in your app from the Cloud DataStore.



In your application code, initialise Smarty like so:
 PHP
$smarty = new \Smarty();
$smarty
->setTemplateDir(__DIR__ . '/templates')
->setConfigDir(__DIR__ . '/templates')
->setCompileDir('gs://#default#/smarty');


The above assumes you have a 'templates' directory with your .tpl files. The compiled templates will be stored in the default bucket in the Cloud DataStore.

Now you can use Smarty as usual.

-i

Skip down to comments...
A quick disclaimer...

Although I put in a great effort into researching all the topics I cover, mistakes can happen. If you spot something out of place, please do let me know.

All content and opinions expressed on this Blog are my own and do not represent the opinions of my employer (Oracle). Use of any information contained in this blog post/article is subject to this disclaimer.
 
comments powered by Disqus
Other posts you may like...