Welcome to www.minisinbox.com

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.

Copyright Infringement Play It Safe: Making Sure You're Not Committing Copyright Infringement Copyright infringement is not an easy thing to explain. While it may seem as simple as not using someone else’s work, it’s not that easy. Thanks to the Electronic Frontier Foundation, and many other organizations, we have the ability to use others’ works – as long as we use it under ‘fair use’ laws. So what does fair use have to do with copyright infringement, and how can you utilize it? Fair use laws are the conditions in which you can use a copyrighted work without having to pay someone royalties. This includes when you use a copyrighted work for educational or instructional uses, criticism of the work, commentaries on the work, news reporting about the work, teaching on the work (including multiple copies for classroom use), scholarship uses, and research. This is talked about fully in Section 107 of the Copyright Code (commonly called Fair Use) and is available for you to read at your local library. Copyright Infringement in day-to-day life Sometimes, if you’re writing a paper for work or school, or if you are creating a Power Point presentation, you need to use someone’s work that is already in copyright. So how do you use it without committing copyright infringement? All you have to do is ask – the worst they can say is no, right? But, if they do say no, there are several items in the public domain which may help you to finish your project without having to commit copyright infringement. What is the public domain, and how does it relate to copyright infringement? Material that is not copyrighted is considered in the public domain – you cannot commit copyright infringement on works in the public domain. These works include things that the copyright has expired on, or is not copyright-able – such as government publications, jokes, titles, and ideas. Some creators (writers, musicians, artists, and more) deliberately put their work in the public domain, without ever obtaining copyright, by providing an affiliation with Creative Commons. Creative Commons allows people who create materials to forfeit some, or all, of their copyright rights and place their work either partially or fully in the public domain. So, how do I ensure I’m not committing copyright infringement? First of all, if you’re going to use someone else’s material, you may want to check the public domain to see if something is suitable for use, instead of trying to use someone else’s copyright. However, if you can’t find something suitable (and you can’t create something yourself), the next best thing (and your only legal course of action) is to find a piece that is in copyright, and contacting the copyright holder. When you contact the copyright holder, make sure you tell them what you want to use their piece for – whether it’s for your blog, podcast, or report – and ask them if you can use it. You may have to pay royalties, or an attribution in your piece, or a combination of both. The creator may also place many limitations on when and how you can use their material. Follow all these instructions they give you, and you’ll be free and clear to use their work as you want. Once you have permission to use a copyrighted work, you need to make sure you stay within the agreed-upon boundaries - if you veer outside their agreed terms, you may open yourself up for a copyright infringement lawsuit – which can be nasty, costly, and time consuming. If you’re in doubt, before contacting the copyright holder, contact a copyright lawyer to ensure you’re following the law – and protect yourself!

Web Hosting - Unix vs Windows-Based Hosting, Which Is Better? An operating system functions largely out of sight, or at least is supposed to. It doesn't matter to non-geeks how a file gets stored, or how memory is used, or how simultaneous processes share the limited resources available on a computer. These are among the basic functions of any operating system. Yet, you can find very passionate supporters - who offer very detailed lists of pros and cons - for every operating system. Why? Because, though the low-level functions of an operating system do their work out of sight, there are many other features that rise to visibility. Sometimes, they do so when they're not supposed to. Weighing the pros and cons objectively could consume a book. But to select a web host operating system, a manageable level of considerations apply. They can be weighed even by those who don't know a processor queue from a pool cue. Learning Curves For most web site owners, administering the site/server is just overhead. It's not something they take pleasure in doing and they have plenty of other things to worry about. Many wouldn't know how and have no interest in learning (rightly so, given their priorities). Consequently, ease of administration is paramount for such people. Whether a Unix-based site (usually Linux these days) is easier to administer than Windows depends on your current skill set and the type of tools and level of access the web hosting company provides. But in general Linux is more difficult to install and maintain than Windows and the learning curve is steeper. FTP and Control Panels Often, you don't have to care. For many, the operating system is fairly transparent. FTP file transfers to get a new web page up to a Windows server are very much like they are to a Linux-based site. The user/administrator simply doesn't see what's behind the curtain. Many companies provide other utilities that completely mask any awareness of the operating system underneath. When that's the case, the web site owner has no reason to care, until or unless they need or want to go 'inside the black box'. Performance Performance issues can be relevant in selecting which operating system host type to choose. But for the most part, that aspect is outside the web site owner's control. Overall performance can be good or bad on either system, depending on many factors that the publisher will rarely see. The issue is a wash, as far as tipping the scales is concerned. What is more likely to be seen by a web site owner, at some point in their (and their site's) development is the database product that can be used to store information. Databases Microsoft SQL Server is relatively simple to use, yet extremely powerful and can deliver great performance. But it doesn't run on Linux. At least, not without special software to emulate Windows, which usually kills performance. On the other hand, with a bit of time invested, MySQL isn't significantly more difficult to learn than MS SQL Server and there are many free installations. Cost may well outweigh other considerations for most on this issue. Programming Languages Last, but not least, there are differences in programming languages that can be (or at least typically are) used on Windows vs Unix. If you have programmers who are skilled in Visual Basic, ASP and other Microsoft technologies, then a Windows-based host will be your preferred choice. For Perl and PHP programmers, Linux is the more common platform of choice. No single factor can push you to one versus the other operating system. And, in the long run, it isn't the primary consideration, unless you just enjoy playing with operating systems.