For the past three weeks I've been working on my personal iMac, developing a graphical analysis. It was already linked to a GitHub repository, but I kept working locally until I had something substantial to push up to GitHub. Today I tried to push the changes to GitHub and got the message that GitHub no longer supports https: with password authentication.
No problem, I thought. I already had ssh setup and was using it for non-R projects. So, snooping around the Internet, I came across instructions such as these and changed the urls from https to ssh.
But somewhere along the way, RStudio decided to gray out the buttons for Pull & Push under the Git tab.
How does one reactivate the buttons?
Make sure first your SSH URL works from command line:
ssh -Tv git#github.com
cd /path/to/local/repo
git remote -v # do you see an SSH URL git#github.com:<me>/<myrepo>?
git ls-remote # do you see remote branches SHA1?
Then, you would need to reference your private key in your RStudio settings
Related
While I am trying to push on GitHUb from rstudio it is stuck and is not reflecting on Github
There might be some mismatch in the settings that I have configured watching tutorials.
Error Screenshot
Git Settings
Rstudio Options
GitHub Account Settings
Repository Settings
I was facing the same issue while following one of the courses online. I don't know exactly what causes this issue.
Problem: Exactly the same with every setting as shown in the screenshot.
The solution:
in RStudio, click on the "Tools" menu and select "Shell"
Run the following command: git push
it might ask you for your git username and password. Supply this
information, make sure it is correct
hopefully, the push is successful, then you can close the window
Now make some more edits to some files so that you have new content to
push
Click on the "push" button in RStudio and this time the push should
work
This is not my solution I found it here: https://stackoverflow.com/a/45804117/5677883
I am struggling with Github and Rstudio. I don't know Github very well and I find the commands very confusing.
I read that Github preferred default branch should now be main and not master anymore. So I created my repository and followed instructions for creating a main branch.
First question:
do I need to use main as default branch to create an R package for download? I see that devtools::install_github still has master as default, so I am puzzled because Hadley and his group are usually very reliable.
I set Rstudio both local and origin to main. However, no matter what I do, Rstudio will always push to master (and recreate it if I deleted it) with the command push origin HEAD:refs/heads/master. (why is this command using HEAD:refs... and not just push origin master? If this is the problem, how do I change Rstudio's default?)
I tried git symbolic-ref refs/remotes/origin/HEAD refs/remotes/origin/main from bash to no avail. I can push to main manually with git push origin main but then Git starts nagging that master is behind. This command really pissed off git git config --global push.default main.
Second question:
How do I set Rstudio to push to main (or to both master and main)?
I am using a file from GitHub
It has a vagrant file with it. When I run vagrant up command in my terminal, I get an error.
The terminal should show READ ABOVE message when successful download
I want to type in the address to the site on my browser to start a local development server.
Its pretty old file and the repo was using puphpet but this project seems dead for 2 years, the website is down.
In your case, vagrant is trying to download the box from internet but the owner of this box hosted it under the puphpet domain not available anymore
I am not sure what's the best way to help now:
find another more recent example and start from there
if you want to fix this, you will need https://github.com/LearnWebCode/vagrant-lamp/blob/master/puphpet/config.yaml#L6 and use a different box available on vagrant site, ubuntu 16.04 is pretty old now but you can search one from vagrant box
I cannot ssh into my Google Compute Engine (GCE) Wordpress instance anymore.
It was working one month ago when I tried last.
I use the Google built-in SSH client in a Chrome browser window.
Yesterday I tried an got the following message:
The VM guest environment is outdated and only supports the deprecated
'sshKeys' metadata item. Please follow the steps here to update.
The "Steps here" link navigates to https://cloud.google.com/compute/docs/images/configuring-imported-images#install_guest_environment which does not seem to help me much.
I am not aware of any changes that I may have made.
How can I fix this?
It looks like your instance's disk is full, and so the SSH keys can't be created in the temp directory. You can do the following:
Stop your instance and wait for it to shut down
Click on the disk your instance is using, and choose "edit" at the top
Enter a larger disk size, and save
Go back to your instance and start it up again
You should now be able to connect via SSH. While you're in there, check to see what filled up your hard disk so you can prevent this from happening again (maybe a rogue program is printing out too many logs, etc).
If you're seeing this on Debian 8 or 9, the most likely reason for this is that the google-compute-engine.* packages that allow SSH access to the instance have been removed by apt-get autoremove.
If you have an open SSH connection to the machine or can use a tool like gcloud, running apt-get update && sudo apt-get install gce-compute-image-packages should fix this.
If you no longer have any SSH access, there is a procedure available on the GCP docs site that can be used to restore it.
I've created a bug report here for this.
Might be a bit late, but you can
1) Stop the VM
2) Edit and enable serial console
3) Use the serial connection to login and update the VM
recent days, I meet similar problem, later I find the permission rights of my home directory fools me, as a lazy-bone, I chmod 777 ~
After did that, I cannot ssh via my terminal, even cannot ssh via browser, only get 'The VM guest environment is outdated and only supports the deprecated 'sshKeys' metadata item, Plese follow the steps here to update'. Sounds like you must set 755 to your home dir, not just care your 700 .ssh or 600 authorized_keys.
I met the similar issue after I created a FreeBSD VM, gcloud ssh not works, but I am lucky that I can use the browser window ssh to my VM. Then I manually add the google_compute-engine public key to the .ssh/authorized_keys, now it work, I can use the gcloud ssh to connect. But not sure if this is a better/security way.
In the pursuit of a more professional WordPress dev and deployment environment I am trying to use Capistrano to deploy from my local dev environment to staging and production servers but I can't quite get it to work.
I am on Site5 shared hosting and am deploying to one server with two different domains - staging.example.com and example.com.
I have used https://github.com/markjaquith/WP-Stack as a basis and have added
set :user, "myserveruser" to my config.rb file as the connection didn't work without that.
Running cap deploy:checktells me "You appear to have all necessary dependencies installed" and I can run cap deploy:setup which successfully connects to staging and production creating releases and shared directories etc.
The problem comes when I run cap deploy. Everything seams to work fine until I am prompted for a sudo password. This is not a normal login prompt though and does not allow me to type a password. As I am on a shared host I don't have sudo access anyway.
Its similar to this problem Capistrano is hanging when prompting for SUDO password to an Ubuntu box but the solutions didn't fix all my issues.
I have set default_run_options[:pty] = true which I seam to need but still get the sudo prompt.
I am using passwordless ssh so Capistrano is able to connect and do everything it needs to do without prompting for a password and I am also using an SSH config file to handel agent forwarding so the server can also connect to my git repository. I have confirmed this is working.
I have found other people having similar problems - Capistrano using sudo even with "set :use_sudo, false" - etc but none of the solutions have worked.
I am using default_run_options[:pty] = true and have tried using set :use_sudo, false and default_run_options[:shell] = false but I still have the same issue.
You can view my Terminal output here - http://pastebin.com/5xZmCnyA
I am seriously going crazy! Any help would be greatly appreciated!!!
Cheers
You can't run setup without sudo. That's the only part that REQUIRES sudo, because it makes a directory public_html/staging.exposecreative.org, in your case...
That step shouldn't be required, you can make that directory yourself (assuming you have permission)..
The problem you will face however is that the shared host will expect your index.php to be directly in public_html, for that to work you'd need write permission to whatever directory public_html is in, which your shared host won't allow (almost certainly)
The line default_run_options[:pty] = true has to do with whether Capistrano pretends to be an interactive shell or not. Many commands (sudo included) use this to determine if they should bother asking the user for input, or if they are part of an automated process (
in which case there's no way to ask for input)
My advice (as Capistrano maintainer) - don't try this on a shared host, it almost certainly won't work. (Sorry, their limitations, not ours)
I wrote an extensive post on how to deploy WordPress with Capistrano on a shared host (Bluehost). I use the Roots/Bedrock stack and it only took me about 20 minutes to get up and running.
I made a WordPress development stack using Shipit JS instead of Capistrano because I'm not comfortable with Ruby. Maybe that can help. Feel free to use it and/or post some issues if needed. Regards.
WP-Jungle / Bonzai