Monday, February 25, 2008

Update Your Entire Website Instantly Using Server Side Includes

Imagine my plight... I have 100+ pages on my website and I have to change my e-mail address and the copyright info on all the pages. The reason...

My mail box is over-flown with junk mails.

My only option is to edit all my web pages offline and then upload each one of them again, not to mention countless errors I make in the process.

100+ pages is still a small website. Imagine what it will be like if my website had 1000+ pages?

Sounds scary right?

If you would like to avoid the kind of mess I'm in right now, you have one option. Start using "Server Side Includes (SSI)"

In technical jargon, Server Side Includes are directives which you can place into your HTML documents to execute other programs or output such data as environment variables and file statistics.

If your only intention is to manage your website more effectively and painlessly, it is more than enough if you learn one "Directive" of SSI - the "Include" directive.

In simple terms, SSI Include is a line of code which you can use in your HTML documents to include contents from other documents. In other words, change just one file (the Include file), and your ENTIRE SITE is instantly updated!

The basic syntax of an Include directive is:

Where PATH_TO is the "VIRTUAL" path to include file on your server.

Here's how to include your copyright info and navigation links using SSI Includes...

First, you need to check with your server administrator whether your server supports SSI or not. Most servers support them.

Second, you need to rename all your HTML files with extension .shtml

-----SIDE BAR-----
You can start with one file and if everything goes fine, rename rest of the files. -----SIDE BAR-----

To keep things organized, you can create a directory at the root level called "includes" to house all of your included files. Now create a HTML document with only your copyright and navigation links. Copy everything that is between the BODY tags of this document and paste it in a new file.

Save this file as nav.html or any name you like with extension .htm or .html. You need not save this file with .shtml extension. Now upload this file to your "include" directory which you created for housing SSI Includes.

To include copyright info and navigation links in a HTML document in your SITE ROOT, place the following code where you want the copyright info to be seen:

Now if you want to include copyright info and navigation links in a HTML document in a folder UNDER your site root, the code will change to:

...and so on.

If you want to change or edit your copyright info or navigation links, just edit and upload your nav.html file and the change will be reflected in all the documents (using the "Include code") instantly!

You can also create your website headers/footers using SSI Includes.

There are host of other cool things you can do with SSI. For more info on SSI, you can visit the following sites:

http://www.useforesite.com/tut_ssi.shtml http://wdvl.com/Authoring/SSI/Intro/index.html http://www.bignosebird.com/ssi.shtml

Vishal Rao publishes an informative e-zine: iNet Profits. Subscribe to his e-zine and get his free e-mail course: "11 Killer Strategies To Explode Your Online Profits", by sending a blank e-mail to => sub@inetprofits.par32.com

Labels: , , , ,

Thursday, February 14, 2008

Website Updates are a SNAP With Server Side Includes

If you ever had to make a change to your website that needed to be carried onto every page, you know what a tedious job it is.Well, have I got news for you. It doesn't have to be. Welcome to the world of Server Side Includes, also known as SSI. The best part about SSI is that it will make your life as a site owner 'oh so sweet.' You're going to want to kiss me after I give you the lowdown on this little beauty.

Let me give you an example. Let's say you have a site with over 50 pages and you need to add another link to your navigation bar. Can you imagine how long it would take you to open each page and update it? By putting your navigation bar into an SSI file, you would only open up that one file and update that -- and the change to your navigation bar will show up site wide. See how simple that was? By editing one file you have updated your entire site instantly.

The most common use of an include file is for your top navigation, your bottom text navigation, copyright, logo or any other piece of info needed to appear on all pages of your site.

So how do you create an SSI file? Glad you asked! An include file can be an HTML file or a simple text file. It should be whatever HTML coding you need for that element of your site, minus the or tags which should remain on your individual pages.

An easy way to make them is to design your web page and cut and paste the code you want into individual files and name them things like topnavigation.htm or bottomnav.htm. By giving them descriptive names, you'll know at a glance which file is which when it comes time to perform those updates.

After creating the files you plan on using as your includes, you'll need to open your web pages and insert a line of code where you want the SSI information to show up in your documents.

The code looks like this:

If your includes are located at the root level on your web server your path would look like this:

That's it. Pretty simple, really. After you get the hang of it you'll wish you would have learned about them years ago. They really do make global updating a snap.

Here are a couple of good sites to learn more about SSI:

Big Nose Bird-
http://www.bignosebird.com/ssi.shtml

CGI Resource-
http://cgi.resourceindex.com/Documentation/Server_Side_Includes/

New Breed Software
http://www.sonic.net/~nbs/unix/www/ssi/

