Explore >> Select a destination
|
You are here 
|
blog.gnoack.org | ||
| | | | |
rolisz.com
|
|
| | | | | So the ML engineer presented the model to the business stakeholders and they agreed that it performed well enough on the key metrics in testing that it's time to deploy it to production. So now we have to make sure the models run reliably in production. We have to answer | |
| | | | |
zzamboni.org
|
|
| | | | | via http://www.freshblurbs.com/blog/2013/06/22/github-multiple-ssh-keys.html#tldr Since Github doesn't allow us to reuse an SSH Key, the only sane solution is to jump through some hoops and generate + use multiple keys on the server itself. Let's look at some effective approaches of doing that. Short version: define multiple hosts in the SSH config file for each repository, which use different SSH keys, then you can assign different deploy keys to each repo. But read the whole article for the full details. | |
| | | | |
sookocheff.com
|
|
| | | | | This is something I often do but rarely remember the steps for. This post is intended to serve as a reminder for me and anyone else having the same question: how to add an upstream remote git repository. Start by forking the repository you are contributing to and cloning that repository to your local file system. In this example, we will use the Elasticsearch repository and assume you have cloned it locally. | |
| | | | |
iwriteher.com
|
|
| | | ©TheModernMet/Pinterest I was absolutely blown away by these few simple verses that so powerfully speak to the effects of having lived thoroughly. Thank you for taking my breath away, Carolyn! Haiga #97 | ||
