Welcome to www.minisinbox.com

Web Hosting - How To Select A Web Host As with many purchases, our first impulse when selecting a web hosting company is to go with the cheapest. Hey, they're all alike, why pay more? Au contraire. There are a number of objective criteria that separates one web hosting company from another and money is only one of them. And not the most important one. Selecting a company based on price alone is equivalent to selecting an auto mechanic on price alone. Sure, he may maintain or fix your car cheaper. But will the car spend all the time in the shop and none on the road? The first consideration is 'horsepower'. Do they have the capacity to carry your load and deliver decent performance? Most hosting companies will advertise that they have huge bandwidth and hundreds of servers. They're usually telling the truth. But there's a difference between existing capacity and usable capacity. If they also have thousands of sites with millions of visitors per day the available or free capacity will be much lower. A big pickup truck may be able to tow 5,000 lbs. But not if it's already carrying 4,999. Be sure to ask about available capacity, and have the prospective company back it up with reliable numbers. If you can't interpret the information they provide, find someone to help you do so. Next, and a very close second, is reliability. A lot of power is worthless if it's cut often. Outages are a normal part of business. Even Google and Microsoft go down from time to time. The difference is, it happens rarely and they have failover plans. That means, if their site/system does go down it's either up again in a flash, or you never see the outage because a backup system kicks in automatically and seamlessly. Be sure to grill the company closely about their up time. They'll often tout 99.6%, or some such figure. But, like the on-time figures of the airlines, those numbers can be shaded by adjusting the definition of 'up time'. What matters to you is whether your visitors will be able to reach your site at any time of the day or night they might want to. Find out what systems, both technical and human, they have in place to deal with failures of all sorts. Servers can go down, networks can fail, hard disks can become defective and lose data even when the other components continue to work fine. The result is YOUR site is unavailable, which is all that matters to you. The web hosting company should be able to deal with all of that and have you up again very quickly. Last, but not least, is security. With the continuing prevalence of viruses and spam, you need to know that the web hosting company you select has an array of methods for dealing with them. That means a good technical plan and staff who are knowledgeable in dealing with those issues. The old saying: 'an ounce of prevention is worth a pound of cure' is more true here than anywhere else. All these issues are central to finding a web hosting company that can deliver the services you need. After those criteria are satisfied by a number of candidates, then you can start narrowing them down by price.

Software copyright statement A Software Copyright Statement Protects Current and Future Works If you have a site that is dedicated to the sharing and distribution of open source software it is a great idea to have a software copyright statement that explains the limits of use for your software as well as the limits of your responsibility for those uses. I also recommend getting an attorney to look over the statement before posting it just to be sure there are no legal issues that you may be unaware of. A software copyright statement doesn't have to be a 10 page booklet on the law or the protections that copyright offers, it should be a simple short paragraph stating the basics and hopefully covering your rear from litigation and/or responsibility should someone use the software you are allowing them to use for something insanely stupid or frighteningly criminal while establishing your ownership of the material and expectations of those you are allowing to use your creation. This for some is a no brainer because they've done it before and know the ropes. There are new software developers born and made each and every day and this type of software copyright statement may serve to save them a little grief of their own some day. If you are being kind enough to freely share the software you created with others, you'd like to think that they would at least return the favor of using it within the letter of the law or the manner in which it was intended. This, however, is rarely the case so protecting yourself, your copyright, and your future interests by posting a software copyright statement on your website is really the best way to go in a situation such as this. Trust me I'm not trying to talk anyone out of sharing his or her software with the world. I rather like open source software and admit to using it freely (no pun intended). I love saving money almost as much as I love playing around with new technology. Software allows me to do that and find likes and dislikes about all kinds of programs. Issuing a software copyright statement is one way of protecting your investment of time, effort, energy, and sheer brilliance in the making and design of your technological masterpiece. Hopefully that flattery will keep you going a bit longer at any rate. It is important to know that a software copyright statement is only part of the process required to protect your software but for the most part poses a significant deterrent to those that would abuse your copyright and/or your kindness in allowing the distribution of your software. Even if you are charging people for the use of your software (we are a nation of capitalists after all) you still need to protect the labor you have put into making not only the software but the distribution method, the website, the payment method and the thousands of other things that are part and parcel of the business model for your software distribution. Your software copyright statement is a very small protection for your software don't expect it to be the brunt of your protection. Most of the software developers, coders, and programmers (and any other name you wish to call them) that I know aren't as concerned nearly as much about associating their name with the products they create as they are with protecting future potential income from both the products they are currently designing and the future, improvements they will make to the software and the much improved finished product that comes later. By protecting all your work with a software copyright statement you are not only protecting current works but future works as well.

Web Hosting - Why Backups Are Essential One thing most web site owners have little time for is... anything! Anything other than focusing on their site content and the business or service it supports and the information it provides, that is. That means that administration often suffers, as it frequently must. There's only so much time in the day. But the one thing that you should never let slide are backups. They are like insurance. You rarely need it (you hope), but when you do you need it very badly. Performing regular backups - and testing them - doesn't have to be a nightmare. A little bit of forethought and effort and they can be automated to a high degree. And, they should be tested from time to time. Even when a backup appears to have gone without a hitch, the only way to know whether it's of any value is to attempt to restore the information. If it can't be restored, the backup is worthless. Even when the web hosting company provides the service, there is still some planning involved for the site owner. Hosting companies often rely on one or both of two methods. They backup everything (called a full backup), then backup anything which has changed since the last full backup (called an incremental backup). Of special interest are any configuration files that have been tailored. If you've modified the default installation of a software package, you want to be able to recapture or reproduce those changes without starting from scratch. Network configuration files, modifications to basic HTML files, CSS style sheets and others fall into the same category. If you have XML files, databases, spreadsheets or other files that carry product or subscriber information - about items purchased, for example, or people who signed up for a newsletter - those should get special attention, too. That's the lifeblood of your business or service. Lose them and you must start over. That can break your site permanently. It should go without saying that all HTML and related web site files that comprise visible pages should be backed up regularly. It isn't necessary to record every trivial change, but you can tailor backup software to exclude files or folders. Usually they're so small it isn't worth the trouble. But in some cases those small changes can add up in scenarios where there are many thousands of them. Here again, the backups are worthless if they can't be used. Even if the hosting company charges for doing so, it's worthwhile to test once or twice a year at least to ensure the data can be restored. That's especially true of database backups, which often involve special software and routines. Database files have a special structure and the information is related in certain ways that require backups be done differently. Developing a backup strategy can be straightforward. Start simply and review your plan from time to time, modifying it as your site changes and grows. But don't neglect the subject entirely. The day will come when a hard drive fails, or you get hacked or attacked by a virus, or you accidentally delete something important. When that day comes, the few minutes or hours you spent developing and executing a backup plan will have saved you days or weeks of effort.