Application Deployment         By Shrikant Lokhande             Exclusive For SBS. © 2012 Shrikant Lokhande All rights res...
1. Proper skeleton using Capistrano remote deployment.     Directory Structure as follows:     myapp/releases           |_...
2. Proper Permission.   Files and Folders
3. Backend processConfiguration And Management.
4. SEO optimization.     Check which URLs feeds are  submitted to webmaster.http://devgrow.com/quick-seo-tip-set-preferred...
5. Source code under Git    (Version Control).    Maintained Branches as per    release.http://philsturgeon.co.uk/blog/201...
6. Source code should be Clean.(Do not push any unused file/folders inthat)
7. Rewrite Rules / URLs
8. Should be use oops Languages like:  Python, Ruby, Jruby, Java for  Frontend and Backend forapplication scalability.
9. Always use and work on   cutting edge technology.
10. If using Check        Framework/API/Library/Plugins        versions for Application.
11. Simple and quicksetup.
12. Check Efficiency and        Scalability.   # NewRelic ?http://newrelic.com/php
13. Stress testing with using   testing tools Like: Apache benchmark(ab)
14. Check the performancetool. i.e. yslow and firebug.http://developer.yahoo.com/performance/rules.html
15. Images should lightweight forserving. Create in .PNG format fromdesigner.http://www.codinghorror.com/blog/2007/03/gett...
16.CDN setup and update DNS records for   serving only static content.http://www.codinghorror.com/blog/2007/03/using-amazo...
17. Exception notification for    Application.
18. No hard coding please.
19. Bug/Testing resolvedependency.
20. Error Pages. ( If the linksbroken)      use 404 for not found.      if break URLS redirect tohome      path.
21. Only one DB and SMTP configfile     for each application.Do not add DB connection and SMTP in any .php file.
22. We all should know andfollow     the Agile Development.http://en.wikipedia.org/wiki/Agile_software_development
23. After production deployment willnot    change any things manually.       If we found it should to update itwill       ...
24. Enable Error Logs and AccessLogs    for Application
25. Add SSL for site if there is any   account activity done.
26. Understanding of software    designing.
27. Good in estimation.
28. Involved in code review andcheck coding stranded. With PM,Dev, Operation Team.
29. Contribution towards    performance, stability andoperation    of the app
30. Strategy:    Start       1. create revision and functionality for therelease.       2. List the changes and To dos in ...
31. Production deploy only onweekdays Tuesday or Wednesday, soeveryone in office. Starting Time: 10:00 Am End Time : 5:00 ...
Planning2 Shrikant Lokhande
Proper Planning and discussion.  All should be on same page.
If site down should showMaintenance page on website.
Continuous Integration and Proper  development and deployment
Do major services optimization.  Httpd, mysql, if any other.
Database side optimization.    Do plan which database is   suitable for our application.                  e.g.pgsql,nosql,...
Database Slow query optimization.    Make it to faster to them.
Master-master, Master-slave, Multi      master environment.
Mail server configuration.    All set with mail server        prospective.
Work on critical task.
Proper server management by server admin only. There will no any kind     of access for developers.
Backup and Restoration plan and        management.      AWS S3, NFS. Volume,   Snapshot, Backup Directory.
The good comes not from thecode or the features,but process standardization.
Upcoming SlideShare
Loading in …5
×

Application depolyment

250 views

Published on

