Jul 062014
 

I’m working for the big chip company now, sound a little bit weird, though ๐Ÿ˜‰ .

Anyway, I’m sitting in backend team focusing on DevOps, I guess I will be in this mixed role till we find a dedicated DevOps guy. I guess whenever that happens, I’ve already finished monitoring facility (plus logistical stuffs like on-call schedule, etc.), and should have finished the plan to migrate from Rackspace to AWS.

Everything works smoothly so far except git – I admit current company is using git in a modern way, but I don’t think previous company was doing something wrong. Anyway, I believe people do have different ideas of how to use git, I just have to fit into the company’s style.

I don’t quite like saltstack although I’m still trying to get familiar with it. However, before I raise this as a concern to the team, I’d like to make sure everything that saltstack is doing can be done by cfengine.

Ah yea, also need to evaluate Shinken as it’s a pure Python solution, and “we are a python house”.

Oct 032013
 

I think it was in year 2005 or 2006 that I migrated everything from CVS to SVN, and it was the time that my company was doing that as well. Now I’m migrating to git, and of course, my current company is doing the same thing :P.

Guess everybody knows the reason … let’s say it’s offline support, that you don’t have to connect to sever to do commit. Further more, subversion does not work well on VirtualBox’s shared folder, while git has no problem at all, I guess people like me who needs to work on both *ix and Windows platforms have to have this kind of support.

And this is the time to see how many projects I have, WeirdBox is a great thing to keep thinking of I’ve play with the codes for several years, aws-browser is obviously another thing to keep thinking of it’s my first app on iOS and AWS (EC2 and S3), XMPP Mail Alert has to be migrated as I’m using it at this moment (for a friend’s web site). I cannot recall anything else but will post here if I find any.

And I’m using github, because of feel like safe? At least it’s not that vulnerable as other small players.

Aug 282013
 

Just leave a note here since I cannot recall this from time to time …

  1. git branch new_branch
  2. git checkout new_branch
  3. git push origin new_branch
  4. (git commit, git push, …)
  5. git checkout master
  6. git merge new_branch
  7. git push

Actually it’s pretty straightforward, but I just cannot memorize … especially step #3, sigh …