poisonbit's comments

In Europe, consumers are persons and have rights.

In some issues, consumer rights have the same importance than big-fat-company.

I don't know if in other continents everybody is pro unscrupulous vendors.

Greetings.

My book (I do not own an startup, sorry):

"You pass from have driver problems in kernel with local devices, to have driver problems in kernel with remote devices. You forget about bios updates, hot air in the CPD, ordering cords and track hardware life-cycle and status." :)

Why amazon? why chef? why puppet? why don't something like:

http://devcenter.heroku.com/articles/node-js

Try to avoid the need to learn and use daily ruby+python+node+AWS+nagios+O.S.foo`(now make a tree of sub-packages of each one) and just focus in your startup node.js code, and just in npm, and not 5 package managers + the distro one.

If I where you, I could just focus in one technology. You do not need to master puppet+chef+AWS to mantain 2 servers or 20 equal servers. It can be passed with ssh+rsync+a bunch of scripts.

They are nice tools... but... is that the focus of your startup ?

Do you need to manage a complex network with many different operative systems (vendor and version), configurations and policies ? or just a production and a developmen node.js environment ?

Has the startup resources, for a person full time, learning to mantain systems? how many systems are needed? how many changes or daily operations in the systems are needed?

There is no "a book" about that. System administration is about practices, policies, know-how and data management, organization, etc.

I don't know a single book that covers all the topics that you may reach doing "AWS+chef/puppet+node.js+monitoring (+DNS, +SSL, +backup, +availability, +tunning, +etc)" sysadmin/devop may reach in a single day/week/month/year.

From this kernel module option that is better because of scenario A, to this api change from last month on sub-package X, or this 0day exploit for service Foo, or this opensource-bug on feature that our plan was relaying, or...

I will not give you book links, but I will give a tip for all those playing to be sysadmin:

   Avoid if possible
   Backup everything
   Test everything (Outside production).
   Do it really.
   Be prepared for everything.
   Do it really.
   Do not blame things until you write something better.

Depends on the size and activity of the business.

Maybe there is no need for a 100% time sysadmin, maybe there is need for 30 sysadmins across different time zones.

But that's not now, that has been always like that.

http://poisonbit.wordpress.com/2011/02/18/opensource-clouds-...

It seems I thought wrong. Drama.

I don't use to use social networks, but as a hobby time "open source" coding project, I thought that post it to some place like this was a good idea to get some community feedback.

err... formating issue, delete the '\' chars for a single line.

You can turn all that elifs on prompt.sh into a case/esac.

I've returned to screen from tmux, since it manages vertical split. I've something similar for auto-screen. But my configuration avoids nested screen sessions (i.e. ssh to host A, and then from host A to host B, both with the same .bashrc configs), like this:

[[ -x $( type -P screen ) ]] && \ [[ -n "$SSH_CONNECTION" ]] && \ [[ "x$TERM" != 'xscreen' ]] && screen -dR

Codes exhausted... anyway nice to read this.

DotCloud++ Miyagawa++ Perl++

Good luck !