Skip to content

Commit e7510bd

Browse files
committed
Local to cloud
1 parent 7dd1ec8 commit e7510bd

File tree

1 file changed

+16
-16
lines changed

1 file changed

+16
-16
lines changed

umbraco-cloud/deployment/local-to-cloud.md

Lines changed: 16 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -10,36 +10,36 @@ In this article, you can learn more about deploying your code changes and metada
1010

1111
Local changes in your Umbraco Cloud project are automatically detected and synced with your Git client for seamless collaboration.
1212

13-
There are two ways this can be done. You can push the changes using a Git GUI or your terminal. This guide will show how you can use both ways to deploy your local changes to Umbraco Cloud.
13+
There are two ways this can be done. You can push the changes using a Git UI or your terminal. This guide will show how you can use both ways to deploy your local changes to Umbraco Cloud.
1414

1515
## Prerequisites
1616

1717
* A clone of your Cloud project.
18-
* A [Git GUI](https://git-scm.com/downloads/guis) or a Terminal.
18+
* A [Git UI](https://git-scm.com/downloads/guis) or a Terminal.
1919
* Created some Document Types and Data Types with corresponding `.uda` files.
2020
* The files are located in the `/umbraco/Deploy/Revision` folder.
2121

22-
## Deploying using a Git GUI
22+
## Deploying using a Git UI
2323

24-
Once you have created some Documents and Data types, follow the steps below to deploy your local changes using a Git GUI. The guide will use [Fork](https://git-fork.com/) as the Git GUI, however you can use your own preferred Git GUI. 
24+
Once you have created some Documents and Data types, follow the steps below to deploy your local changes using a Git UI. The guide will use [Fork](https://git-fork.com/) as the Git UI, however you can use your own preferred Git UI.
2525

26-
1. Go to your Git GUI.
27-
2. Check for local changes in your GUI.
26+
1. Go to your Git UI.
27+
2. Check for local changes in your UI.
2828

29-
<figure><img src="../.gitbook/assets/image (81).png" alt="Local changes in Git GUI."><figcaption><p>Local changes in Git GUI.</p></figcaption></figure>
29+
<figure><img src="../.gitbook/assets/image (81).png" alt="Local changes in Git GUI."><figcaption><p>Local changes in Git UI.</p></figcaption></figure>
3030

3131
3. Prepare changes, so they are ready to be committed.
32-
1. Write a commit subject
33-
2. &#x20;Write a description of the commit.
34-
3. Commit the files.
32+
1. Write a commit subject
33+
2. Write a description of the commit.
34+
3. Commit the files.
3535

3636
<div align="right" data-full-width="false">
3737

3838
<figure><img src="../.gitbook/assets/image (82).png" alt="Ready the files for commit."><figcaption><p>Ready the files for commit.</p></figcaption></figure>
3939

4040
</div>
4141

42-
4. Push the files to your cloud project in the GUI.
42+
4. Push the files to your cloud project in the UI.
4343

4444
<figure><img src="../.gitbook/assets/image (83).png" alt="Push changes to Umbraco Cloud."><figcaption><p>Push changes to Umbraco Cloud.</p></figcaption></figure>
4545

@@ -52,15 +52,15 @@ After deploying changes locally to your Cloud environment, use the Umbraco Cloud
5252
To deploy your local changes from local to Umbraco Cloud using a terminal follow the steps below:
5353

5454
1. Navigate to your local projects folder using the `cd YourProjectName` command in the terminal.
55-
2. Check for pending changes in your project with `git status`
56-
3. Add the pending changes with `git add -`
57-
4. Commit the staged files using `git commit -m "Adding updated schema changes"`&#x20;
55+
2. Check for pending changes in your project with `git status`.
56+
3. Add the pending changes with `git add -`.
57+
4. Commit the staged files using `git commit -m "Adding updated schema changes"`.
5858
5. Push the changes to Umbraco Cloud using `git push`.
5959
1. Do a `git pull` if the push is rejected.
6060

61-
If you have to pull down, make sure to see if any of these commits contain changes to the schema (anything in `umbraco/Deploy/Revision/`).&#x20;
61+
If you have to pull down, make sure to see if any of these commits contain changes to the schema (anything in `umbraco/Deploy/Revision/`).
6262

63-
To validate your local site and ensure compatibility with the updated schema, use the [**Deploy Dashboard**](https://docs.umbraco.com/umbraco-cloud/deployments/deploy-dashboard) in the **Settings** section of the Umbraco backoffice.&#x20;
63+
To validate your local site and ensure compatibility with the updated schema, use the [**Deploy Dashboard**](https://docs.umbraco.com/umbraco-cloud/deployments/deploy-dashboard) in the **Settings** section of the Umbraco backoffice.
6464

6565
Here, you can see the status of ongoing or completed deployment processes. The status will show whether an operation has been triggered and is in progress has been completed, or has failed.
6666

0 commit comments

Comments
 (0)