KB0024 - Moving a PowerShell Universal to a new git remote

KB0024 - Moving a PowerShell Universal to a new git remote

Purpose

The purpose of this document is to provide the steps necessary to migrate a PowerShell Universal git repository from one remote to another. 

Overview

PowerShell Universal does not provide this functionality directly in the platform. You will need a git client installed on your machine to follow this process. 
For example, Git for Windows.

Process

1. Create a bare git repository on the target remote. 
2. If you have configured git sync in the PowerShell Universal admin console, navigate to Settings \ Git, click Git Settings and then click Reset. 
3. Stop the PowerShell Universal service. 
4. Navigate to the PowerShell Universal repository and run the following commands: 
  1. git remote set-url <remote name> <target git repository> 
  2. git push
An example of this command would be: 
  1. git remote set-url origin https://github.com/ironmansoftware/fuzzy-giggle.git
  2. git push
After running the command, your PowerShell Universal configuration files will be present in the new repository. 
5. If you have configured git settings within appsettings.json, update your git settings to reflect the new git remote. 
6. Start the PowerShell Universal service. 
7. If you have configured git settings within the admin console, navigate to Settings \ Git and click Git Setting. Enter the new git remote settings. 

    • Related Articles

    • PowerShell Universal Service crashes on startup after an upgrade to 1.4.6

      Version: PowerShell Universal 1.4.6 Issue The PowerShell Universal service will crash with the following error in Event Viewer.  Application: Universal.Server.exe CoreCLR Version: 4.700.19.56402 .NET Core Version: 3.1.0 Description: The process was ...

    • KB0069 - PowerShell Universal Startup Process

      Purpose The purpose of this document is to outline the steps that PowerShell Universal takes when starting up. Process 1. Insert current product version and install date in database Updates the database with a record about the current product version ...

    • KB0011 - Are licenses different between Production, QA and Test/Development servers?

      Update January 24th, 2023 Adam recently summarized the Developer's license per below: The only real limitation on the developer license is that it cannot be accessed remotely. The server is only available on loopback when using the dev license. If ...

    • KB0035 - How to add the Calendar and other components

      Purpose The purpose of this article is to demonstrate how to install and use the Calendar component (module) Background There is a growing list of add-on components (modules) for PowerShell Universal at ...

    • KB0048 - License is about to expire

      Scope This article only applies to PowerShell Universal instances with a perpetual license (monthly licenses excluded). See https://ironmansoftware.com/license/info for more information about PowerShell Universal licensing. Problem Your PowerShell ...