From client projects to personal ones I played with. And this time I wrote down what I did Backup first So about a month or so ago I decided to start from scratch. It’s a tool that just speeds up my development a ton. I’ve set up my external IP address, ports, and everything and I couldn’t get the step debugging to work on my PhpStorm. I never got to the bottom of it to be honest. One of the bigger hiccups was Xdebug not working properly. I got it working, but there were a few hiccups. Remember the multiple PHP versions thing I’ve mentioned? Yeah, using something like phpenv with valet-wsl means you need to modify things a bit. It’s Valet, but for WSL and ubuntu on it. It’s lightweight and it works beautifully. On my Mac, I used Laravel Valet as my dev environment. I like to play around with different PHP versions for instance. The thing you need to know about me is that I’m a person who likes to test things and tinker with different development solutions. Well, I’m still not there quite yet, but it’s getting better. It has to be smooth sailing – I turn everything on, and it just works. So I’ve decided that I’d like to just work with the terminal. I could just use the alias command but I learned about it way later. I was using WSL2 with Docker Desktop, and while it worked, I had to pay attention from where I started my project, to start my docker, I haven’t played around with the certificates, and running WP-CLI commands in order to do any work on my WordPress projects meant I had to provide the –ssh flag in order to run the WP-CLI on the Docker instance. I’ve played around with it and ended up with some slowdown issues as well. That’s because, on Mac, the Docker has to run using virtualization, they’re not sharing the same kernel as on Linux machines, or something like that.īut I had a PC, so things should work out better here, right? I’ve tried out everything, Devilbox, some weird listener/propagation hacks. The problem for me (when I tried using Docker as my daily driver) was that the file sync on Mac with Docker was just too slow. I remember reading articles about how it didn’t work at all when it came out, but maybe they fixed it in the meantime. I’m not sure if anything got better with the new M1 processors. One huge drawback Mac has is working with Docker. But given that I had a brand new, clean computer, I wanted to play around a bit. Previously you either had to mess with the PowerShell, or install gitbash, and it was a bit odd to work with, in my opinion. I knew that Windows 10 had Windows Subsystem for Linux (WSL) support for a while, so that was a comforting thought. I wanted to show how I’ve set up my development environment, but also have it saved somewhere in case I need to redo it again sometime in the future ?. This article was inspired by Carl Alexander’s How I setup my 2021 MacBook Pro article. One thing I didn’t want to give up was terminal. So after about 4 years of developing on Mac, I had to go back to a PC, and re-learn (or unlearn?) the command/control and other development shortcuts that were baked into my brain. This year my main development driver was my PC. Given the article title, we won’t be going through the personal change part. Both on a personal level, but also on a development level. And I really love working from the terminal. I guess it comes down to the fact that under the hood it’s a Unix based system, so its terminal is really nicely integrated with it. It took me some two weeks to get used to the whole command/control switcheroo, but overall I was, and still am, a big fan of using Mac for development purposes. Then in 2017, I’ve got a job as a software engineer at Infinum, and I had to switch to Mac for development. That’s just what I grew up with, and was comfortable with. I’ve always been a PC Master Race person. Over the years my development setup changed quite a lot.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |