Skip to content

Commit 0ce3f5f

Browse files
Review and resize
1 parent cbfa03b commit 0ce3f5f

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

content/en/docs/refguide/version-control/on-premises-git.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,7 @@ With most providers, HTTP basic authentication takes the form of using of person
4242

4343
To use PAT (or another equivalent), you need to specify it in the **Password** field when Studio Pro requests credentials for the version control server:
4444

45-
{{< figure src="/attachments/refguide/version-control/on-premises-git/sign-in-dialog.png" alt="Sign In dialog" class="no-border" >}}
45+
{{< figure src="/attachments/refguide/version-control/on-premises-git/sign-in-dialog.png" alt="Sign In dialog" class="no-border" width="600">}}
4646

4747
{{% alert color="info" %}}When using a PAT for the Mendix platform, fill in your email in the **Username** field. For more information on how to create a PAT for the Mendix platform, see the [Personal Access Tokens](/community-tools/mendix-profile/user-settings/#pat) section in *User Settings*.{{% /alert %}}
4848

@@ -88,15 +88,15 @@ To interact with this private repository from Studio Pro, you need a link to the
8888

8989
To use on-premise Git, you need to configure name and email values that will be used to identify your commit in Studio Pro by navigating to **Edit** > **Preferences** > **Version Control**:
9090

91-
{{< figure src="/attachments/refguide/version-control/on-premises-git/preferences-git.png" alt="Preferences dialog" class="no-border" >}}
91+
{{< figure src="/attachments/refguide/version-control/on-premises-git/preferences-git.png" alt="Preferences dialog" class="no-border" width="800" >}}
9292

9393
Studio Pro now is set up to support Git.
9494

9595
### Creating an App {#create-app}
9696

9797
Create an unversioned app in Studio Pro:
9898

99-
{{< figure src="/attachments/refguide/version-control/on-premises-git/app-settings.png" alt="App Settings dialog" class="no-border" >}}
99+
{{< figure src="/attachments/refguide/version-control/on-premises-git/app-settings.png" alt="App Settings dialog" class="no-border" width="600">}}
100100

101101
Once the app is created, you can upload it to your private Git repository. For more information on how to upload it, see the [Uploading to the Private Git Server](#upload-to-private-git-server) section below.
102102

@@ -116,7 +116,7 @@ Now that you have a Git app on your server, you can download it to another direc
116116
1. Click **OK**.
117117
1. In the **Sign In** dialog box, enter your credentials:
118118

119-
{{< figure src="/attachments/refguide/version-control/on-premises-git/sign-in-dialog.png" alt="Sign In dialog" class="no-border" >}}
119+
{{< figure src="/attachments/refguide/version-control/on-premises-git/sign-in-dialog.png" alt="Sign In dialog" class="no-border" width="600">}}
120120

121121
1. Enter username (it can be anything except empty) and use the PAT you saved earlier as the password.
122122

@@ -221,7 +221,7 @@ After the import process is completed, your previously version controlled app wi
221221

222222
Note that your previous app still exists, **Studio Pro** will simply make an unversioned copy and upload it to your private Git server. So, in your **Recent Apps** list, you will still see both:
223223

224-
{{< figure src="/attachments/refguide/version-control/on-premises-git/recent-apps.png" alt="Recent Apps form" class="no-border" >}}
224+
{{< figure src="/attachments/refguide/version-control/on-premises-git/recent-apps.png" alt="Recent Apps form" class="no-border" width="600">}}
225225

226226
## Read More
227227

0 commit comments

Comments
 (0)