Tag: rhel5

Background

I am looking for a more flexible, faster Source Code Management system as development expands both in and out of house. Especially now with our increased use of Magento – some people are doing style sheets, some doing templates, some doing new scripts and still others code.

It’s increasingly difficult to manage with CVS alone. It’s damn near impossible to not make every site always the latest and greatest because branching and merging would make several heads explode.

Does git makes this easier in practice? Only one way to find out. And that’s to use it – and to use it, I gotta have it.

Installation

Get to a bash prompt, and get the latest tar bundle (1.6.5.2 as I write this) from http://www.git-scm.com. I like wget:

My need was to pull a text stream from Server B into Server A. It was actually an osCommerce problem: I need a plain text input to UnForm, our form-making software. At the time our backend system gets ready to print a pick ticket for warehouse personnel, I need the backend system to call back to the osCommerce database and grab the packing slip information.

This is due to a limitation in our backend software – we can’t store the part numbers the way they need to be displayed to the customer. The backend software is not an SQL-based solution, so cramming extra fields into the backend is a painful process.

However, we don’t have to: the data exists … drat, on the webserver. That’s OK. With a little ssh program execution we can do it, have it come back to us as text, or simply send the data to the TCP port UnForm is listening on, and let it work its form-making magic.

To get ssh to execute a remote without passing passwords:

Here I’m assuming you already have usernames on both servers, and both servers are RHEL5. If not, please see Mathias’ directions, as he has a few extra tidbits you may need.

1. Logon on to the server that you will be executing the ssh commands from, let’s call that Server A. There, you’ll create your authentication key pairs:

ssh-keygen -t rsa

2. Append the Server A’s public key to Server B’s authorized keys. You’ll of course be prompted for your password – for the last time.

cat .ssh/id_rsa.pub | ssh userB@serverB 'cat >> .ssh/authorized_keys'

3. Sign in to serverB, because you have to set the permissions correctly on the authorized_keys file: