![]() In general, the closer your development environment matches your production environment, the fewer environment/deployment related issues you'll have. You can research more on your own if you'd like The PHP group's code word for Windows is "some platforms". works differentĮmail is handled differently on both platforms in a web application is a bad idea to begin with, but if you're using these functions they're going to behave differently between Windows and *nixįile writing, locking, etc. The same goes for PHP custom extensions (PECL). If your application relies on any Apache module, make sure it's available for both platforms. Also, the same version of a module may run differently on a different platform. Apache Windows and Apache Unix often come with a different set of Apache Modules installed by default. Ideally abstract this away with your own file path class.Īpache Modules, PECL Extensions. Even though you're on Windows, PHP will let you use a forward slash separator. Do not use the Windows backslash (\) separator. A lot of PHP functions take file paths as arguments. Here are some things off the top of my head you'll want to watch out for if you stick with your Windows environment.įile paths. For simple applications and websites, your setup is fine, but you will eventually run into subtle differences when you deploy. If you can, I'd invest in some kind of Linux, or at least *nix, development environment.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |