Skip to main content

Git push to production machine

Application: I have code on my development machine that is under git. I would like to be able to send this code to my production machine when I'm ready. One way is to have a repository, say on github or bitbucket, and push from my devel machine and then pull from my prod machine. But sometimes the code is very specific and I'm not sharing it publicly. And, this is a kind of cumbersome two step process. Can we automate this process?

Solution (From discussions here and here): 


On production machine
---------------------
mkdir wm.git
mkdir wm
cd wm.git
git init --bare
create a file: hooks/post-recieve
---------------------------------
#!/bin/sh
GIT_WORK_TREE=/home/kghose/Research/wm git checkout -f
chmod +x hooks/post-receive
On devel machine under the repository
-------------------------------------
git remote add production ssh://kghose@172.17.146.192/home/kghose/Research/wm.git
git push production master:master
view raw gitautocheckout.txt hosted with ❤ by GitHub
The basic idea is to set up a git repository in the production machine (wm.git) and indicate that as a remote. When you push, wm.git gets updated with the code that you push. The magic happens in the hook/post-receive script which gets executed on the production machine after a push, so you do not have to manually checkout the latest push.

Labels

Labels:

Comments

Post a Comment

Popular posts from this blog

A note on Python's __exit__() and errors

Python's context managers are a very neat way of handling code that needs a teardown once you are done. Python objects have do have a destructor method ( __del__ ) called right before the last instance of the object is about to be destroyed. You can do a teardown there. However there is a lot of fine print to the __del__ method. A cleaner way of doing tear-downs is through Python's context manager , manifested as the with keyword. class CrushMe: def __init__(self): self.f = open('test.txt', 'w') def foo(self, a, b): self.f.write(str(a - b)) def __enter__(self): return self def __exit__(self, exc_type, exc_val, exc_tb): self.f.close() return True with CrushMe() as c: c.foo(2, 3) One thing that is important, and that got me just now, is error handling. I made the mistake of ignoring all those 'junk' arguments ( exc_type, exc_val, exc_tb ). I just skimmed the docs and what popped out is that you need to return True or...
Post a Comment
Read more

Store numpy arrays in sqlite

Use numpy.getbuffer (or sqlite3.Binary ) in combination with numpy.frombuffer to lug numpy data in and out of the sqlite3 database: import sqlite3, numpy r1d = numpy.random.randn(10) con = sqlite3.connect(':memory:') con.execute("CREATE TABLE eye(id INTEGER PRIMARY KEY, desc TEXT, data BLOB)") con.execute("INSERT INTO eye(desc,data) VALUES(?,?)", ("1d", sqlite3.Binary(r1d))) con.execute("INSERT INTO eye(desc,data) VALUES(?,?)", ("1d", numpy.getbuffer(r1d))) res = con.execute("SELECT * FROM eye").fetchall() con.close() #res -> #[(1, u'1d', <read-write buffer ptr 0x10371b220, size 80 at 0x10371b1e0>), # (2, u'1d', <read-write buffer ptr 0x10371b190, size 80 at 0x10371b150>)] print r1d - numpy.frombuffer(res[0][2]) #->[ 0. 0. 0. 0. 0. 0. 0. 0. 0. 0.] print r1d - numpy.frombuffer(res[1][2]) #->[ 0. 0. 0. 0. 0. 0. 0. 0. 0. 0.] Note that for work where data ty...
Post a Comment
Read more