Web Reference
http://www.webreference.com/programming/ssi/intro/

Before you start implementing SSI you need to ask your web host if they support them (most do), and also if they will need to be named with any special extensions. Some servers may require you to give them specific extensions like .asp (if it's NT) or .shtml (for many Unix servers). Although the majority won't, it's always better to ask first. Better safe then sorry.

By designing your website with server side includes you'll save yourself a ton of headaches when it comes time to updating your site. SSI is a Webmaster's best friend, so I suggest you spend some time getting acquainted.

Merle http://www.EzineAdAuction.com "Where some of the BEST Deals in Ezine Advertising are Made" Buy & Sell Ezine Ads in a live auction setting! Publishers sell off your excess inventory and Buyers pick up some Fantastic bargains. Go now.

Labels: , , ,

Monday, February 11, 2008

Is Your Website Secure On A Shared Server? Part 1

Security aspects of a shared web hosting server have always on the forefront. And, with almost 90% of websites being hosted on shared servers, the security considerations are not uncalled for.

Also know as virtual hosting, shared hosting has been the favorite of small and medium size enterprises. Owing to the fact that shared web hosting works out to be cheaper than hosting on dedicated servers. That?s because a website shares a server with other websites in a virtual environment. But, does that make it vulnerable to hacking? That?s the million dollar question. To understand the security aspects of hosting on shared servers, we will have to first understand the different modes of shared hosting.

Types of shared hosting

  • Domain based shared hosting:
It works on the Virtual Private Server (VPS) technology and provides each website with a unique URL, even though they are hosted on a single server. The VPS technology achieves by creating effective partitions in the server and gets them to act as individual servers.
  • Name based shared hosting:
In name based shared hosting, a websites name appears as a subset of the service providers name. Example of such service providers are geocities, blogspot etc.

  • Directory based shared hosting:
With respect to directory based shared hosting, the customers website will be mentioned as a directory in the host domain name. The most important point that comes through with shared hosting is the relative lack of a dedicated IP address. That?s because most of the web security apparatus are applicable on the IP address level. That?s the reason why, dedicated severs are capable of providing a more secure environment; as they guarantee a unique IP address.

The other blockade with shared server security is the relative difficulty encountered in implementing SSL certificates.

Search Engine marketing expert, Tarun Gupta is one of the most prolific writers in the internet marketing domain with his articles being published in numerous search related websites and newsletters. He is the founder director of web development and web hosting services company BrainPulse.com.

Labels: , ,

Friday, January 18, 2008

Website Hosting - Dedicated Servers

You have heard of dedicated servers but you really are not sure what they are and if you should have one. On the other hand, maybe you know that you require a dedicated server, but really do not know how to choose the right host. Well, either way, this article is filled with information just for you.

When it comes to website hosting, essentially they provide you with two options dedicated servers or shared servers. What is the difference? Well, shared servers are the type in which you will share the space with other people. Your website and those of other people will share the same server. A dedicated server is completely the opposite, every aspect of that server, as well as the network connection is "dedicated" only to your website.

Before choosing a dedicated server, you should have an understanding of the major differences between shared and dedicated. One massive difference is the price. In most cases, a dedicated server will cost you a great deal more than a shared server. Another massive difference is the skill levels required for each. With a shared server, the host typically takes care of administration of the server, which requires little technical skills. On a dedicated server, it is your responsibility to take care of server administration.

Before deciding if a dedicated server is for you, you should consider the level of your website. If you operate a small business or a basic website, a dedicated server is likely not the best choice. However, if you have a high traffic, large, and massive website, a dedicated server will be the likely choice.

Overall, it is important to understand your space needs, reliability, bandwidth, and budget prior to choosing dedicated server website hosting. Generally, a large website, a large company, with high traffic, may want to consider a dedicated server. A small business, with minimal traffic, will likely want to stick with shared servers.

The author is owner & operator of several reliable website hosting sites. For Cheap Website Hosting Visit http://www.myreliablehosting.net today

Labels: , , , , ,

Thursday, January 17, 2008

VPS VS Dedicated Servers Comparison

VPSs(Virtual Private Servers) allows hardware to run at a higher utilization rate. They are cheaper since usually they have less power costs than one physical server.

Their maintenance is still more expensive since it is difficult to patch all virtual servers running different operating systems on different physical servers which still needs separaWeb Hosting Reviews and Information - StartLogic Company Profile and Hosting Plans
te maintenance. All maintenance on higher amount of systems must be done quick so maintenance time is as low as possible.

It might be difficult to make backup of one arbitrary software. Security issues are more complex in VPS providers than in dedicated server providers. There are two layers of security : both physical server security and VPS security. VPS monitoring might be more difficult than dedicated server monitoring.

VPS requires usually more expensive drivers like multi-port network adapters and more physical connection than dedicated server. There are some more management problems since you will use more Ethernet cables and network equipment like switches.

VPS providers tends to need more IP addresses than dedicated providers. If you have only 100 physical computers with 20 VPS on each it is still 2000 IP addresses. Also, physical system which runs more VPS might have very high number of packets per second (PPS) though network. It is difficult to manage large number of IP addresses, MAC addresses etc.

There are sometimes software licensing advantages when running VPS. Some software licenses are by number of physical processors or physical computers and therefore they are cheaper when you can divide its price by number of VPS on one physical computer.

VPS performances nowadays are very good with overhead less than 5% on some modern virtualisation software like Virtuozzo. But, disk I/O performances might have bottlenecks due to more disk fragmentation.

Mr. Adamovic is software developer and linux fan who runs the following websites: Cheap VPS , VPS deals , promo codes and discounts , VPS Review Magazine , VPS hosting linux .

Labels: , , , ,

Monday, December 17, 2007

Dedicated Servers ? Backup and Recovery Strategies for Web Hosting Companies

What kind of backup recovery strategy should a company have for its dedicated server? Web hosting companies have been debating this architecture since their existence began. It is really a question pondered by the whole IT community. There are many right solutions, dependent on your company?s ability to handle downtime. The correct solution for you will factor in the amount of redundant protection you need against the overall cost.

Before we discuss the different options for backing up and recovering your dedicated server, we should mention that the server hardware, data center, and fiber connection are all critical to reliability. This article is specifically focused on strategies to backup and recover your server?s data.

At a minimum, you can create a partition in your hard drive and backup your server weekly or monthly. There is no cost to this kind of solution, but the downsides are obvious. If your hard drive crashes, you will lose your backup as well. This kind of solution is only recommended if you can afford to lose all of your data, which most web hosting companies cannot.

Next, you can contract a remote backup service to set up offsite backups. These backups can be run daily, weekly, or monthly. The cost of this solution is around $30-$50/month depending on the web hosting provider. This option gives you a solid backup in case your hard drive crashes. The downside is that recovery time will take 6-12 hours or more depending on how much data you have. The data has to be manually copied over, and this is a slow process. If you can afford the cost, this solution is part of an overall backup system, but it is not recommended as your only solution.

The next backup option is to have a second hard drive installed on your server and have it set up to do daily, weekly, or monthly backups. Most web hosting companies that provide dedicated servers will charge between $15-$30 for a second hard drive. This is a nice compliment to the previous solution if you have the budget for both. The recovery time is faster then a remote backup. But unlike a remote backup, if your dedicated server or the datacenter are down, then you cannot access the backup. For most small web hosting companies this is not a problem. If their entire server or datacenter are down, they have larger issues to worry about. We recommend this as a complimentary option with a remote backup.

Next, a web hosting company can use mirrored RAID drives. This option will cost $50-$80/month more, but it provides the fastest possible recovery in case of a hard drive crash. You can just reboot using the mirrored drive, and you are back in business. The cost is a little higher, but this is a nice luxury. The downside of this option is that if your server is unavailable, then you still cannot reach your data. Additionally, if the hard drive becomes corrupted it will also corrupt your backup. This is why we recommend mirrored drives as part of a larger solution that includes other backup systems.

Finally, there are mirrored servers. This entails the largest cost and is really not necessary, except for those web hosting companies that can tolerate no downtime at all. In this scenario, if the server itself dies you can have another server ready to take the load. In fact, if your company is large enough, you might already need this kind of solution for performance. Some websites require multiple servers to handle the performance, and it is load balanced across them. In this case, if a server dies the system still runs. This is the best solution but it is not always necessary. And, of course it is costly.

We recommend a weekly remote backup to provide you with a fail safe version. Even if the datacenter burns down, you will have a copy of your data. To this we would add either mirrored RAID drives or a second hard drive, depending on your hosting company?s needs. If you are more worried about recovery time from hard drive crashes, which is the most frequent hardware problem with dedicated servers, then go with the RAID drives. If you are more worried about the hard drive getting corrupted, go with the second hard drive.

We hope this article provides you with the information you need to adequately back up your dedicated server!

Rodney Ringler is President of Advantage1 Web Services, Inc., which owns a network of Web Hosting Informational Websites including HostChart.com, ResellerConnection.com, FoundHost.com, ResellerForums.com, and HostingKnowledge.net. Rodney has over 15 years industry experience from programming to internet marketing. rodney@hostchart.com

Labels: , , ,