Jump to content

FileMaker Pro version control with Git in Beanstalk / Github?


This topic is 2015 days old. Please don't post here. Open a new topic instead.

Recommended Posts

  • Newbies

We currently use Subversion for version control of our FileMaker development, but we're starting to explore moving to Git instead. We've heard some rumors of people experiencing file corruption when using Git for FileMaker files, but I haven't been able to track down any real sources.

Is anyone using Git for version control of FileMaker Pro files? Other than needing to close the files completely before committing, have you had any issues?

Link to post
Share on other sites

FM does not really lend it itself for that kind of version control since it is all one binary file.  There is no forking and merging of scripts or layouts within a file and so on.

 

We solve it by hosting the dev files on a dev server and running backups at 10 minute intervals.

Link to post
Share on other sites

This topic is 2015 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Similar Content

    • By Brooks
      File Name: iPoint Version Control
      File Submitter: Brooks
      File Submitted: 30 Dec 2012
      File Category: Solutions
      FM Version: 12

      This is a simple file that can help you with version control. If you work from different locations or use different computers it can get frustrating keeping track of the most current version. I tried drop box, but had many issues of conflicting copies and found myself repeating hours of work due to poor version management. This file will allow you to have a secure location to keep your file. To work on a file you must check it out, and minimize the version control file. The Version Control file will not close until you check back in your file. It automatically updates the build number each time you check in your file and also requires a brief description of changes made. By hosting the version file you will always be working from the most recent project file and it will be kept in a central storage location. I made this file for myself and you may use a very different numbering or tracking method, so feel free to alter this file as needed to suite your needs. Please let me know if you encounter any bugs!
      NOTE: When checking in a file the checked in file replaces the checked out file. If you wish to keep a copy of the file prior to change make a new version and then check out the file and continue modification. Also, this is for development files only. If you have large files with lots of data this will be a slow process over a WAN.

      Click here to download this file
    • By Brooks
      This is a simple file that can help you with version control. If you work from different locations or use different computers it can get frustrating keeping track of the most current version. I tried drop box, but had many issues of conflicting copies and found myself repeating hours of work due to poor version management. This file will allow you to have a secure location to keep your file. To work on a file you must check it out, and minimize the version control file. The Version Control file will not close until you check back in your file. It automatically updates the build number each time you check in your file and also requires a brief description of changes made. By hosting the version file you will always be working from the most recent project file and it will be kept in a central storage location. I made this file for myself and you may use a very different numbering or tracking method, so feel free to alter this file as needed to suite your needs. Please let me know if you encounter any bugs!
      NOTE: When checking in a file the checked in file replaces the checked out file. If you wish to keep a copy of the file prior to change make a new version and then check out the file and continue modification. Also, this is for development files only. If you have large files with lots of data this will be a slow process over a WAN.
  • Who Viewed the Topic

    13 members have viewed this topic:
    Pipm  Dirigo  amerioca  toolhead  Slater  Chip Demetri  moriya0238  JosephK  AlanTrewartha  Lowermountain  axon  -Queue-  Zach360Works 

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.