We encrypt SSH keys and OAuth tokens, the most private data that's entrusted to our systems. Of course, the keys aren't stored in the database.
When buying infrastructure rather than building it, keep a good eye on what your providers do and how they handle security and your data. This is just as important as handling outages, if not even more so.
Make sure that your privacy/security statements reflect which services you're using and how you handle your customers' data …
…cluster nodes, install software and monitor them. Therefore, this control node needs to have access with SSH to all other nodes. That's the reason we can upload an SSH private key. It is recommended that all 5 servers can connect to each other with passwordless authentication (root user) using an SSH key.
Now we have two options. Just deploy the cluster from the web interface or generate an installation package. We are going to use the second option so we can see what it does under …
…final issue, which is rather niche: My newsreader gnus connects to my NNTP feed via a SSH hop. The configuration looked like this: (setq gnus-select-method '(nntp "localhost" (nntp-address "myshellhost") (nntp-rlogin-program "ssh") (nntp-open-connection-function nntp-open-rlogin) (nntp-end-of-line "\n") (nntp-rlogin-parameters ("nc" "mynntpserver" "nntp")))) …
…the credential management to support different setups . Currently Samus does rely on SSH keys being available on the machine for Git commands. I would like to fix that.
Self-contained releases could be useful . Right now you still need some local setup to use Samus, like credentials on your machine, and occasionally some binaries (custom commands, if you use them). Being able to build a self-contained archive with all the custom commands and credentials in the zip would make publishing …
SSH'd to my hosting server, set up a bare git repo ( git init --bare )
Back on my local machine, set up the git remote, and pushed to my hosting site
SSH'd back to my hosting server, and copied the post-receive.sample to post-receive
Copied giflister into the new hook
cloned the bare repo into a real repo (at ~/nanoc )
Made sure the paths etc in the post-receive hook were accurate
Ran it once to see that it worked
Tried a git push from my local workstation …
Create your SSH Key
Introduce yourself to Git
Add some additional Git settings
Set up your GitHub account
Follow a Friend
Creating a new repository
Deleting and renaming repositories
Fork a repository
Push changes to a repository
Clone a public project
Add collaborators to a project
Collaborate with other users
Send a pull request
Merge changes from a pull request
Use project wikis
Create and delete branches and tags …
SSH into your new instance.
Fetch the EPEL repository definitions from the Fedora Project - the RightScale image I am using included some EPEL settings so I disabled them (by editing the .repo files, an exercise for the reader!) in favour of using the direct EPEL release rpm -ivh http://www.mirrorservice.org/sites/dl.fedoraproject.org/pub/epel/5/i386/epel-release-5-4.noarch.rpm
Update the box yum -y update
Pull down the ISO image of Elastix - i'm using the latest stable …
…deploy directly toif unit tests pass - no need to use or manage SSH keys
Move slugs around between Heroku apps, for example to promote a release on a staging app to a production app
Are you a CI service provider, source code repository provider, or just a plain old hacker interested in the opportunities this opens up? We want to work with you, get in touch with firstname.lastname@example.org .
The slug and release endpoints complete the functionality that we plan to expose …
…add-on to the enterprise version that allows users to initiate actions on a node without requiring SSH access; we call this feature Push Jobs. Right now, Push Jobs (formerly known as Pushy) are a feature of Enterprise Chef, but we are working towards open sourcing Push Jobs in early 2014 (think Q1).
Getting started with Push Jobs is fairly easy. There are 2 additional components that need to be installed, the Push Jobs server and the Push Jobs clients. The Push Jobs server …
…serverspec that sets it apart from Aruba is it can test things locally and remotely via SSH.
This is useful when testing automation that creates servers somewhere: run the tool, connect to the server created, verify conditions are met.
But what happens when we want to test the behaviour of tools that create things both locally and remotely? For local testing Aruba is awesome. For remote testing, serverspec is a great fit.