Welcome to the NEW CHUG— your ultimate destination for cutting-edge insights and discussions at the intersection of healthcare and technology.

Our platform is dedicated to exploring the dynamic landscape of healthcare technology, empowering professionals, enthusiasts, and innovators alike with the knowledge and resources to navigate the rapidly evolving field.

From telemedicine revolutionizing patient care to the transformative potential of artificial intelligence in diagnostics, we delve into a myriad of topics shaping the future of healthcare delivery. Whether you’re a seasoned healthcare IT professional, an aspiring entrepreneur in the digital health space, or simply curious about the latest innovations, our curated content, expert interviews, and thought-provoking articles provide a comprehensive exploration of healthcare technology’s most pressing issues.

Join us as we navigate the forefront of innovation, driving forward the transformation of healthcare for a healthier, more connected world.

Have questions or suggestions? Please use the contact button below.

Notifications

Clear all

text file version control

General Discussion

Last Post by mikeseale 8 years ago

5 Posts

5 Users

0 Reactions

70 Views

RSS

jbarnett

(@jbarnett)

Posts: 6

Active Member

Topic starter

How do you manage text file changes and versions? Does anyone currently manage their text file version via a tool like Git?

Posted : November 3, 2016 11:07 am

dcarpenter

(@dcarpenter)

Posts: 323

Reputable Member

We do not use the text files too heavily, so we do not have a separate tool like git (although that would be a good idea if you are a heavy TFE user.)

Our process is to make changes on the test environment. if it works, we copy the files to our App Server (we use Citrix, so nobody logs directly into this server). once the changes are verified to work on the APP server, I save the old, working version to a backup folder, and then use a batch file to send the changed files to our 15 Citrix servers.

This is the same proccess for our upgrading to new versions. to recap:

get files working on test server
copy files to APP server and verify that CPS still works
backup old files from a citrix server
push out all changes via batch file.

Posted : November 4, 2016 3:24 am

SLHV

(@slhv)

Posts: 478

Honorable Member

Similar to dcarpernter, we don't change ours a lot.

After testing, we rename the original to something like textfile^1.txt in our sync source folder. Our sync job is configured not to remove missing files on the destination, so renaming the original doesn't affect production.

We then copy the new tested file to the sync source folder with the intended filename. Our sync job copies the newly created version file (textfile^1.txt) to the production folders along with the new file.

There's also a way to use a single source network share folder for CCC by editing the userlib.txt file, but the method we use works just fine so we've never had reason to switch.

Posted : November 4, 2016 4:16 am

DavidShower

(@davidshower)

Posts: 1255

Noble Member

At my previous job, we used Subversion for Windows to version control all out development, including text files. But Git would work also. If you are just doing text files, SharePoint would even work if you turn versioning on where you store the text files.

Posted : November 7, 2016 3:33 am

mikeseale

(@mikeseale)

Posts: 344

Reputable Member

We use Tortoise SVN for all of our files. Since we have multiple people working on the same VFE forms, HTML Forms, and SQL reports, it makes life so much easier. The version control is the best part. You are able to go back to previous versions of any form or SQL script without having to create multiple files with different names.

Posted : November 17, 2016 3:19 am

Share:

24 Forums
9,940 Topics
39.9 K Posts
1 Online
6,470 Members

Forum Icons: Forum contains no unread posts Forum contains unread posts

Topic Icons: Not Replied Replied Active Hot Sticky Unapproved Solved Private Closed

Powered by wpForo Powered by wpForo version 2.4.0