Shop OBEX P1 Docs P2 Docs Learn Events
Version management software suggestions needed... — Parallax Forums

Version management software suggestions needed...

pmrobertpmrobert Posts: 675
edited 2013-10-07 14:04 in General Discussion
I have several projects under development, undergoing upgrades and additions, etc. Physically, I have a home office with my nicest system (multiple monitors, scopes, function generator, banch power supplies, 25mb Internet connection, etc.). I also have a shop, 10 miles distant, no internet besides phone hotspot, where most of the software actually executes on live machines that test and characterize fuel injectors, coils, etc. The shop has one industrial kiosk type PC that controls the pumps, injector drivers, coil IGBTs, etc. - this is the actual operational and financially productive part of my business. I also have a decent laptop that I usually keep at the shop but if I need to go on the road it's available. My problem is that I try to keep the latest version of all the software (3 PC apps, 3 Prop apps) on a USB drive and copy it back and forth to the hard drive of whatever machine I'm developing on at each physical location. Being human, I occasionally mess up and accidentally overwrite the latest version among other human errors. I'm wondering if a version control system, where I'm led to believe you can check out and check in code and have a central repository, might be the answer to my problems. The phone hotspot connection at the shop works just fine for up to 5GB/month - then it gets expensive but I think that's plenty for what I'm thinking of. All machines are currently using Windows but I'm fairly well versed in Linux and could easily power up an old machine running Linux and throw it on the home network. I'm seeking advice, guidance, whatever crumbs you all can throw my way. Thank you for reading my overly long request, I tried to fully describe my environment!

-Mike

Comments

  • Heater.Heater. Posts: 21,230
    edited 2013-10-07 10:07
    I feel your pain. I have worked like that for many years. I have also tried many source code management systems and been subjected to others by various employers. My conclusion is that the best way to go is github:
    https://github.com/

    If you are really paranoid about having your code in the cloud run your own git server. But is suspect most of us don't need that.

    I just love the ease with which I can hack code in the office, push it to the server and then hack it again when I get home or to some other site. Never have to worry about breaking anything because I can always go back.
  • SRLMSRLM Posts: 5,045
    edited 2013-10-07 12:33
    I'd use Git. You have two options for getting your code to your shop:

    1. Use an online service (such at Github) to host, and git pull it from the shop.
    2. Store your local copy of the repository on your flash drive and transport that around. Since Git is just a hidden directory this will work fine for "sharing" your code between computers, while automatically backing it up via version control.
  • pmrobertpmrobert Posts: 675
    edited 2013-10-07 14:04
    Heater. wrote: »
    I feel your pain. I have worked like that for many years. I have also tried many source code management systems and been subjected to others by various employers. My conclusion is that the best way to go is github:
    https://github.com/

    If you are really paranoid about having your code in the cloud run your own git server. But is suspect most of us don't need that.

    I just love the ease with which I can hack code in the office, push it to the server and then hack it again when I get home or to some other site. Never have to worry about breaking anything because I can always go back.
    Thank you! I'm now using github. It addresses all my concerns. I'm looking forward to not doing the "Oh ^%$!" right after I overwrite some hours worth of work.
    This is a great community, it is very much appreciated. I try to give back what I can when I can. Thanks to Heater and SRLM!

    -Mike
Sign In or Register to comment.