Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
PRESENTED BY
Hands-on with Source Control:
Using Flare with a Cloud Source Control Provider
Paul Pehrson
DocGuy Training |...
About Me
• (Ab)using Flare for 10
years
• Full time technical writer
at Venafi
• Part time Flare consultant
and trainer at...
Let’s talk source control
What benefits does source control give me?
• Project is backed up. Forever.
• Multiple writers, one project.
• Version tra...
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...
Step 2: Figure Out Where Your Database Is
• Dev group?
• Cloud provider
• Set up your own
Step 3: Configure CloudForge
1. Go to www.cloudforge.com
2. Click Login
3. Enter the username and password assigned to you...
Step 4: Configure Flare
1. Visit
http://www.docguy.training/MW2016/SampleSourceCont
rol.flprjzip
2. Locate the download on...
Step 5: Day-to-Day Operations
• Update the Project
• Modify files
• Check in files
• Lock a file
• Source Control settings...
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...
Q&A
Thank You!
Visit my website for more information on consulting and training opportunities
www.docguy.training
Hands-on with Source Control: Using MadCap Flare with a Cloud Source Control Provider
Hands-on with Source Control: Using MadCap Flare with a Cloud Source Control Provider
Upcoming SlideShare
Loading in …5
×

Hands-on with Source Control: Using MadCap Flare with a Cloud Source Control Provider

700 views

Published on

You already know you should be using source control, but implementing it may sound daunting. In this two-hour workshop, we’ll take an existing MadCap Flare project and bind it to your choice of either a Git or Subversion repository in the cloud, live and in-session.

Published in: Software
  • Be the first to comment

  • Be the first to like this

Hands-on with Source Control: Using MadCap Flare with a Cloud Source Control Provider

  1. 1. PRESENTED BY Hands-on with Source Control: Using Flare with a Cloud Source Control Provider Paul Pehrson DocGuy Training | @docguy | www.docguy.training
  2. 2. About Me • (Ab)using Flare for 10 years • Full time technical writer at Venafi • Part time Flare consultant and trainer at DocGuy Training
  3. 3. Let’s talk source control
  4. 4. 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?)
  5. 5. Begin with the in mind Image Credit: Mike Wolpert
  6. 6. 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
  7. 7. Step 2: Figure Out Where Your Database Is • Dev group? • Cloud provider • Set up your own
  8. 8. Step 3: Configure CloudForge 1. Go to www.cloudforge.com 2. Click Login 3. Enter the username and password assigned to you 4. Create a Project 5. Choose SVN (to minimize questions today)
  9. 9. Step 4: Configure Flare 1. Visit http://www.docguy.training/MW2016/SampleSourceCont rol.flprjzip 2. Locate the download on your computer and double-click it to open it in Flare 3. Open Project Properties 4. On Source Control tab, Bind Project… 5. Use options from CloudForge, and click Okay.
  10. 10. Step 5: Day-to-Day Operations • Update the Project • Modify files • Check in files • Lock a file • Source Control settings in Flare
  11. 11. Administration • Add users • Review revision history • Resolve conflicts
  12. 12. 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
  13. 13. Q&A
  14. 14. Thank You! Visit my website for more information on consulting and training opportunities www.docguy.training

×