Gain insights into modern PHP by delving into POST requests, forms, sessions, and redirects to build a CRUD app with authentication, focusing on pure PHP without frameworks.

Learn PHP Without a Framework by Matthias Noback.png

php-setup.tar.gz

php-job

php-favi

php-pub

php-public

php-error

php-mult

php-tests

PHP for the Web is a terrific introduction on how to use modern PHP effectively. While there is a lot of material out there about building applications with PHP, most of them focus on using a framework like Laravel or Symfony. By working with pure PHP, you will be able to focus on the core ideas instead of how a particular framework implements them.

In this course, you will learn how to use multiple web technologies like POST requests, forms, sessions, and redirects to build a CRUD application with an authentication system.

By the end, you will have all the ingredients at your disposal to go out and build stunning, dynamic PHP web applications.

PHP for the Web: Learn PHP without a Framework

## Purpose of routing
Another important concept that needs to be discussed  before we move on to the next chapter is routing. We will be discussing it because of the following two concerns:

1. We have `.php` in every page URL, which does not look great. A URL that looks like `/pictures` instead of `/pictures.php` needs to be used.
2. The URL of a page is tied to its file name, which does not give us flexibility.  A URL that looks like `/random-number`, which shows the output of the `random.php` script, needs to be used. We also want to be able to rename that file, while the URL stays the same and vice versa ( we should be able to change the URL without changing the name of the script).

Once all of this is possible, we can move the page scripts out of `public/` because they no longer need to be publicly accessible.
Instead, we will have one *entry point* for the PHP server, the `index.php` file, which will inspect the URL of a request and include the right PHP script.


# Purpose of routing
Another important concept that needs to be discussed  before we move on to the next chapter is routing. We will be discussing it because of the following two concerns:

1. We have `.php` in every page URL, which does not look great. A URL that looks like `/pictures` instead of `/pictures.php` needs to be used.
2. The URL of a page is tied to its file name, which does not give us flexibility.  A URL that looks like `/random-number`, which shows the output of the `random.php` script, needs to be used. We also want to be able to rename that file, while the URL stays the same and vice versa ( we should be able to change the URL without changing the name of the script).

Once all of this is possible, we can move the page scripts out of `public/` because they no longer need to be publicly accessible.
Instead, we will have one *entry point* for the PHP server, the `index.php` file, which will inspect the URL of a request and include the right PHP script.


Getting Started

Serving Resources

Serving PHP Scripts

Forms

Cookies

Sessions

Authentication

PHP Project Structure

CRUD Part 1: Create

CRUD Part 2: The Rest

File Uploads

Error Handling

Automated Testing

Conclusion

Routing: Mapping URLs

Purpose of routing