Kinsta, a managed WordPress hosting company, announced its local development tool named DevKinsta earlier today. The tool allows developers to spin up new WordPress sites, including multisite support, in moments. Each site is automatically configured with Nginx, PHP, and MySQL.
DevKinsta packages Adminer, an open-source database manager. The system also includes an SMTP server and email inbox for testing outgoing emails locally.
“This is the first version of the tool, let’s say the MVP, but we have a dedicated development team supporting and adding a lot of new features to it,” said Tom Zsomborgi, Kinsta’s Chief Business Officer.
Developers can run and test HTTPS support and enable
WP_DEBUG at the flip of a switch. Kinsta web hosting customers can also deploy their sites directly from the interface.
It took me around an hour to get the system set up and running. To be more exact, I spent 53 minutes. Close enough. Between having to sign out, restart my laptop, and waiting for various pieces to install, I at least managed to get a little laundry done in those dull, in-between moments.
The setup process was not a completely pain-free affair. However, the price of admission to use this tool — a little bit of my time — was well worth it.
Let me be clear. I have tested far worse systems. Even with over 15 years of development experience under my belt, I have utterly failed at setting up other local dev environments. For DevKinsta to simply get me to the finish line is a success.
However, I like simple things, and I prefer them to move along relatively quickly. I am accustomed to a 20-minute XAMPP setup. While it may not be as fancy or have the bells and whistles of more sophisticated development tools, it gets the job done and rarely doles out headaches.
The holdup was setting up Windows Subsystem for Linux (WSL 2) and Docker, which are both requirements. Jump-starting DevKinsta itself was a breeze. And, as an old-school XAMPP user, DevKinsta’s ease of use has pulled me in enough to do more than just give it a passing glance. I could actually see myself using this on a day-to-day basis.
In short, I am sold. DevKinsta is a tool all WordPress developers should at least spin up once.
Thus far, the feedback on Twitter has been generally positive. However, Linux users may have to wait a bit because the tool is only available for macOS and Windows at the moment.
“I love seeing companies releasing local development tools but I wish more would offer their services to Linux users,” tweeted WordPress developer Chad McCullough. “There are a lot of us developers out there running Linux.” The Kinsta team responded that the tool will eventually support Linux and that news is forthcoming.
The simple and straightforward UI is what makes this tool useful. Most developers do not need overly complicated configurations and options. They simply need to launch an environment that lets them work on their own projects. Anything beyond the basics far too often gets in the way.
DevKinsta makes it easy to launch and manage multiple development installs. Developers can also switch PHP versions via a simple dropdown — versions 7.2 – 8.0 are currently supported.
The obvious comparison for DevKinsta will be against Local by Flywheel, which has increasingly become a primary tool for many WordPress developers.
Zsomborgi explained why the company thinks DevKinsta is a better option. “In our case, Docker is an important part here. Local doesn’t use virtualization in the background. Local has to install every piece of the environment to the host machine (NGINX, apache, different PHP versions, etc.). DevKinsta encapsulates these technologies into containers. Containers do make things easier for maintaining different applications without interrupting the host OS or installing many of the dependencies that are not required. We pretty much don’t touch the host OS, but have Docker as our main dependency to run the applications on their own environments.”
He said this speeds up the upgrade process and makes it easier to maintain bug fixes and send out security patches. He also said that because each application runs on its own Kernel namespace, any security issues should not affect the host OS.
“If the user is comfortable enough with Docker, he can extend DevKinsta features,” said Zsomborgi. “For example, he can monitor the usage of the container, or the PHP usage specifically as an example with docker monitoring tools that comes out of the box with Docker installation. The user can install any utility inside DevKinsta containers without touching the host OS and use applications that are not supported on Windows, for example.”
One of the use cases he mentioned was installing a benchmark tool to get statistics about site performance. This can be installed inside the Nginx container as a sidecar or separate container.
“In the past, Local didn’t use exactly Docker,” said Zsomborgi. “They used VirtualBox + DockerMachine. We tried it, and it was a bit painful. But without VirtualBox, DevKinsta can be more stable and scalable. So we use Docker without VirtualBox. It also needs virtualization, but nowadays, there are fewer Windows computers that have disabled virtualization by default.”
I don’t understand the usecase. Really. Can someone explain why i should develop on a local machine? I do all my work on my server.
And doing a local docker container with wordpress is easy described here: https://docs.docker.com/compose/wordpress/
If you create a plugin or theme I’m sure you won’t do this on live server. DevKinsta gives you an in-app MailHog, SSL and MyKinsta integration.
Sounds promising. Looking forward to check it out. It took a bit of a struggle getting my local dev (Brew) to play nicely with Big Sur. Might be a thing of the past! Cheers
Didn’t realize on first read that DevKinsta currently only supports WordPress. I may still have to rely on my current Brew setup for non-WordPress websites, but I can certainly live with that. 🙂
I’ve run non-WordPress sites on Flywheel’s Local. Just let it set up a WP site for you, delete everything, and you’ve got a clean slate if you just need the PHP, database, and nginx (or Apache, at least in the case of Local). I’d bet DevKinsta is about the same.
That being said—if you like your setup, you can keep it!
I’ll stick to Local
Did you give DevKinsta a try?
I have switched to Local by flywheel from WAMP server and I’m loving it.
Looking forward to trying DevKinsta.
For windows users https://laragon.org is king and version 5 is on its way.
You can use ddev (https://www.ddev.com/) and my own extension (https://github.com/fschmittlein/WordPress-Distribution) for WordPress.
This is a brilliant development as the devops workflow becomes seamless.
I am, as a Kinsta customer, very happy and excited for this. And, of course, I already installed it (already have Docker installed) but just about to test it. It looks promising, especially after fussing with my local WP/Nginx/MariaDB … 🙂
Looking forward to a real head-to-head with DevKinsta and Local. I’ve been a Local user for quite a while, but Kinsta is a name I trust.
yes, I’d also see head-to-head comparisation. just don’t forget to calculate that Local has been developing for 6 years and DevKinsta max ~for 8 months.
I am not a developer but a business person who has launched a small consulting business and knows just enough about WordPress (I have had a WordPress site in some form since WP 3.0) to get into trouble. I do a lot of the basic maintenance work and testing out of plugins and ideas for new site functionality on my own and then hand it off to my developer to deal with the details and implement the big stuff once I have an idea of what I want. I am also a new Kinsta customer and the workflow from this to the staging server and then live server flows seamlessly and instills confidence in someone like me. Well done in my books.
Thanks for writing a great rundown of what DevKinsta has created!
I wanted to chime in about Docker and in particular Local’s use of Docker. It’s true that older versions of Local made use of Boot2Docker (basically Docker running in a VM). This was done because, at the time, Docker’s support on non *nix operating systems was pretty bad.
Things have definitely improved, and Docker on Windows and Mac has come a long way.
That being said, Local no longer uses Docker and instead uses native processes for the server software (PHP/MySQL/nginx/Apache)
We found two main issues with virtualization when Local reached scale:
Virtualization in general and Docker, in particular, caused a lot of frustration during the onboarding experience
The performance of virtualized software never reached the same performance as native processes
For more details on why Local went this route, see this tweetstorm as well as this post within the Local Community Forums:
The @LocalWP team reached an important milestone as we introduced Local Lightning to the public last week! I haven’t personally touched on the reasoning behind Lightning a whole lot so I wanted to quickly provide a deeper look into our thought-process: (cont.)
— Clay Griffiths (@claygriffiths) February 18, 2020
Enter your email address to subscribe to this blog and receive notifications of new posts by email.
WordPress Tavern is a website about all things WordPress. We cover news and events, write plugin and theme reviews, and talk about key issues within the WordPress ecosystem…
© All Rights Reserved. Powered by WordPress, hosted by Pressable