@XFS_Duke a bit of advice: stop posting...period.
By continuing to post you keep fanning the flames. I can't believe everytime I see a post of yours trying to answer the who's and what's.
You have nobody to answer to...this is your business and you should run it as you see fit.
Wow, thanks for the link. It loooks to be a real game changer.
Best part besides being free...two commands and the domain is setup with ssl!
Will defintaly give it a go for my personal sites, the business sites will require a "wait and see".
I agree with the posts above, it all depends on what platform/service you are trying to develop.
And what no love for C? If you are developing for the Unix/Linux platform knowing C is a must.
Just to add to the unattended update discussion.
I run unattended updates on all my servers, but unattended does not mean not monitoring the update.
All my unattended updates are run at a time when I know I will be present to intervene if needed.
I use screen for all updates so if the udpate...
I guess it depends on what you want out of the system.
But honestly to spend $75 dollars on a 35 AH battery seems excessive.
I would just go down to Walmart or a local big box store and pick up a pair of marine deep cycle batteries and wire them in parallel.
My batteries are 2X 109 AH units...
@MannDude Make sure you get a bank of deep cycle batteries.
You'd be surprised how much you can power with deep cycle batteries.
My UPS batteries are a pair of marine 12v deep cycle units that will keep my desktop computer with two monitors, and all the network gear running for about 8 hours...
I have never seen default policies at the end of an iptables script...they typically go at the beggining.
I don't know if that is the issue, but I would just move the below to the top of the script:
iptables -P INPUT DROP
iptables -P FORWARD DROP
Setup a cron job to run every day and update as necessary.
If not confortable with auto updates, then at least set up a script to query for udpates daily and update as needed manually.
I would run a script to tail the web server logs and check and make sure the IP hitting the server first made a request to a regular page of the site.
If the request went straight to a POST, then ban the IP.
You're blocking Googlebot, android and msnbot?
Edit: Just read that you block search engines.
Honestly, I don't even want to know the reasoning. But I would advice to remove these blocks from the tutorial...for the sake of the reader.