LiveZilla Live Help

You are here

Documentation

Recommendations for Standard Installations.

  • SafeSquid® has a very low Total Cost of Owner-ship, and a very good ROI. Most users prefer to extract more out of the fixed costs, by increasing the derived results. It is therefore recommended to use Hardware that can be scaled for RAM / CPU / NICs.
  • Choose H/W that can scale for RAM / CPU. It will help to accommodate more users, over a period of time.
  • Use Hard Disks with good seek / read / write speed. It will reduce latency in case you plan to use large content disk-caches.
  • If you expect a large traffic to be handled, it would be a good idea to use a GigaBit NIC. To increase security, or to cater to multiple networks it would be advisable to use 2 NICs or more.
  • System Configurations that have easily accessible Hardware drivers for Linux are absolutely preferable. It would be useful, if you plan to increase redundancy by using Clusters.
  • You will surely want to use variety of Log Analyzers (both open and closed open source) available. Use Linux Distributions that have a good support for Web Servers, Perl, PHP, Caching Name Servers, etc.
  • SafeSquid servers shouldn't be requiring x-windows, so basic hardening should be enough.
  • Antivirus will be required to scan content being transported via SafeSquid. Choose vendor that offers ICAP based solution because ClamAV is free. If you prefer to be secured by a commercial vendor go for it.
  • If you have a Microsoft Network, then sooner or later you will want authentication to work from ADS. If you are a large network you'll alternatively want user authentication done from LDAP or RADIUS, or something else, that's available.
  • RPMS are available for most of the software mentioned above, but quite a few are served as raw source codes, and must be compiled on your server. So it's always a good idea to install GCC & G++ on your SafeSquid Server.

 

Comments

Great stuff as usual! This content is relevant and genuinely enjoyed to read it. Thanks much