![]() Packages like Apache2 (or nginx), PHP, MariaDB, etc. Even in production, the same configuration can be cloned for horizontal scaling. All you need is a Dockerfile from a common build and replicating an environment is trivial. I’ll use the example of a basic WordPress environment using Docker. Configuration is much easier and it’s very repeatable. ![]() I won’t go deep into what they are, but they allow us to quickly and reliably spin-up an environment or a number of environments for development. You could clone an existing VM, but there was so much to update that it was almost easier to start from scratch, especially if a project had oddball requirements. Installing software, editing configuration files, setting up backups, and integrating code and content. Going back to my old VM method for a minute, a lot of time was spent in configuration mode. However, I use something else for most other projects because I don’t want to have databases on my main computer. In fact, I use it for the WordPress core repo. In my case, I ran XAMPP for some projects. These were great programs because they ran on the machine you were already using, and they included a web server, database server, FTP server, and more right out of the box. If you didn’t have access to dedicated, server-grade hardware at home, another option was XAMPP, WAMP, etc. Rackspace was king, and, yes, GoDaddy was already horrible. AWS was nascent and mostly an internal product for Amazon. Digital Ocean and Vultr didn’t exist yet. In the mid- to late-2000s, servers were expensive. For client QA, I would add some port forwarding to allow outside access to my local server farm. The VM could be customized to fit any project in terms of resources, packages, and access. Back in the day, it was my normal process to spin-up a virtual machine, or VM, in Virtualbox on a local server, install Apache, PHP, MySQL, etc., and add some hosts records to point to alias the local environment with a practical, semantic URL. I have a whole rack of older, used Dell servers, as well as several other servers outside the rack. ![]() The Old Wayįor ages, I’ve been a server geek. Typically that means writing custom shell scripts and aliases to help sync both code and content. Unless I’m involved with the engineering at project kick-off, I usually have to adapt to what’s been put in place by other developers. Since every project is different, the workflow is usually unique as well. Agencies/companies need me to come into a sprint, usually for the stuff that’s a bit too much for juniors. The vast majority of work I do is retainer. In my case, work comes from several sources, all of it freelance. Given that WordPress is still growing 1 WP is about a third of the web now, as of April 2019, there’s no shortage of work for proper WordPress developers.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |