| [11:50:05] | * zz_kvanderw is now known as kvanderw |
| [12:09:37] | * kvanderw is now known as zz_kvanderw |
| [12:10:00] | * zz_kvanderw is now known as kvanderw |
| [12:13:48] | * kvanderw is now known as zz_kvanderw |
| [13:11:51] | * fatguylaughing_ has quit (Quit: fatguylaughing_) |
| [16:04:16] | * ybabel has joined #aegir |
| [17:20:02] | * Shwele has joined #aegir |
| [17:24:07] | * Tirant_lo_Blanc has joined #aegir |
| [18:04:47] | * caldenjacobs[m] has quit (Ping timeout: 255 seconds) |
| [18:04:50] | * stephaniefuda[m] has quit (Ping timeout: 245 seconds) |
| [18:04:51] | * memtkmcc has quit (Ping timeout: 245 seconds) |
| [18:05:21] | * ergonlogic[m] has quit (Ping timeout: 240 seconds) |
| [18:25:08] | * memtkmcc has joined #aegir |
| [18:25:12] | * stephaniefuda[m] has joined #aegir |
| [18:27:45] | * ergonlogic[m] has joined #aegir |
| [18:29:46] | * caldenjacobs[m] has joined #aegir |
| [00:10:12] | * theMusician has joined #aegir |
| [00:27:13] | * fatguylaughing has joined #aegir |
| [00:36:15] | <fatguylaughing> | Morning |
| [01:04:12] | * Shwele has quit (Ping timeout: 252 seconds) |
| [01:35:08] | <fatguylaughing> | For anyone that may have had my problem… I fix it by going to the command line and running the git clone. This triggered the “Are you sure you want to continue connecting (yes/no)?” question. After saying yes to this, I was able to go back to the frontend and reverify the platform and it was able to clone. |
| [01:35:35] | <fatguylaughing> | Is there a way for the frontend of Aegir to present that question if needed? “Are you sure you want to continue connecting (yes/no)? yes” |
| [01:44:06] | <viashimo> | fatguylaughing: not as far as I know. I guess you could deploy the fingerprint to ~/.ssh/known_hosts in advance if you know it though. |
| [01:45:11] | <fatguylaughing> | viashimo: Darn |
| [01:45:26] | <fatguylaughing> | viashimo: Thanks for the help on the whitelist |
| [01:45:43] | <viashimo> | fatguylaughing: np |
| [01:59:35] | * theMusician has quit (Ping timeout: 240 seconds) |
| [02:38:04] | * theMusician has joined #aegir |
| [02:39:00] | * theMusician has quit (Client Quit) |
| [02:53:32] | * mutin-sa has joined #aegir |
| [02:56:02] | * theMusician has joined #aegir |
| [02:56:57] | * mutin-s has quit (Ping timeout: 240 seconds) |
| [02:59:16] | * theMusician has quit (Client Quit) |
| [03:13:10] | * theMusician has joined #aegir |
| [03:20:16] | * theMusician has quit (Quit: theMusician) |
| [03:29:50] | * theMusician has joined #aegir |
| [03:51:27] | * theMusician has quit (Quit: theMusician) |
| [04:01:23] | * shaneonabike1 has joined #aegir |
| [04:32:08] | * theMusician has joined #aegir |
| [04:34:38] | * theMusician has quit (Client Quit) |
| [04:41:58] | <colan> | fatguylaughing: i just ssh manually for the first time to get past that issue. |
| [05:06:35] | <fatguylaughing> | colan: Yeah, that’s what I did. However, if you don’t know you need to do such a thing, then you might be wondering in the dark. |
| [05:07:08] | <fatguylaughing> | colan: Would be nice for a “warning” message to display to inform the user they may need to look into that issue. |
| [05:09:02] | <colan> | Indeed. Maybe there's something we can do for this in the Web UI? |
| [05:09:21] | <colan> | Right, at the very least. |
| [05:36:56] | * ybabel has quit (Quit: ybabel) |
| [05:41:32] | * theMusician has joined #aegir |
| [05:41:36] | * Tirant_lo_Blanc has quit (Quit: Leaving) |
| [05:54:47] | * shaneonabike1 has left #aegir ("PART #drupal-commerce :PING 1531166087") |
| [06:54:25] | * theMusician has quit (Ping timeout: 248 seconds) |
| [08:09:26] | * fatguylaughing has quit (Quit: fatguylaughing) |
