I will not get into details here about setting up XDebug on a server, but you can find that with some Internet searching. Instead, this post is about how to use XDebug within Visual Studio Code.Continue Reading PHP: XDebug in VS Code
Visual Studio Code
The first two posts covered the two big files: GitPod.Dockerfile and .gitpod.yml. This final post will cover a few minor changes I had to make to other configuration files.Continue Reading Drupal GitPod Container 3: Settings and Config
GitPod is a great tool for cloud-based containers when developing. If you’re developing and want a safe and efficient cloud container to try things out, it’s a pretty good way to go. You even get 50 hours per month for free, which is pretty great if you only need occasional side project and not full-time work. It also works with Visual Studio Code – although that has not been working for me lately – so you can use it in the browser or in your desktop editor. When you browse to a GitHub or GitLab repository with the extension installed, there’s a simple button that will launch the container with that repository’s code, making it quick and easy to see how it works as well as make changes.
In this mini-series I describe how I created a generic Drupal-friendly container working with GitPod. It is available in my GitHub. Note that since is some code I may continue using over time, the code there may change beyond what is covered in this article.Continue Reading Drupal GitPod Container 1: .Dockerfile
Configuring a hosts file on your computer allows your browsing traffic to go to a different server than is listed by public DNS. This can be essential for a few scenarios, such as:
- migrating a site to a new server and needing to test it before changing the public DNS
- development on dev/staging servers which do not have public DNS listings
This is a quick post about a feature I discovered by accident in Visual Studio Code that I really like:
I was working in a Linux machine and ran a grep in the integrated terminal to find a particular piece of code. The terminal gave me the results in the usual way, with the file names highlighted, the line in the code, and a bit of the code around what I searched for. Then I happened to scroll over the file name in the results and it showed me a tooltip offering that I could open the file by holding Ctrl and clicking on the path.Continue Reading Visual Studio Code: Grep
In a recent post I talked about how great MySQL Workbench is. A few days later, I discovered a Visual Studio Code extension simply called MySQL. It is not as robust in some ways as Workbench (e.g. bulk importing and exporting).Continue Reading Visual Studio Code: MySQL Extension
You know what desktop app made the largest improvement to my workflows when I discovered it? Not Visual Studio Code, as much as my writing sometimes hypes it up as my preferred text editor. There were already good text editors.
No, the desktop tool that made the biggest improvement to my workflows was MySQL Workbench. If you work with MySQL databases at all, this will make your life so much easier than navigating those databases in a command line.Continue Reading MySQL Workbench
I’ve written before about Visual Studio Code, my preferred text editor. One of the great things about VS Code is the large number of extensions that are available, while continuing to be a lightweight and efficient program even with lots of extensions installed.
Here are some of my favourite VS Code extensions in my workflow:Continue Reading Visual Studio Code: Favourite Extensions