Dontyoudarenottobeaware

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...

I found this nice page explaining mailman as subdomain: My Mailman Virtual Hosting List Setups But I found this to be too redundant compared to the default settings already been done by the installings process of mailman with postfix. And there were even some people working with HTML-Header-Redirects in subfolders for their virtualhost. I just did this in /etc/httpd/conf/httpd.conf <VirtualHost *:80> ServerName lists.mysite.com ServerAlias lists.mysite.com RewriteEngine on RewriteRule ^/mailman[/]+$ http://lists.mysite.com/mailman/listinfo [L,R] RewriteRule ^/$ http://lists.mysite.com/mailman/listinfo [L,R] </VirtualHost> Of course there were the RedirectMatch for /mailman/ in place; as well as the changes for the hosts in mm_cfg.py and postfix/main.cf like the link above shows. Mailman had to be initialised again, but then it worked all fine. Before going to smash something though, test your mailserver with: mail %TO_ADDRESS% ...

In this post I will show how to configure several virtual hosts on a linux machine, that will function as subdomains with their own DocumentRoots. Goal: access your site via blog.mysite.com access a different site via test.mysite.com allow different app to be accessable via mysite.com/app1 First you will have to redirect any traffic to a virtual host on port 80: NameVirtualHost *:80 From now on every 'html' traffic is redirected to your following settings; and have in mind that you former DocumentRoot is overridden. (the last caused me some troube/time) Now set up some subdomains: <VirtualHost *:80> ServerName blog.mysite.com ServerAdmin webmaster@mysite.com DocumentRoot /var/www/html/blog <Directory /var/www/html/blog> Options Indexes FollowSymLinks MultiViews AllowOverride All Order allow,deny allow from all </Directory> </VirtualHost>  <VirtualHost *:80> Server...