People using **mp tend to set up things based on their host OS (weird \'s or the user's own home directory, etc) so they have no idea what to do when it comes to actually setting up an application on a real server. Not only will you learn a bit of Linux setup and usage, but it will give you a knowledge advantage over **mp users when it is time to set up a production environment. If you are on a mac, I would suggest Docker, but there are filesystem issues which neither Docker nor Apple want to fix (it can be done, but requires work-arounds to not be slow af), so best bet there would be firing up a Linux VM. If you are learning on Windows, utilize WSL so PHP will be running in a semi-realistic If you don't give a :poop: about the backend and just need to get something working so you can do front-end design, then it might be fine for you. Yes, it's used mostly for web/APIs, but learning the language does not mean you need to know how to set up apache, mysql, etc. When learning PHP, you do not *need* a webserver. Personally, I would not start someone out on wamp/xamp/**mp unless they want lean more towards front end and need to learn HTML/CSS/JS first. on if you want to be a "website developer" or a "PHP developer". Probably going to bet flamed, but my answer would be "it depends". No need to blame tools for general incompetence. What people are saying about spaghetti code-bases are perfectly do-able on more professional environments as well. For the bigger projects I run Docker simultaneously to run tests to verify it'll work after committing to remote. The things I do, I can do using any locally installed PHP though, so whether it be Xampp, Wamp or any other, it would be fine. Then again though, things like Xampp and Wamp make for fast developement (on Windows, which I use), versus things like Docker (which I also use). However, our company also does a bunch of WP websites and sometimes (very very rarely, thank god), I gotta take a look at some code and help out a colleague. I've got Xampp installed but only use it for the PHP installation during development, for which I use the Symfony CLI (which requires a locally installed PHP instance). Use what you need, not what someone else thinks you need. We have it running on Google Servers and Amazon Servers and local XAMPP servers and if it can't thats a bug and we fix it. I mean I have a app that has thousands of files, relies on elasticSearch, redis and a composer file a mile long and I have Developers and QA people running Windows, MacOS and ChromeOS all contributing to it. If you are worried about human error then let your code determine where it is running and read the appropriate config file. Yes, you have to have a config for your development setup and your production setup. Absolute paths are both unnecessary and inflexible. If you have an absolute path anywhere in your code then you should recode it. There isn't a major framework out there that depends on absolute paths. Its almost the default situation I would imagine. There a thousands out there that develop on windows and run prod on linux. You should never rely on results being what you expect them to be. "Some extensions behave differently between windows and Linux (like the FS ones for instance, stats does not return the same values on both OSes)." I do not think it can get much easier than that. Even setting up Let's Encrypt is a matter of typing a few commands in terminal. It is extremely easy to setup, and the location of configuration files is very intuitive once you get used to Linux. You got to remember, in Ubuntu at least, it is just a simple matter of running: sudo apt install apache2 PHP8.0 mysql-server php8.0-fpm In the end I gave up and just installed Apache MySQL PHP the old fashioned way, and I find that works very well for me. Last time I tried XAMPP I actually found it to be confusing and complicated, since stuff was stored in non-standard locations. This was before the time of social media FYI, so the tone was very rough on these forums - if you asked a question before Googling and doing your homework, you would be crushed! I think I even tried it out a few times, but the nerds, at the time - those hanging out on the forums - was advising people to install servers manually, since they would learn more, so that was what I did. Back when I started out learning how to setup servers, I remember XAMPP being promoted as the beginner-friendly alternative to setting up your own servers.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |