I've been attempting to clone a repository from GitHub, but haven't quite figured out where I'm going wrong.
I have a .build file that references my .make file, found in my repository, though it cannot clone the repo.
I've tried using just the .make file to build from, and that seems to work, but I need it to use the .build file to reference the repo to pull the profile from.
Does anyone have a "best practices/how-to" on this?
The error message from the UI on adding a platform:
drupal downloaded from http://ftp.drupal.org/files/projects/drupal-7.26.tar.gz.
Unable to clone leviathan_skeleton from ssh://git@github.com/:narcissus921/leviathan_skeleton.git.
Command dispatch complete
Peak memory usage was 13.22 MB
Could not download platform using drush make. No platform present
Comments
Pubkey?
Sorry if this answer is too obvious, but it's worth double-checking. Did you give Github the pubkey for SSH access to your server?
Jim,I did, for my root
Jim,
I did, for my root account, in /root/.ssh/
I then added that to GitHub, though it still failed. Should I be creating an SSH key for o1.ftp, o1, or just my root aegir account?
I created the key as Aegir, then added the public key to Github.
Yes
Yes. You will need a key for each Octopus installation using the .ftp account.
No. There is only one SSH pub
No. There is only one SSH pub key you should use, and it is already generated for your convenience. You can find it in /data/disk/USER/static/USER.id_rsa.pub and also in /data/disk/USER/.ssh/id_rsa.pub
Note that it is an Aegir backend user related, not your .ftp user and not a root.
BOA even adds some known services in the /data/disk/USER/.ssh/known_hosts automatically.
That said, it is recommended to run drush make on command line and not via Aegir interface. At least during debugging, so you can run it with -d flag. It is also important to note that on command line you can use drush6 make, while Aegir will use the legacy drush4, so it may not work, depending on how you have built your drush make stub file.
[EDIT] Of course, if you will run the drush make on command line, and the remote repo is private, so it needs a key, then you need to create and use SSH pub key related to your USER.ftp account, as Jim mentioned above.
Thanks for the clarification
Thanks for the clarification and recommendation on running drush make.
interesting
Sorry to have offered incorrect information. The USER pubkey is new to me. Generating one for USER.ftp had worked for me when cloning a repo in the /static directory.
interesting
Sorry to have offered incorrect information. The USER pubkey is new to me. Generating one for USER.ftp had worked for me when cloning a repo in the /static directory.
interesting
Sorry to have offered incorrect information. The USER pubkey is new to me. Generating one for USER.ftp had worked for me when cloning a repo in the /static directory.
interesting
Sorry to have offered incorrect information. The USER pubkey is new to me. Generating one for USER.ftp had worked for me when cloning a repo in the /static directory.
[Edit] Apologies also for the multiple posts. My tablet is not cooperating this morning.
@JimSmith - Your suggestion
@JimSmith - Your suggestion is absolutely correct when running drush make on command line and there is remote private repo referenced in the makefile. But if you would use the Aegir built-in option to use makefile when creating a platform, the correct pub key is that one provided by BOA for your backend/system user.