Write php deploy everywhere tek11
3 likes3,083 views
The document discusses using Phing, an XML-based build tool written in PHP, to automate the deployment of PHP applications to various platforms including Linux, Windows, and Windows Azure. It provides examples of using Phing tasks to export code from version control, deploy via SCP, FTP, or cloud services, and set up continuous integration and continuous deployment workflows. The key message is that Phing allows for easy, automated deployment of PHP code to any environment.
Write php deploy everywhere tek11
- 1. Write PHP, deploy anywhere Tek 11 - Chicago, IL (USA)
- 2. m a I’ p e r v e lo D e
- 3. I write code
- 5. Just want to run code
- 8. Live Hacking
- 10. FTP deploy
- 12. Version control
- 13. Code management
- 15. Symlink switch old path/to/webapp path/to/webapp-1.0.2 -> path/to/webapp path/to/webapp-1.0.3
- 16. Symlink switch new path/to/webapp path/to/webapp-1.0.2 path/to/webapp-1.0.3 -> path/to/webapp
- 18. Concept: build • required steps •- to “build” an application validate - test - document - package
- 19. PHP provides the tools!
- 20. Phing •- build tool written in PHP comparable to ANT - but written in PHP :-) • impressive list of task templates • extensible for missing tasks
- 21. Phing HelloWorld! <?xml version="1.0" encoding="UTF-8"?> <project name="demo" default="build"> <target name="build"> <echo msg="Hello World!"/> </target> </project>
- 23. Export from SVN <property name="buildpath" value="./build"/> <property name="repopath" value="https://svn.myserver.com/demo/trunk"/> <target name="prepare"> <delete dir="${buildpath}" includeemptydirs="true" quiet="true" verbose="false" failonerror="false" /> <mkdir dir="${buildpath}"/> </target> <target name="getsources" depends="prepare"> <svnexport svnpath="/usr/bin/svn" force="true" nocache="true" repositoryurl="${repopath}" todir="${buildpath}"/> </target>
- 25. Deployment targets • scp • rsync • ftp •- VCM deployments cvs - svn - git - …
- 28. Where to deploy to? • bare metal servers •- virtual servers even cloud instances • any OS (Windows, OSX, Linux, i5, …)
- 29. Linux server
- 30. Example deploy Linux <target name="deploy-linux"> <exec dir="./build" command="rsync -ruq [email protected]:/srv/www/demo"/> </target>
- 32. Windows server
- 33. Deploy to windows <target name="deploy-windows" depends="version-bugfix"> <ftpdeploy host="${env.win-prod}" port="21" username="${auth.win-prod.username}" password="${auth.win-prod.password}" dir="/" mode="binary" clearfirst="false"> <fileset dir="."> <exclude=”./library/Zend”/> <exclude=”./library/ZendX”/> </fileset> </ftpdeploy> </target>
- 34. Deploy to S3 <target name="deploy-windows" depends="version-bugfix"> <ftpdeploy host="${env.win-prod}" port="21" username="${auth.win-prod.username}" password="${auth.win-prod.password}" dir="/" mode="binary" clearfirst="false"> <fileset dir="."> <exclude=”./library/Zend”/> <exclude=”./library/ZendX”/> </fileset> </ftpdeploy> </target>
- 35. Windows Azure
- 36. A few remarks •- runs only on windows but still uses phing :-) • takes a considerable time to upload • instances are defined in the config
- 37. Setting properties <property name="cmd-cspack" value="c:Program FilesWindows Azure SDKv1.3bin cspack.exe" override="false"/> <property name="cmd-csrun" value="c:Program FilesWindows Azure SDKv1.3bin csrun.exe" override="false"/>
- 38. Prepare for Azure <target name="prepare-azure" depends="version-bugfix"> <!-- start building in ./bldtmp --> <mkdir dir="./bldtmp" /> <copy todir="./bldtmp" overwrite="true"> <fileset dir="./deploy/azure"> <include name="**/*.*" /> </fileset> </copy> <copy todir="./bldtmp/PhpOnAzure.Web" overwrite="true"> <fileset dir="."> <include name="**/*"/> <include name="*"/> </fileset> </copy> </target>
- 39. Deploy to Azure <target name="deploy-azure" depends="prepare-azure"> <exec command=""${cmd-cspack}" ServiceDefinition.csdef / role:PhpOnAzure.Web;PhpOnAzure.Web /out:PhpAzure.cspkg" dir="./bldtmp" /> <mkdir dir="./release/${phing.project.name}-$ {version.number}/azure-prod" /> <copy todir="./release/${phing.project.name}-$ {version.number}/azure-prod" overwrite="true"> <fileset dir="./bldtmp"> <include name="PhpOnAzure.cspkg"/> <include name="ServiceConfiguration.cscfg"/> </fileset> </copy> </target>
- 45. With CI • always “ready to deploy” codebase • feedback on quality • documentation • more …
- 46. Considerations
- 47. Some reminders •- design your apps to work everywhere use OOP abstraction layers - use plugins - take care of sessions! • investigate “the other platform” - gives you a head start over competetion - teaches you the caveats • “cloud” solutions are in high-demand - see what works best for your customer
- 48. automate what you might forget under stress!
- 51. Conclusion
- 52. 1. deployment is simple 2. automate the steps 3. deploy to any platform
- 53. Thank you • source code: http://github.com/DragonBe/zftest • your rating: http://joind.in/3438 •- follow me: twitter: @DragonBe - facebook: DragonBe Please use joind.in for feedback