1

Looking into cleaning up a repo - we are using CodeKit on this project, and want to remove the generated files from the server and repo etc.

But then what is the best way to make sure that other devs on the project use the same CodeKit config files?

We have considered keeping the CodeKit file in dropbox, but then that seems like it would get cumbersome to have to go download it from there anytime someone is working on the project. And hope that they remember to do so...

What are some suggestions for keeping CodeKit config files out of the repo, but keep the development team in sync with using CodeKit, sharing the config file etc?

Hugo y
  • 1,421
  • 10
  • 20
ByteMyPixel
  • 151
  • 2
  • 3
  • 15

2 Answers2

1

As suggested in Using CodeKit With Git, a config.codekit3 file could be part of the history of your repository.

If you don't version in the repo itself, then it becomes a tooling issue, with its own deployment/update challenge.
Dropbox (that you mention) should synchronize automatically that file, and you could then add a symbolic link from your project to said synchronized file.
If that file is managed in a folder with a common path on all developers platform, that symlink can be versioned in your Git repo.

VonC
  • 1,262,500
  • 529
  • 4,410
  • 5,250
-2

Go to Codekit > Preferences and check both options under "Pause File-Watching when:"

More about that on https://codekitapp.com/help/git/

Milan Rabrenovic
  • 1