Lompat ke konten Lompat ke sidebar Lompat ke footer

Hosting your own Web Server: things to consider

Hosting your own Web Server things to consider

Are you feeling annoyed or disappointed with your current web hosting provider? Have you changed your web hosting company? Have you ever thought about hosting your own website? Do you have ambitions to control and manage your own web server?

If you answered ' yes ' to the above question, then you are probably ready to host your own site. This article will give you things to consider when switching.

When becoming a web host yourself, you must have technical skills and basic knowledge of operating systems, understand technical terms, understand how to set up a server environment (such as: DNS, IIS, Apache, etc.), have basic knowledge of programming languages and databases (PHP, Perl, MySQL, etc.), be familiar with the latest technology, and have a basic understanding of server hardware and components.

You should be aware of the pros and cons. Saying that you want to host your own web server is one thing, and actually doing it is another.

Pro:

A real sense of responsibility

Increased level of awareness (you are at the forefront of all server events)

No monthly hosting fees/accounts

Incompetence no longer exists

Non-shared environment (dedicated server)

Website, database, content, storage, etc. no limits

More bandwidth

No need to wait for someone else's time

Full control

Cons:

Sometimes exhausting

Facing server/hardware issues

ISP business account (monthly expenses for business/broadband)

If the server is down, then the website cannot be accessed

No technical support team

Software, hardware and network costs

There can be many more pros and cons, but I have highlighted some of the main ones. Managing a web server starts as a full-time job, you need to constantly monitor its performance and security. This can sometimes be a tiring task, especially if you currently have other responsibilities. Nonetheless, the control you have over your website and its performance is enough to give you satisfaction. You no longer need to wait for technical support or approval to install scripts to the server. You can have as many websites and databases as you want, as long as your hardware is capable of handling them. You no longer need to log into discussion forums and search for the best web host or complain about how disliked you are on your current hosting provider. You can even start hosting personal websites of family and friends.

Ask yourself, how advanced are your technical abilities? Many times you don't need to be a tech geek or something of the sort, but you do need to be very good at leveraging the resources at hand. You must know how to find solutions and answers to problems quickly and efficiently. This means that you must be proficient in using the internet. Not just ordinary internet users who come from browsing, but you have to be an internet user who can always find what they are looking for. This is key, because in any server environment you will encounter problems and finding the most appropriate answer is usually done online, using various resources, search techniques and search engines. Of course you could hire someone to fix your problem, but as we should have learned from "web hosting", having someone do it for you is not always the best option. Here is a test to see if you are ready to find a solution. I need a solution for Microsoft Windows 2003 Server Event Error - "Event ID: 1056', it is DHCP Server Error. How Will you find the solution? Please find a solution.

Did you go to Google for the first time? If you do, it's a good and common venture for most people, as well as a good place to start, but it's usually better to start on the developer's website. In this case, "microsoft.com" it would be the first choice. Why? Google will most likely give you answers from Microsoft and other sources, but you don't want to get inaccurate information from other sources. Usually, getting information directly from Microsoft isn't always going to specifically solve your problem, but developers should always be the first place to look for answers. Now look for the error again and go to the Microsoft site to find the solution.

What search phrases do you use? It should be Event ID: 1056, since Event ID is the exact error, it shows your problem exactly without expanding your search. Sometimes the description of the error is also suitable for searching, only the description of the error itself or in combination with the Event ID. It depends on your mistakes, your search feedback, your ability, and your technique. In this example, I did not include a description of the error.

Google or Yahoo! it should be your second choice (the two largest search engines). Then search in smaller, specialized search engines. Good search sites that use the Google operator tag are www.soople.com. next, you should search within forums and discussion groups.

Determine the speed and power of your processor. Regardless of the amount of traffic you expect, I would recommend a dual processor or a larger one. Dual or larger processors are best because if your website suddenly becomes popular, then you will be well prepared, and if you host other server options or other websites on the same server, then the performance will be better. Currently, 64-bit platforms are the direction of processors used. A speed of 3.8 GHz is the most commonly available. If your budget allows you to buy the latest technology, it is the ideal, but remember that at the moment a 64-bit compatible processor is not necessary without many applications that require or support the platform. That is a lot of speed that does not move anywhere. In addition, remember the power of 64-bit platforms and the higher the speed of the processor, the more heat it generates, therefore, it should be cooled more quickly and efficiently. Today, a dual 32-bit processor with speeds of 2.8 GHz to 3.2 GHz is enough (in fact it is already much more than enough). However, if your budget allows you to afford it, then the latest and greatest will be fine, and you will be well prepared. If not, do it like most people and improve when the time comes.

Make sure you have a CD/RW drive. A floppy Drive is not required, but I recommend creating a system recovery disk. A CD/RW Drive is required because you need a removable storage device. You never know when you need to install a driver from a different location, for example an ethernet driver. An external CD/RW Drive is the best option, especially if you have multiple machines.

Choose your operating system carefully. Choose the vendor with whom you feel most comfortable. Don't choose a MAC if you've never used a MAC before. Just because your friend suggested it and said that it is very easy, does not mean that it will be easy for you. You are trying to create an online web server, not to learn a whole new system. Stay focused and realistic. If you are comfortable with Microsoft, then use Microsoft, regardless of the opinion of IT people at your workplace who say that Microsoft products are not secure, Linux or Unix are safer and much better for web servers. If you have never used Linux or (especially) Unix, then you will have a hard time. Your experience with a web server will soon become a nightmare and you will be throwing away thousands of dollars in wasted equipment. Choose what you already know, not what others say. Each platform has its own advantages and disadvantages: Microsoft

is the most user-friendly among all; Mac is the web/graphics developer among all; Linux is the open source developer's paradise among all; Unix is the most secure among all. Each platform can be customized in a certain way to provide a solid and quality platform, but it's better to stick with what you already know.

You must install all web services (such as: Apache, IIS, etc.), applications (such as: backup device software, RAID (Array) manager), programming languages (such as: PHP, Perl, etc.), CGI, Database (such as: MySQL, Microsoft SQL, etc.), and web log analysis (such as: weblog expert, nihuo, etc.) in your system. It is also recommended to perform system updates, installation of security patches, and firewall installation and configuration. Sometimes it is better to leave the installation and configuration of security after the system is working properly to avoid unforeseen problems. This way, when you install a firewall and there is a problem with the connection to your website from outside your network, you can perform troubleshooting by assuming that it is a firewall, so you can open port 80 on the firewall. This method can save you a lot of trouble, but is sometimes considered unsafe, especially if you don't have a hardware firewall yet.

Next, there are a few things to consider before installing and configuring the server. Where to put it? A secluded, cool location is ideal, but if this is not possible, adjustments can be made.

Where to put it?

Find a location inside your home that is free of static, we don't want to put the server on the carpet, close to curtains, or anything else that could cause a static reaction. The reason for this is so that the internal components of the server do not receive static loads and are short-circuited.

The location should be in a cool environment, ideally below room temperature. The reason for this is that servers (also desktop computers) generate a large amount of heat, the more heat is generated, the more cooling is required. If the server does not stay cool, this can cause the server to stall and eventually crash. This is the same as when the car is overheating, then the engine stops working. You can keep the internal components of the server cool by keeping the room temperature cool, in addition you can also add additional fans on the server that will help cool the internal components of the server, or you can also place a standalone fan directly on the back panel of the server to constantly cool the internal components of the server. Depending on how cool your room is and how much heat your server generates

Posting Komentar untuk "Hosting your own Web Server: things to consider"