although i own this domain, i have never really used this domain apart from this blog. which actually means although i have administrator powers, i never really use them. i have no freaking idea how to do more then set up ftp access, subdomains, mysql databases and emails.
one of the reasons i seldom access my control panel is that i have no idea what the other functions are for. i’m freaking terrified of messing around with stuffs i don’t know. anyway, something happened last night that reinforced that.
so the fgb asked me to help him set up a subdomain for the purpose of testing out wordpress mu. i thought it was a simple matter and actually it was. i mean, ftp access, a subdomain and a mysql database for the wordpress mu. how hard could it be? it’s something i have to do even to set up this subdomain for my blog.
well. fgb asked if it was possible for me to enable him to create a sub subdomain. he then linked me a knowledge base article on what to do to enable it. it was simple. just open a support ticket with my webhost and that’s it.
simple yeah? and i screwed it up. haha! all i had to do was simple. get my hosting company to add
ServerAlias *.subdomain.soliloquy.us
on to my domain’s httpd.conf file. nothing else. instead, what i did was ask them to add
ServerAlias *.soliloquy.us
instead. this affected ALL my current subdomains, thereby killing this blog. i panicked for a while before realising what exactly was wrong. i then opened another support ticket to get things back the way it was before.
thankfully, it was easy to do so. heh. moral of the story? before messing around with what i don’t know, i will make sure to not only read the manual and documentations but to bloody understand what i am doing before even attempting. some stuffs you can get away by reading the FAQs midway into the procedure. some other stuffs can only be done once and if you screwed it up, that’s it. as an example…
rm -rf
never ever try that as root.