hands-on with source control: using madcap flare with a cloud source control provider
TRANSCRIPT
PRESENTED BY
Hands-on with Source Control:Using Flare with a Cloud Source Control Provider
Paul PehrsonDocGuy Training | @docguy | www.docguy.training
Advance
d Works
hop
About Me• (Ab)using Flare for 10
years• Full time technical writer
at Venafi• Part time Flare consultant
and trainer at DocGuy Training
Let’s talk source control
What benefits does source control give me?
• Project is backed up. Forever.• Multiple writers, one project.• Version tracking that matches your product.• UNDO! Oh Crap!
(i.e. Why do I care?)
Begin with the
in mind
Image Credit: Mike Wolpert
Step 1: Pick a Source Control Provider• Flare connects with the following source control
providers natively:– Subversion (SVN)– GIT– Microsoft Team Foundation Server (TFS)– Microsoft Visual Source Save (VSS)– Perforce
Step 2: Figure Out Where Your Database Is• Dev group?• Cloud provider• Set up your own
Step 3: Configure CloudForge1. Go to www.cloudforge.com2. Click Login3. Enter the username and password assigned to you4. Create a Project5. Choose SVN (to minimize questions today)
Step 4: Configure Flare1. Visit
http://www.docguy.training/MW2016/SampleSourceControl.flprjzip
2. Locate the download on your computer and double-click it to open it in Flare
3. Open Project Properties4. On Source Control tab, Bind Project…5. Use options from CloudForge, and click Okay.
Step 5: Day-to-Day Operations• Update the Project• Modify files• Check in files• Lock a file• Source Control settings in Flare
Administration• Add users• Review revision history• Resolve conflicts
How GIT is different• Local commits vs. pushing to the server• Better option if you work offline frequently• Better for smaller doc teams (fewer merge conflicts)• Doesn’t allow you to ‘lock’ files, which makes for more
merge conflict potential than SVN
Q&A
Thank You!
Visit my website for more information on consulting and training opportunities
www.docguy.training