Home » , » Latest Release - Zend Server 8 AMIs Updated Version

Latest Release - Zend Server 8 AMIs Updated Version

jaki watson | 02:42 | 0 comments
Zend Framework Development India
Zend team is happy to announce the latest release of an updated Zend Server 8 AMIs on the AWS marketplace. In the last version, users can easily control different parameters of the new instance by using JSON in userdata and are capable to automated tasks be to implemented during the boot process.

In this latest version, users can have a collection of latest features like:

  • Capability to specify a preparation script in user data to be downloaded and executed before Zend Server customization
  • Ability to choose a Zend Server Launch profile (development or production) using user data
  • Refined deployment using user data – new deployment parameters that enable specifying the path for a deployed application and multiple applications deployment

Launch Profile

User can have an alternation to select between production profiles and development. Previously, when we were specified the Zend Server admin password in JSON, Zend Server was launched by default along with production profile. However, now, we are allowing you to choose a launch profile when starting instance using the new ZEND_BOOTSTRAP_PRODUCTION parameter to explicitly.

ZEND_BOOTSTRAP_PRODUCTION (bool) – Check out whether Zend Server should be bootstrapped for production (true) or development (false). See below given example of using this parameter.

{
"ZEND_ADMIN_PASSWORD": "1234",
"ZEND_BOOTSTRAP_PRODUCTION": true
}

Preparation Script

In the last release, we have seen a customization script that enable to personalize a server after the deployment of applications. Here, we have learned that customization should be performed before application deployment.

The installation of a local MySQL server is needed when deploying a development environment. Moreover, MySQL requires to be installed before deployment of the web application. For such purpose, we have added two new parameters such as:

  • ZEND_PRE_SCRIPT_PATH (string) – It is an absolute path, where custom preparation script should be placed. One can have to save the script in the directory with filename extracted from URL, if the path is a directory. A re-downloaded script will overwrite this file after a reboot.

  • ZEND_PRE_SCRIPT_URL (string) – Here, the URL from which custom preparation script should be downloaded and executed.

Check out the example given by using this parameter:

{
"ZEND_ADMIN_PASSWORD": "1234",
"ZEND_BOOTSTRAP_PRODUCTION": false,
"ZEND_PRE_SCRIPT_URL": "https://s3.amazonaws.com/some-bucket/some.script",
"ZEND_PRE_SCRIPT_PATH": "/tmp/prepare.sh"
}

Multiple Deployments

In the last release, the Automatic Deployment is featured. However, in this release, we have upgraded it by following different deployments to various paths. One new parameter is added:

ZEND_DEPLOYMENTS (array) – Array in which each item is considered as an object, describing a deployment that will be done after Zend Server starts. Below given is a list of possible keys for objects:

  • prefix (string) – possible for “s3″ deployment. Specifies which directory in S3 bucket should be downloaded.
  • path (string) – needed for all deployments and specifies into which path web application should be deployed. To deploy application to root, specify “/”.
  • type (string) – needed and must be one of “git”, “s3″ or “zpk”.
  • relativeRoot (string) – optional for “git” and “s3″ deployments. If specified, indicates which folder inside a deployment should be document root (or in case application is not deployed to root, which directory should be aliased in apache).
  • url (string) – needed for “git” and “zpk” deployments. Specifies URL from which git repository or ZPK file should be downloaded.
  • name (string) – needed for “zpk” deployment. Name of application that will appear in Zend Server UI after deployment.
  • params (array) – required for “zpk” deployment. Array of additional parameters that is passed to Zend Server during ZPK deployment. Keys of this array are names of parameters and respective values are values of parameters. Parameter values are scanned for string $IP and if it is found, then it is replaced with external IP of instance. This is useful, for example, when deploying WordPress application.
  • buket (string) –needed for “s3″ deployment. Specifies from which S3 bucket application should be downloaded.
{
"ZEND_ADMIN_PASSWORD": "1234",
"ZEND_BOOTSTRAP_PRODUCTION": false,
"ZEND_DEPLOYMENTS": [
{
"type": "git",
"url": "https://github.com/zendframework/ZendSkeletonApplication.git",
"path": "/"
},
{
"type": "git",
"url": "https://github.com/zendframework/ZendSkeletonApplication.git",
"path": "/demo",
"relativeRoot": "public"
},
{
"type": "git",
"url": "https://github.com/zendframework/ZendSkeletonApplication.git",
"path": "/demo2",
"relativeRoot": "public"
}
]
}

It is expected that you will like the new Zend Server on AWS AMIs. Using these new features, you will surely set up Zend Server with ease and can enable to deploy application as well.

If you are thinking to hire PHP Zend Developer for your project then Contact Perception System, a PHP Zend Framework Development Company In India.
Share this article :

0 comments:

Post a Comment

 
Design by: