Security Checklist/Testing and Development
From Joomla! Documentation
< Security Checklist(Difference between revisions)
Dextercowley (Talk | contribs) (add link to eclipse setup instructions) |
m (update navigational call) |
||
| (12 intermediate revisions by 5 users not shown) | |||
| Line 1: | Line 1: | ||
| − | {{ | + | {{:Security Checklist/TOC}} |
| − | + | ||
== Secure Testing and Development == | == Secure Testing and Development == | ||
| Line 10: | Line 9: | ||
===Use a versioning system=== | ===Use a versioning system=== | ||
| − | : Be able to roll back to an earlier version of your site using a modern version control system, such as CVS, [http://subversion.tigris.org/ Subversion], or [http://git.or.cz/ git].</li> | + | : Be able to roll back to an earlier version of your site using a modern version control system, such as CVS, [http://subversion.tigris.org/ Subversion], or [http://git.or.cz/ git].</li> The Eclipse IDE indicated above includes a Subversion plugin. This allows you to work with the Joomla! source repository as well as other projects hosted on [http://joomlacode.org/ JoomlaCode]. |
| + | |||
===More suggested tools=== | ===More suggested tools=== | ||
: Check out the Joomla! community's list of popular [http://forum.joomla.org/index.php/topic,25307.0.html Developer Software and Tools]. | : Check out the Joomla! community's list of popular [http://forum.joomla.org/index.php/topic,25307.0.html Developer Software and Tools]. | ||
| − | == | + | ==Setup a backup process first== |
| − | : | + | ===The most important rule=== |
| + | : '''Thou shalt at all time be able to return your site to a previous working state through regular use of a strong, off-site backup and recovery process. ''' | ||
| + | |||
| + | : Be sure your backup and recovery process is ready and tested BEFORE your site goes live. | ||
| + | |||
| + | : This is the single best way (and often the only way) to recover from such inevitable catastrophes as:''' | ||
| + | |||
| + | # A compromised/cracked site. | ||
| + | # Broken site due to a faulty upgrade. | ||
| + | # Hardware failure, such as dead hard drives, power failures, server theft, etc. | ||
| + | # Authoritarian government intervention. (More common than some think.) | ||
| + | # Needing to quickly relocate to a new server or hosting provider. | ||
<!-- KEEP THIS AT THE END OF THE PAGE --> | <!-- KEEP THIS AT THE END OF THE PAGE --> | ||
[[Category:Security Checklist]] | [[Category:Security Checklist]] | ||
Latest revision as of 20:00, 15 October 2012
| |||||||||||||
[edit] Secure Testing and Development
[edit] Develop locally, deploy globally
- Develop and test your site on a local machine first. Installing Joomla locally is not as hard as it may sound, and the exercise will greatly boost your confidence.
[edit] Use an IDE
- Consider using an Integrated Development Environment (IDE). One free IDE that many Joomla! developers use is Eclipse. See Setting up your workstation for Eclipse development for instructions on installing Eclipse.
[edit] Use a versioning system
- Be able to roll back to an earlier version of your site using a modern version control system, such as CVS, Subversion, or git. The Eclipse IDE indicated above includes a Subversion plugin. This allows you to work with the Joomla! source repository as well as other projects hosted on JoomlaCode.
[edit] More suggested tools
- Check out the Joomla! community's list of popular Developer Software and Tools.
[edit] Setup a backup process first
[edit] The most important rule
- Thou shalt at all time be able to return your site to a previous working state through regular use of a strong, off-site backup and recovery process.
- Be sure your backup and recovery process is ready and tested BEFORE your site goes live.
- This is the single best way (and often the only way) to recover from such inevitable catastrophes as:
- A compromised/cracked site.
- Broken site due to a faulty upgrade.
- Hardware failure, such as dead hard drives, power failures, server theft, etc.
- Authoritarian government intervention. (More common than some think.)
- Needing to quickly relocate to a new server or hosting provider.
