You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: umbraco-cloud/deployment/local-to-cloud.md
+16-16Lines changed: 16 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,36 +10,36 @@ In this article, you can learn more about deploying your code changes and metada
10
10
11
11
Local changes in your Umbraco Cloud project are automatically detected and synced with your Git client for seamless collaboration.
12
12
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.
14
14
15
15
## Prerequisites
16
16
17
17
* 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.
19
19
* Created some Document Types and Data Types with corresponding `.uda` files.
20
20
* The files are located in the `/umbraco/Deploy/Revision` folder.
21
21
22
-
## Deploying using a Git GUI
22
+
## Deploying using a Git UI
23
23
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.
25
25
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.
28
28
29
-
<figure><imgsrc="../.gitbook/assets/image (81).png"alt="Local changes in Git GUI."><figcaption><p>Local changes in Git GUI.</p></figcaption></figure>
29
+
<figure><imgsrc="../.gitbook/assets/image (81).png"alt="Local changes in Git GUI."><figcaption><p>Local changes in Git UI.</p></figcaption></figure>
30
30
31
31
3. Prepare changes, so they are ready to be committed.
32
-
1. Write a commit subject
33
-
2. 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.
35
35
36
36
<divalign="right"data-full-width="false">
37
37
38
38
<figure><imgsrc="../.gitbook/assets/image (82).png"alt="Ready the files for commit."><figcaption><p>Ready the files for commit.</p></figcaption></figure>
39
39
40
40
</div>
41
41
42
-
4. Push the files to your cloud project in the GUI.
42
+
4. Push the files to your cloud project in the UI.
43
43
44
44
<figure><imgsrc="../.gitbook/assets/image (83).png"alt="Push changes to Umbraco Cloud."><figcaption><p>Push changes to Umbraco Cloud.</p></figcaption></figure>
45
45
@@ -52,15 +52,15 @@ After deploying changes locally to your Cloud environment, use the Umbraco Cloud
52
52
To deploy your local changes from local to Umbraco Cloud using a terminal follow the steps below:
53
53
54
54
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"` 
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"`.
58
58
5. Push the changes to Umbraco Cloud using `git push`.
59
59
1. Do a `git pull` if the push is rejected.
60
60
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/`). 
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/`).
62
62
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. 
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.
64
64
65
65
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.
0 commit comments