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
  • Overview
  • Resources
  • Configuration

Was this helpful?

  1. Git-Based Source Control
  2. Supported Vendors

Inductive

PreviousCODESYSNextLenze

Last updated 2 years ago

Was this helpful?

Overview

Copia provides native Git support for Ignition 8, as recommended by Inductive Automation. No additional advanced features are provided at this time. The configuration below is provided to assist in the configuration of Copia and Ignition. In addition, we recommend you also review the Inductive Automation resources for additional details.

Resources

Configuration

The configuration below is based on the "" resources provided above, but adapted to make it easier for users to set up the product in Copia. This workflow stores all Ignition projects into a single repository.

In this section, we are going to assume:

  • The user has already created a Copia account

  • You are working on your Ignition development system.

  • You have downloaded, installed and configured the Copia Desktop App

Let's get started!

  1. Open the Copia desktop app on the PC which has the Ignition projects directory

  2. Select File -> Add local repository...

  3. Navigate to the Ignition projects directory using the "Choose" button (replacing the <IGNITION INSTALL DIRECTORY> in the image below with the correct path). Copia will identify that it is not currently a repository, and ask if you would like to create it. Click "create a repository".

  4. You will be asked for a name and description for the new repository. I have changed them, as seen below, and we recommend adding a README, so that you can update it later, if needed. (a .gitattributes and .gitignore file will be automatically added, as well)

  5. Now you have created your repository locally, you just need to publish it to Copia. Click the "Publish Repository" button.

  6. Now update this information with the name and description used in Step #4, choose the correct organization and press "Publish repository"

  7. We will now update the gitignore, by selecting the Repository Settings

  8. In the Repository Settings, selected the "Ignored files" section and add ".resources/" to the bottom of the list, and press "Save"

  9. Add a backup of the tags, images and Gateway, if applicable. As recommended by Inductive Automation, put the them into the project directory:

    • Export the tags from the Designer into a tags.json file.

    • Use the Image Management Tool in the Designer to export all images to a folder called “images”.

    • Make a Gateway backup.

  10. Back in the Copia Desktop app, you should now see the gateway backup, gitignore, tags.json and "images" folder with its contents. Add a commit summary and description, and press "Commit to Main", and then "Push" your changes to Copia

  11. Inductive Automation recommends creating a branch for both Development and Testing. This is accomplished easily via the desktop all, following the . Once for Development and another time for Testing.

  12. On the dedicated development and testing machines (or VMs), install the Copia desktop app. You can then "Clone" the repository by first selecting "File -> Clone repository..."

  13. Select "app.copia.io at the top, use the filter field to narrow your selections, and choose the repo you want to clone. In the local path, make sure to edit it to reflect the "Ignition Install Directory + /data/projects". Press Clone.

From this point forward, you can follow along using the Inductive Automation document linked above to add auto-commits, if desired (Step #8, in that document). On each system, use the Copia Desktop app to pull changes, push commits and switch branches, as needed. Copia fully supports merging, as well, for updating the Main from the development or testing branch.

https://inductiveautomation.com/ignition/
https://inductiveautomation.com/resources/article/ignition-8-deployment-best-practices
Ignition 8 Deployment Best Practices
Standard Workflow in the Branching section