Go back

Setup and installation of 'Gitness: Selfhosted, Private & Secure Opensource Github alternative' on GCP



This section describes how to provision and connect to ‘Gitness: Selfhosted, Private & Secure Opensource Github alternative’ VM solution on GCP.

  1. Open Gitness: Selfhosted, Private & Secure Opensource Github alternative listing on GCP Marketplace

  2. Click Get Started.

/img/gcp/gitness/marketplace.png

It will ask you to enable the API’s if they are not enabled already for your account. Please click on enable as shown in the screenshot.

/img/gcp/nvidia-ubuntu/enable-api.png

  • It will take you to the agreement page. On this page, you can change the project from the project selector on top navigator bar as shown in the below screenshot.

  • Accept the Terms and agreements by ticking the checkbox and clicking on the AGREE button. /img/common/gcp_agreement_page.png

  • It will show you the successfully agreed popup page. Click on Deploy. /img/common/gcp_agreement_accept_page.png

  • On deployment page, give a name to your deployment.

  • In Deployment Service Account section, click on Existing radio button and Choose a service account from the Select a Service Account dropdown.
  • If you don't see any service account in dropdown, then change the radio button to New Account and create the new service account here.
  • If after selecting New Account option, you get below permission error message then please reach out to your GCP admin to create service account by following Step by step guide to create GCP Service Account and then refresh this deployment page once the service account is created, it should be available in the dropdown.

  • You are missing resourcemanager.projects.setIamPolicy permission, which is needed to set the required roles on the created Service Account
  • Select a zone where you want to launch the VM(such as us-east1-a)

  • Optionally change the number of cores and amount of memory. ( This defaults to 1 vCPUs and 3.75 GB RAM)

  • Optionally change the boot disk type and size. (This defaults to ‘Standard Persistent Disk’ and 30 GB respectively)

  • Optionally change the network name and subnetwork names. Be sure that whichever network you specify has ports 22 (for ssh), 3389 (for RDP), 80 (for HTTP) and 443 (for HTTPS) exposed.

  • Click Deploy when you are done.

  • Gitness: Selfhosted, Private & Secure Opensource Github alternative will begin deploying.

/img/gcp/gitness/deployed-01.png

/img/gcp/gitness/deployed-02.png

/img/gcp/gitness/deployed-03.png

  1. A summary page displays when the compute engine is successfully deployed. Click on the Instance link to go to the instance page .

  2. On the instance page, click on the “SSH” button, select “Open in browser window”.

/img/gcp/rancher/ssh-option.png

  1. This will open SSH window in a browser. Switch to ubuntu user and navigate to ubuntu home directory.
sudo su ubuntu
cd /home/ubuntu/

/img/gcp/rancher/switch-ubuntu-user.png

  1. Change the password for ubuntu user using below command
sudo passwd ubuntu

/img/gcp/jupyter-python-notebook/ssh-passwd.png

  1. Now the password for ubuntu user is set, you can connect to the VM’s desktop environment from any local windows machine using RDP or linux machine using Remmina.

  2. To connect using RDP via Windows machine, first note the external IP of the VM from VM details page as highlighted below

/img/gcp/rancher/public-ip.png

  1. Then From your local windows machine, goto “start” menu, in the search box type and select “Remote desktop connection”

  2. In the “Remote Desktop connection” wizard, paste the external ip and click connect

/img/gcp/rancher/rdp.png

  1. This will connect you to the VM’s desktop environment. Provide “ubuntu” as the userid and the password set in step 6 to authenticate. Click OK

/img/gcp/rancher/rdp-login.png

  1. Now you are connected to out of box Gitness: Selfhosted, Private & Secure Opensource Github alternative VM’s desktop environment via Windows machines.

/img/azure/minikube/rdp-desktop.png

  1. To connect using RDP via Linux machine, first note the external IP of the VM from VM details page,then from your local Linux machine, goto menu, in the search box type and select “Remmina”.

    Note: If you don’t have Remmina installed on your Linux machine, first Install Remmina as per your linux distribution.

/img/gcp/common/remmina-search.png

  1. In the “Remmina Remote Desktop Client” wizard, select the RDP option from dropdown and paste the external ip and click enter.

/img/gcp/common/remmina-external-ip.png

  1. This will connect you to the VM’s desktop environment. Provide “ubuntu” as the userid and the password set in step 9 to authenticate. Click OK

/img/gcp/common/remmina-rdp-login.png

  1. Now you are connected to out of box Gitness: Selfhosted, Private & Secure Opensource Github alternative VM’s desktop environment via Linux machine.

/img/azure/minikube/rdp-desktop.png

  1. To connect to Gitness UI, copy the Public IP of the VM and paste it in your Browser and hit enter. For the first time Browser warning will show up. Click on advance, accept the risk and continue to login page.

/img/gcp/gitness/browser-warning.png

  1. When accessing the UI first time, you need to sign up to create the first user. The first user created will automatically become admin user here.

/img/gcp/gitness/login-page.png

On login page, click on Sign up link. Provide the sign up information and hit enter.

/img/gcp/gitness/signup-page.png

  1. Now you are connected to Gitness UI with admin user.

/img/gcp/gitness/home-page.png

  1. Create new project or export your existing project here and explore Gitness’s features.

/img/gcp/gitness/create-new-project.png

/img/gcp/gitness/new-project.png

  1. By default, anyone having access to Gitness VM UI can click on “Sign Up” link on login page or goto https://vmpublicip/register page and create a user. If you want to disable this behavior and want only admin to be able to create/signup new user, then follow the Disable/Enable User Signup page.

For more details on Gitness please refer to Gitness official documentation page

Go back