BENEFITS OF WORKING LOCALLY
Developing locally is considered a best practice. In general, you do not want to be actively
developing on a live production website because you could have visitors accessing the site at
any time and development involves iterations of breaking code and making it work again. This
is not the experience you want to provide to your visitors.
Why So Much Process?
Now that you have a basic understanding of the workflow, let’s circle back to why a developer
should take these extra steps on the path to code deployment.
First, as explained earlier, developing locally allows the developer to test and try things without
breaking the live website. Truly, this can be one of the most important aspects of this system.
The second benefit is privacy. Developing locally means your project is only available on your local.
Think about the prerequisites for WordPress, and then make a shopping list of the components you
need for WordPress. WordPress is a web application. That means you need a web server. WordPress
runs on PHP, a programming language for the web. That means your web server must support PHP.
Apache is a good (and very popular) general‐purpose web server that supports PHP, although there
are many others that will work as well, including Microsoft IIS or Nginx. With WordPress version
4.1, the minimum version of PHP that is required is version 5.2.4. Ideally, you would like a web
server that supports URL rewriting to make your permalinks work. Apache has a module calledmod _ rewrite to make this work.
WordPress also needs a database to store the content of the site. WordPress only supports MySQL
for the database and, as of version 3.2, the MySQL version must be 5.0 or greater. In addition, your
PHP must have the appropriate MySQL libraries to make the database connection. Finally, you will
also want a client to manage your database.
Developing locally is considered a best practice. In general, you do not want to be actively
developing on a live production website because you could have visitors accessing the site at
any time and development involves iterations of breaking code and making it work again. This
is not the experience you want to provide to your visitors.
Why So Much Process?
Now that you have a basic understanding of the workflow, let’s circle back to why a developer
should take these extra steps on the path to code deployment.
First, as explained earlier, developing locally allows the developer to test and try things without
breaking the live website. Truly, this can be one of the most important aspects of this system.
The second benefit is privacy. Developing locally means your project is only available on your local.
TOOLS FOR COMPONENT ADMINISTRATION
Think about the prerequisites for WordPress, and then make a shopping list of the components you
need for WordPress. WordPress is a web application. That means you need a web server. WordPress
runs on PHP, a programming language for the web. That means your web server must support PHP.
Apache is a good (and very popular) general‐purpose web server that supports PHP, although there
are many others that will work as well, including Microsoft IIS or Nginx. With WordPress version
4.1, the minimum version of PHP that is required is version 5.2.4. Ideally, you would like a web
server that supports URL rewriting to make your permalinks work. Apache has a module calledmod _ rewrite to make this work.
WordPress also needs a database to store the content of the site. WordPress only supports MySQL
for the database and, as of version 3.2, the MySQL version must be 5.0 or greater. In addition, your
PHP must have the appropriate MySQL libraries to make the database connection. Finally, you will
also want a client to manage your database.
INSTALL WordPress Locally
download apache and install on your pc. Create a database in MySQl with phpmyadmn. Download and install wordpress.
Comments
Post a Comment