Published in: Health & Medicine, Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
250
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
5
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • *
  • *
  • *
  • *
  • *
  • *
  • *
  • *
  • *
  • *
  • *
  • *
  • *
  • *
  • *
  • *
  • *
  • *
  • *
  • *
  • *
  • *
  • *
  • *
  • *
  • *
  • *
  • *
  • *
  • *
  • *
  • *
  • Application depolyment

    1. 1. Application Deployment By Shrikant Lokhande Exclusive For SBS. © 2012 Shrikant Lokhande All rights reserved.
    2. 2. 1. Proper skeleton using Capistrano remote deployment. Directory Structure as follows: myapp/releases |_ 20081019001122 20081019001123 myapp/current -> releases/20081019001122 # Sym link current. myapp/shared |_ images config |_ config.php myapp/system |_maintenance.html
    3. 3. 2. Proper Permission. Files and Folders
    4. 4. 3. Backend processConfiguration And Management.
    5. 5. 4. SEO optimization. Check which URLs feeds are submitted to webmaster.http://devgrow.com/quick-seo-tip-set-preferred-domain-in-google-webmaster-tools/
    6. 6. 5. Source code under Git (Version Control). Maintained Branches as per release.http://philsturgeon.co.uk/blog/2010/02/Deploying-websites-with-Git
    7. 7. 6. Source code should be Clean.(Do not push any unused file/folders inthat)
    8. 8. 7. Rewrite Rules / URLs
    9. 9. 8. Should be use oops Languages like: Python, Ruby, Jruby, Java for Frontend and Backend forapplication scalability.
    10. 10. 9. Always use and work on cutting edge technology.
    11. 11. 10. If using Check Framework/API/Library/Plugins versions for Application.
    12. 12. 11. Simple and quicksetup.
    13. 13. 12. Check Efficiency and Scalability. # NewRelic ?http://newrelic.com/php
    14. 14. 13. Stress testing with using testing tools Like: Apache benchmark(ab)
    15. 15. 14. Check the performancetool. i.e. yslow and firebug.http://developer.yahoo.com/performance/rules.html
    16. 16. 15. Images should lightweight forserving. Create in .PNG format fromdesigner.http://www.codinghorror.com/blog/2007/03/getting-the-most-out-of-png.html
    17. 17. 16.CDN setup and update DNS records for serving only static content.http://www.codinghorror.com/blog/2007/03/using-amazon-s3-as-an-image-hosting-service.html
    18. 18. 17. Exception notification for Application.
    19. 19. 18. No hard coding please.
    20. 20. 19. Bug/Testing resolvedependency.
    21. 21. 20. Error Pages. ( If the linksbroken) use 404 for not found. if break URLS redirect tohome path.
    22. 22. 21. Only one DB and SMTP configfile for each application.Do not add DB connection and SMTP in any .php file.
    23. 23. 22. We all should know andfollow the Agile Development.http://en.wikipedia.org/wiki/Agile_software_development
    24. 24. 23. After production deployment willnot change any things manually. If we found it should to update itwill go in next release.
    25. 25. 24. Enable Error Logs and AccessLogs for Application
    26. 26. 25. Add SSL for site if there is any account activity done.
    27. 27. 26. Understanding of software designing.
    28. 28. 27. Good in estimation.
    29. 29. 28. Involved in code review andcheck coding stranded. With PM,Dev, Operation Team.
    30. 30. 29. Contribution towards performance, stability andoperation of the app
    31. 31. 30. Strategy: Start 1. create revision and functionality for therelease. 2. List the changes and To dos in revision. 3. Updates on local/staging 4. Testing and Bug fix. 5. Push to production. End.
    32. 32. 31. Production deploy only onweekdays Tuesday or Wednesday, soeveryone in office. Starting Time: 10:00 Am End Time : 5:00 PM #After thatwill stop deployment.
    33. 33. Planning2 Shrikant Lokhande
    34. 34. Proper Planning and discussion. All should be on same page.
    35. 35. If site down should showMaintenance page on website.
    36. 36. Continuous Integration and Proper development and deployment
    37. 37. Do major services optimization. Httpd, mysql, if any other.
    38. 38. Database side optimization. Do plan which database is suitable for our application. e.g.pgsql,nosql,mongodb,mysql,percona,tok yo cabinet
    39. 39. Database Slow query optimization. Make it to faster to them.
    40. 40. Master-master, Master-slave, Multi master environment.
    41. 41. Mail server configuration. All set with mail server prospective.
    42. 42. Work on critical task.
    43. 43. Proper server management by server admin only. There will no any kind of access for developers.
    44. 44. Backup and Restoration plan and management. AWS S3, NFS. Volume, Snapshot, Backup Directory.
    45. 45. The good comes not from thecode or the features,but process standardization.

    ×