Dontyoudarenottobeaware

First of all, I like these little problems because they make me so much better with dealing with linux. And since its a hobby of mine, I cant really complain. Anyway, it took me a while to figure out that postgresql could not connect via the console because of some settings regarding authorization. Go to your pg_hba.conf and change from peer to md5 and you can login your database with your user and password. ----------------------------------------------------------- The second thing also troubled me a while and I was checking everything, because the log files did tell what was going wrong. passenger was running fine apache2 was set up ok, same with my virtual hosts and rvm was running wonderfully But I could not connect to my virtual hosts. And after a decent research on the internet and after quite a lot of message boards and posts I found the answer: check for the apache2/sites-enabled/default And there it was, these default files overwrote my virtualhosts an...

My centOS vserver broke down after a "yum update" and even the centOS community forum could not give an answer within 24h. In my books that is poor for the almighty and stable centOS. Bare in mind that I am just a normal user of linux, no professional and definitely no expert when it comes to server, but I can read, try and share my findings: debian 6 installation steps via ssh secure your server: adduser foobar for security purposes  change /etc/sshd/sshd_conf to PermitRootLogin no now you can login as foobar and change to root via su - visudo for sudo command permissions and put this at the bottom: foobar   ALL=(ALL) ALL change hostname change hostname in /etc/hostname and in /etc/hosts reboot login via rsa key rather than password locally do ssh-keygen ssh-copy-id -i foobar@hostname... ssh now works without passwords but with keys (for easy deployment) install ruby and rails via rvm login as root always good to have: sudo apt-get install...