# Web Servers: Nginx vs. Apache Multi-PHP lets you choose the right web server for each of your projects or set a global default. --- ## đŸŒŠī¸ Choosing a Web Server You can switch between Nginx and Apache for any of your projects in the **"My Projects"** settings. - **Nginx**: Lightweight, high-performance, and standard for modern web development. - **Apache**: Traditional, robust, and supports native `.htaccess` files for fine-grained configuration. --- ## đŸ› ī¸ Global Configuration Management Each server has its own main configuration file where you can manage ports, worker processes, and global settings. ### Nginx Configuration (`nginx.conf`) - **Test Config**: Use the "Test Configuration" button to verify your changes without restarting the server. - **Save & Reload**: Apply configuration changes instantly. ### Apache Configuration (`httpd.conf`) - **Main Server Settings**: Configure global document roots, module activation, and standard ports. - **HTAccess Support**: When Apache is active, it automatically reads `.htaccess` files in your project folders. --- ## 📁 Shared Server Assets Multi-PHP comes with pre-configured, professional designs for **Index of** (directory listings) and **Error Pages** (404, 500). These are consistent across both Nginx and Apache. > [!WARNING] > Editing global configuration files can prevent your servers from starting. Always use the **"Test Configuration"** tool before applying changes. ### 📖 Next Steps - [Learn how to manage CLI and System Integration](./settings.md) - [System Advanced Tools](./tools.md) - [Troubleshooting Common Issues](./troubleshooting.md)