Conversation
supportHello, I just installed this plugin to test. At the Configuration step 1 I fill in the remote URL. I use https://Rowdysign@bitbucket.org/Rowdysign/git_test2.git and then, if I press “Fetch” I get the following error: “Could not push to remote: https://Rowdysign@bitbucket.org/Rowdysign/git_test2.git ERROR: s:95:”fatal: could not read Password for ‘ https://Rowdysign@bitbucket.org’ ;: No such device or address”;” If I am using SSH: git@bitbucket.org :Rowdysign/git_test2.git I get the following error: Could not push to remote: git@bitbucket.org :Rowdysign/git_test2.git ERROR: s:125:”fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists.”; I don’t know what to fill in at “Key pair”. Some help would be appreciated.
Hello @rodricus , Can you try the following steps After activation, go to the Gitium settings in your WordPress admin area. Copy the Public Key that Gitium has generated for you from the Key Pair field(you can press regenerate key pair). In your repository manager of choice (GitHub, GitLab, or Bitbucket), go to the settings page and find the “Deploy keys” (or similar) section. There you will need to add the Public Key you’ve copied from Gitium. This will grant Gitium access to your repository. Make sure to allow write access as well. Also make sure that you copy the entire key from gitium. Now go back to your main repository page and copy the SSH URL to your repo. Paste this URL in Gitium and press the “Fetch” button. A “Repository initialized successfully” message will show up. This means that your repository has been populated with the current code of your website and it is ready to start working with Gitium. Webook configuration: Gitium uses the webhook to automatically deploy remote changes to your server. To configure it follow these steps: Go to your WordPress website and go to your Gitium Settings page; Copy the full Webhook URL that Gitium provides; In your Git Manager settings, go to Webhook section, add a new webhook and paste the webhook URL you have copied from Gitium. Press Add, no settings changes needed. The webook simply needs a ping, nothing more. The security key is already embedded in the final URL Gitium has generated for you. Now when you push to your repo, this webhook will automatically pull the changes to your remote server and deploy them.
Hello, thank you very much, it worked.
Alright, thank you for your confirmation!
Hello @rodricus , Can you try the following steps After activation, go to the Gitium settings in your WordPress admin area. Copy the Public Key that Gitium has generated for you from the Key Pair field(you can press regenerate key pair). In your repository manager of choice (GitHub, GitLab, or Bitbucket), go to the settings page and find the “Deploy keys” (or similar) section. There you will need to add the Public Key you’ve copied from Gitium. This will grant Gitium access to your repository. Make sure to allow write access as well. Also make sure that you copy the entire key from gitium. Now go back to your main repository page and copy the SSH URL to your repo. Paste this URL in Gitium and press the “Fetch” button. A “Repository initialized successfully” message will show up. This means that your repository has been populated with the current code of your website and it is ready to start working with Gitium. Webook configuration: Gitium uses the webhook to automatically deploy remote changes to your server. To configure it follow these steps: Go to your WordPress website and go to your Gitium Settings page; Copy the full Webhook URL that Gitium provides; In your Git Manager settings, go to Webhook section, add a new webhook and paste the webhook URL you have copied from Gitium. Press Add, no settings changes needed. The webook simply needs a ping, nothing more. The security key is already embedded in the final URL Gitium has generated for you. Now when you push to your repo, this webhook will automatically pull the changes to your remote server and deploy them.
Hello, thank you very much, it worked.
Alright, thank you for your confirmation!