LogoLogo
  • Overview
    • Introduction
      • Git-Based Source Control
      • DeviceLink
    • System Requirements
    • Supported Vendors and Device Types
    • Glossary
  • Git-Based Source Control
    • Getting Started
      • Planning
      • Initial Setup
        • Migrations
    • Basic Tasks
      • Navigation
        • Home page
        • Exploring the Web App
        • Exploring the Desktop App
      • Configuration
        • Creating Repositories
        • Creating Templates
        • Cloning Repositories
      • Operations
        • Pulling
        • Committing
        • Pushing
        • Managing History
        • Binary & Large Files
    • Advanced Tasks
      • Branching
        • Branch Protections
      • Pull Requests & Code Review
        • Contributors
        • Reviewers
      • Merging
    • Additional Features
      • Topics
      • Issues
        • Milestones
        • Labels
        • References and Links
      • Wiki
      • Tags & Releases
      • Webhooks
      • Activity
    • Administration
      • Org Settings
      • User Management
        • External Identity Management (SSO + SCIM)
      • Teams & Permissions
        • Permissions by Account Type
      • Registration & Billing
      • Repo Settings
      • Desktop App Options
      • Profile and Settings
        • Notifications
        • Two-Factor Authentication (2FA)
    • Supported Vendors
      • ABB
      • Beckhoff
      • B&R Automation
      • CODESYS
      • Inductive
      • Lenze
      • Rockwell
        • RSLogix 500
        • RSLogix 5000
        • Studio 5000 Logix Designer
      • Schneider
        • Control Expert
        • Machine Expert
      • Siemens
        • Siemens Step7 TIA Portal
        • Siemens Step7 5.x
      • WAGO
    • Integrations
      • Discord
      • Jira
      • Microsoft Teams Connectors
      • Slack
      • Zapier
      • Microsoft Teams Workflows
  • DeviceLink
    • Getting Started
      • Architecture
      • Planning & Installation
    • Sites and Agents
      • Sites
        • Site Settings
        • File Lists
        • Graphs and Metrics
      • Agents
        • Creating a Site-Based Agent
        • Creating a Multi-Site Agent
    • Projects and Devices
    • Vendor Configuration
      • Beckhoff TwinCAT 3
      • CODESYS v3
      • Copia FTP
      • Copia sFTP/SCP
      • Copia Scripting
      • FANUC Robots
      • Rockwell RSLogix 500
        • Smart Filter
      • Rockwell Studio/RSLogix 5000
        • Smart Filter
      • Rockwell PanelView ME HMI
      • Schneider Control Expert
      • Siemens Step7 TIA Portal
      • Siemens Step7 5.x
    • Jobs
      • Job Navigation
      • Creating Jobs
      • Managing Jobs and History
      • Manual Backups
      • Pull Requests
    • Additional Features
      • Webhooks
      • Copia Import Tool
        • Getting Started
        • Preparing your data
        • Importing your data
        • Rolling back a prior import
    • Administration
      • Teams
      • Permissions
      • Notifications
  • Copilot
    • Copia Copilot
    • Getting Started
    • Using Copia Copilot
  • Copilot FAQ
  • Support
    • Best Practices
    • FAQs
      • Git-Based Source Control
        • Troubleshooting
      • DeviceLink
        • Troubleshooting
Powered by GitBook
On this page
  • Collaborate Using Copia
  • Manage Virtual Machines

Was this helpful?

  1. Support

Best Practices

PreviousCopilot FAQNextFAQs

Last updated 3 months ago

Was this helpful?

Collaborate Using Copia

Copia shines when used in collaboration with multiple engineers. Some of the benefits of using Copia for collaboration include:

  • Ability to invite external users or contractors with read-only seats.

  • Ease of transferring repositories to clients

  • Use of Copia across different Teams and functions as a source of truth for accessing the latest version of a project

To learn more about collaborative features like Organizations, Teams, Issue Tracking, and Wikis, check out the section.

But generally, there are several rules of thumb to keep in mind when collaborating using Copia:

  • Keep branches short-lived.

    • Generally, the turnaround time of merging a branch should be quick. This also means that branches should be relatively small.

    • Try to have everyone merging into the same branch (Prefer fewer target branches)

      • Generally, everyone on your team should be merging into the same branch (the mainline). Releases and release candidates (RCs) should branch off of the mainline.

  • Merging between multiple non-mainline branches is discouraged.

Manage Virtual Machines

Copia supports the use of virtual machines. You can either run the Copia Desktop App app from within the virtual machine or via the host.

We recommend that you create a shared folder between the virtual and host machines. This way, you can run Copia on the host machine and monitor the shared folder from as many VMs/IDEs as needed.

This suggested workflow allows Copia users to make changes on one machine as opposed to switching back and forth between multiple machines.

Advanced