Write php deploy everywhere
7 likes6,022 views
The document is a presentation by Michelangelo van Dam discussing various deployment strategies for PHP applications at ConFoo 2011 in Montreal. It covers topics such as automated deployment using tools like Phing, deployment to different platforms (Windows, Linux, Azure), and continuous integration practices. Key considerations include designing applications for compatibility, leveraging OOP abstraction, and the demand for cloud solutions.
Write php deploy everywhere
- 1. Write PHP, deploy everywhere Confoo 2011, Montreal (CA)
- 2. Michelangelo van Dam • Independent Consultant • Zend Certified Engineer (ZCE) • President of PHPBenelux
- 3. Topics Live hacking FTP deploy Version control Automated deployment Anywhere deployment
- 4. Related
- 5. Rob Allen Stress Free Deployment http://www.flickr.com/photos/stuartherbert/5089882125 http://akrabat.com/talks/#sfd
- 7. Live Hacking
- 9. FTP deploy
- 11. Version control
- 12. Code management
- 14. Symlink switch old path/to/webapp path/to/webapp-1.0.2 -> path/to/webapp path/to/webapp-1.0.3
- 15. Symlink switch new path/to/webapp path/to/webapp-1.0.2 path/to/webapp-1.0.3 -> path/to/webapp
- 17. Concept: build • required steps •- to “build” an application validate - test - document - package
- 19. Phing • build tool written in PHP • comparable to ANT build scripts • impressive list of task templates • extensible for missing tasks
- 20. Phing HelloWorld! <?xml version="1.0" encoding="UTF-8"?> <project name="demo" default="build"> <target name="build"> <echo msg="Hello World!"/> </target> </project>
- 22. 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>
- 26. Deployment options • platform (windows, linux, i5, …) • database engine (mysql, ms sql, oracle) •- deployment protocols rsync - FTP
- 27. Linux server
- 28. Example deploy Linux <target name="deploy-linux"> <exec dir="./build" command="rsync -rq [email protected]:/srv/www/ demo"/> </target>
- 30. Windows server
- 31. 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>
- 32. Windows Azure
- 33. A few remarks •- runs only on windows but still uses phing :-) • takes a considerable time to upload • instances are defined in the config
- 34. 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"/>
- 35. 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>
- 36. 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>
- 41. Considerations
- 42. 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
- 43. automate what you might forget under stress!
- 45. Questions • http://slideshare.net/DragonBe/write-php-deply- everywhere • http://twitter.com/DragonBe • http://facebook.com/DragonBe • http://joind.in/2782
Editor's Notes
- #2: \n
- #3: \n
- #4: \n
- #5: \n
- #6: \n
- #7: \n
- #8: \n
- #9: manual modifying on server\nno return to previous\nfailures visible\n\n
- #10: \n
- #11: local files &#x201C;out-of-sync&#x201D;\noverwriting code of others\nno previous version\n
- #12: \n
- #13: all go to a central (or decentral) repository\ncode is versioned\nwhen failure, you can revert\n
- #14: snapshot tag -> deployment package\n
- #15: \n
- #16: \n
- #17: \n
- #18: \n
- #19: \n
- #20: \n
- #21: \n
- #22: \n
- #23: \n
- #24: \n
- #25: \n
- #26: \n
- #27: \n
- #28: \n
- #29: \n
- #30: \n
- #31: \n
- #32: \n
- #33: \n
- #34: \n
- #35: WA SDK: http://msdn.microsoft.com/en-us/windowsazure\n
- #36: \n
- #37: first create a package with 2 instances\nthan deploy to azure\n
- #38: \n
- #39: WA Manager\n- two instances\n
- #40: \n
- #41: perfect world\n
- #42: \n
- #43: layers: db, services\nplugins: caching solutions -> OS detection\n
- #44: when your boss asks you to deploy quickly\n- you might forget steps\ncomputers are good at doing repeated tasks\n- use that!\n
- #45: if you&#x2019;re interested in cloud deployment\n- phpa - Feb 2011 issue\n
- #46: \n