If you’re making improvements to your sites, even as simple as pushing updates, you’re going to be changing things around. Inevitably, you’ll break something. Wouldn’t you like to find that out before the production site goes down from the “improvements”?
In short, choosing a particular technology allows us to:
Make a decision once and leverage the results over and over
Increase profitability
Increase developer satisfaction
When you build a new website, going live is relatively easy. You get ahold of a domain name, point it at a webhost, put the website code there, and you're up and running!
After a site is live, it gets a lot more complicated.
Glitzy websites are all the rage these days. Everybody seems to be looking for easy ways to create multimedia-rich pages with ease.
Just ran across a sad story where Digital Ocean is accused of killing a startup:
New versions of Drupal core dropped today, to fix a file handling issue.
After assessing the patches, statements, and risks associated with this update, we have decided this is an important update to apply, but not urgent for most of the sites we manage.
How much do you know about the firm you're partnering with for web development and DevOps? Watch our quick video to get to know our founder John Locke better!
At Freelock, we’re in the business of building websites that make your business better.
Go ahead... Make My Changes in Prod
You thought I was going full "Dirty Harry" there, didn't ya? It's okay, I kinda wanted to as well. You can't go wrong with Clint Eastwood.
A client asks about yet another hosting option:
The VPS-2000HA-S includes the following resources:
6GB RAM (burstable)
150GB SSD Disk space
5TB Monthly Bandwidth
4 free dedicated IP's
Software as a Service (SaaS) is all the rage these days.
Wordpress's most recent release, which they are calling "5.0" (catchy, huh?), comes with a bunch of new functionality and makes the solution "easier to use". Of course, I'm putting "easier to
