Quick Tip: Disable Auto-Updating of CodeKit Settings

When it comes to CodeKit, there are normally global CodeKit settings that I use; however, a number of the projects that I work on often result in some minor deviation from my core settings.

For those who have used CodeKit regularly, you know that you can set per-project settings, but if you’re using a project that’s under source control, there’s likely one irritating factor that you’ve noticed.

CodeKit Settings: It’s All Under Control

The problem with placing your CodeKit project and the associated CodeKit settings under source control is that you often see something like this:

CodeKit Settings in Source Control
CodeKit Settings in Source Control

Specifically, you see the CodeKit configuration file showing up every several minutes.

Because CodeKit automatically refreshes projects every so often depending on how you have it configured, the configuration file is also updated.

Thus, it shows up as an updated file needing to be committed to work your working directory.

The other day, a friend and I were talking about this exactly issue and he was mentioning that although he loves CodeKit, he hates having the settings file constantly changing.

So, sure, you could always add `codekit-config.json` to a `.gitignore` file of your version control’s equivalent, but if you don’t update your settings that often, you can also disable the automatic updating within CodeKit itself:

Disable CodeKit Settings
Disable Auto Update of CodeKit Settings

If you notice on the Project Settings screen, there’s a checkbox for “Auto-update configuration file.”

Un-check that option to disable the auto-refresh of the CodeKit settings file and you’re gold. Easy enough (and you don’t have to deal with source control ignore files either :)).

8 Replies to “Quick Tip: Disable Auto-Updating of CodeKit Settings”

    1. It was all part of a conspiracy – I contacted Brandon, the guy behind CodeKit, told him to build a feature that I knew would annoy you, then I wrote this post waiting for you to find it so that I could write this comment.

  1. This is driving me nuts too.

    What is the downside of not letting it update this file?

    I guess I’m starting to question what this file even does…I thought it was to help team members sync up their settings, but it seems to be perpetually updated by each client that refreshes, so that kind of defeats the purpose?

    1. The downside is that you’ll need to manually save, then commit your changes whereas before, the app would do it for you.

      If you’re working with a team, I’ve found that the easiest thing to do is just keep a copy of the JSON file in source control and pull it each time there’s an update; otherwise, it just keeps creating updates that aren’t really changes.

  2. Thanks.. You know what’s even worse? When the codekit-config.json file is the Dropbox folder at home and you keep getting buggered every 5 minutes at work with a Dropbox bubble informing you that the file has updated. It even messed up my entire git merging and drove me nuts for 3 days (git noob, mostly my fault)… All this is to say thanks a bunch for the tip, it made a difference here..

    1. Haven’t looked in the latest version. Usually, I have the file added to .gitignore. In the case that I do need to save the file, say, for teamwork then I got ahead and just commit it to the repository with the changeset so the latest version is always available.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.