An Easy Way to Set up Grav for Local Development

October 4th, 2016 at 1:50pm | Reading Time: 3 minutes, 58 seconds

You should almost never download individual files via FTP, edit them, and then upload them—overwriting the older copies on a server. This is a generally outdated practice and something I still see used frequently when people don't know of a better option, are too lazy to change, or maybe just in a hurry. It's also very prone to errors, and if you overlook something and overwrite a file without a backup copy, well—you're screwed. This is also why the entirety of modern development workflows rely on version control systems, like Git.

The correct way to do development for your blog is to have two copies of your website: your production copy (the site that is live on the web), and your development instance (the mirrored copy that you actually modify and develop, that lives on your local machine). Since Grav was designed for developers, there are some great ways to get started with this kind of environment. Here is a fast route to getting up and running:

Hopefully this will help anyone who is out there working on their Grav blogs to create a nice mirrored development setup, so they don't accidentally overwrite files on a live site, or edit files on their production servers; directly.

  • Blogging
  • Technology

Nick Warren

Nick Warren is the Founder & CEO of MetaSensor, a venture-backed IoT startup located in Silicon Valley, and a consulting Product Designer at the Center for Advanced Hindsight (with Dan Ariely et al.). | Read Full Bio »