I'm a web developer/sysadmin/host (NERD TRIPLE THREAT!) and this is my attempt to write about...leaving the house. Sometimes. Like, to go backpacking. And take some pictures. And justify spending the money on all the gear WHY SO MUCH?!?
Feel free to write and complain.
So cPanel has a nifty tool that allows you to do DNS clustering. This lets you make changes to DNS and have them propagate to the other servers in the cluster.
One thing to remember, though: when you first run it you should make sure that
Synchronize zones that are not configured on this server
is checked or you will see some funky problems trying to send mail, etc. (funky as in 'lame nameserver' reports because part of your cluster only has incomplete records). Just because you see the proper records in cPanel's DNS editor does NOT mean the entire set of records is there. You need to also check
and make sure the items in question are present in both places.
So, you're trying to restore a web site backup using cPanel and you get the
Account Creation Status: failed (Sorry, a mysql user with the name blerg already exists.)
Account Restore Failed... Restore failed.
The solution (well, a solution) is to go into phpMyAdmin and check which database has the conflicting user. If you don't want to take the time to change usernames/configs (say, you're trying to restore several sites at once and time is of the essence), simply remove the account with the conflicting username and then restore your site backup. THEN restore the site you removed.
This has worked twice so far. It seems cPanel may sometimes not prefix MySQL usernames properly.
There are better ways to block brute force attacks against Wordpress (mod_security, carpet bombing), but if your host provider goes the .htaccess route then here are a couple of caveats to be mindful of.
First, pay attention to the order of statements. This
Allow from XX.XXX.XXX.X
Deny from all
won't work like you expect. You need to put the Allow statement at the end. In addition, there can be no space between
or again it will fail to work.
Using .htaccess can mitigate some small attacks, but it can quickly be overwhelmed so don't expect miracles. Sometimes you have to ride it out or employ other more drastic solutions (Special Forces, anthrax).
Working on a community web site can be rewarding. But it can also spiral out of control in a hurry. Well-meaning people (and those not so) empowered with tools to instantly reach a large audience on their own will still need guidance and support. As much as we'd like to believe that WordPress and all the rest make our lives as devs easier, it often is just the opposite. Yes, it's easy to update JUST ONE CLICK! but when that update causes a plugin to misbehave and OOPS WHITE SCREEN...you see the problem?
If you build a site like this -- especially volunteers -- then be prepared to support it indefinitely. You're name is going to be called whether to cast blame or beg for help. It's best to be there from the start to avoid both instances.
It's been standard practice for quite a while that domain registrars are allowed to block you from transfering your domain within 60 days of your registration renewal (this works either before or after). While this is inconvenient for users, it makes some sense for the registrars to keep excess churn at a minimum.
But did you know that the clock resets when you change your registration info? Specifically, first name, last name, or organization? Yup, at least with GoDaddy it sure does. Now, the common refrain is 'ICANN rules allow this'. I think ICANN rules also allow my dog to take a dump in the living room but it doesn't make it any nicer to clean up.
Now that I've been at this for nearly a dozen years, I find that I have often been less than efficient with how I fill the time between projects. (This really didn't take that long to figure out). I'm also not the greatest at hustling for work: salesmanship is not my strong suit.
So why not just jump into the deep end right off?
I had some experience with online job boards in the past. When I was just starting out it was mostly an exercise it being overwhelmed by the posted requirements: I didn't know a third of the acronyms, and the ones I was aware of were used in combinations I didn't understand (PHP OOP: how the hell do you do THAT?). Needless to say, this was very off-putting. If I didn't understand something, how could I possibly apply/bid/ask for it? That just wasn't fair to anyone. These job posters knew what they wanted and I wasn't going to be able to bluff them.
This time, however, things would be different: now I know plenty of acronyms. I am well-prepared with years of experience and tons of code under my belt. I CAN BUILD THINGS!
I noticed something new this time. Or maybe I was seeing it for what it was with the benefit of experience.
Many job posters really had no idea what they were asking for.
Code my portfolio site and launch it. Budget: $50
This was for a design firm. That builds web sites. For money.
I want to prevent the browser from closing when the user clicks the close button
I think the object of this is how to create a rage-filled sub-Reddit.
I want a site just like site X. Copy site X and put it on your server. Whoever does this gets the job
Really. I build it, leave it in plain sight, and you'll drop some coins in a fountain, maybe?
Perhaps these folks really do know what they want.
I love what I do. I love being my own boss and all that comes with that. Lunch at 11:30? no problem! Take a break at 2 to walk the dog? Go for it! Get distracted by a video of a cat playing with a laser NOT ACCEPTABLE GET TO WORK.
Trouble is, no one is here to say that.
So, why not try blogging? And not just go sign up for Blogger or install WordPress, but create a publishing system as I go along? THAT SHOULD FILL THE DAYS.