Explore creating scalable PHP web applications, structuring code efficiently, managing data storage, and implementing automated testing to ensure robustness and maintainability in real-world projects.

docker.tar.gz

Serve /usercode

Run index.php (quiet composer install)

Serve /usercode (quiet composer install)

execute_apcu

This course is for people who have already learned the basics of PHP (or just finished the "Learn PHP from Scratch" course) and want the bigger picture of making big web applications with this language.

First, you'll learn how all PHP web applications communicate with the world and how to turn multiple source code files into one application. Then you'll learn multiple approaches to structuring the whole application. It will help you write code that's easy to maintain. Also, this is a common topic for job interview questions.

Next, you'll learn different data storage methods, from user sessions to databases. This course doesn't duplicate the official documentation but instead provides an overview of the various tools you can use. You'll learn how to use them in PHP, their tradeoffs, and how to pick what's best for your project.

Finally, you'll learn how to make automated tests for your project to ensure that it works as expected.

Developing Web Applications with PHP

The Composer autoloader is a critical piece of code that changes global PHP behavior. Which command should you use to include it?


The Composer autoloader is a critical piece of code that changes global PHP behavior. Which command should you use to include it?

What should be the file path for class `\App\Foo\Bar` if you follow PSR-4 and configure the namespace prefix `App` to match the `src/` directory`?


What should be the file path for class <code>\App\Foo\Bar</code> if you follow PSR-4 and configure the namespace prefix <code>App</code> to match the <code>src/</code> directory`?

What features does Composer provide?

Should the `composer.json` file be committed  to Git?


Should the <code>composer.json</code> file be committed to Git?

Should the `composer.lock` file be committed to Git?


Should the <code>composer.lock</code> file be committed to Git?

Should the `vendor` directory be committed to Git?


Should the <code>vendor</code> directory be committed to Git?

We can skip installing them in the production environment.


What makes `require-dev` dependencies different from `require` dependencies?


What makes <code>require-dev</code> dependencies different from <code>require</code> dependencies?

You maintain a library and follow semantic versioning. You notice that one of the functions in public API is broken by design, so you remove it.

What should be the new library version if the current version is `1.2.3?`

You maintain a library and follow semantic versioning. You notice that one of the functions in public API is broken by design, so you remove it.
What should be the new library version if the current version is <code>1.2.3?</code>

If you need to install a library with a minimum version of `1.2.3 `and update it automatically while the major version number stays the same, what version constraints can you use?


If you need to install a library with a minimum version of <code>1.2.3 </code>and update it automatically while the major version number stays the same, what version constraints can you use?

What's best to configure as a website root directory in the HTTP server?


What’s best to configure as a website root directory in the HTTP server?

Introduction

Communicating with the Client

Static Web Application

Structuring Code Files

Application Architecture Basics

PHP-Based Web Application

Storing State

Databases

Using a Database in the PHP Application

Testing

Testing the PHP Application

Advanced Architecture Patterns

Final Assessment

Conclusion

Quiz: Structuring Code Files