![]() |
any NATS webmasters here?
I wanted to ask how you set up your affiliate program / NATS.
Do you install it on a separate server? Apart from your paysites? What's the best way to do it? :helpme |
nats.domain.com with a unique static IP.
|
Quote:
Example: dedicated server 1: NATS installation with all the databases, etc dedicated server 2: paysites with CMS and content |
Quote:
dedicated server 1: NATS installation with all the databases, affiliate website, etc. dedicated server 2: Everything else |
Quote:
Do you have any idea what kind of server specs are needed to run a small NATS program? CPU/RAM etc. |
Ask TMM/NATS they will give you all the info on what you need . there is a list somewhere for server requirements that you can find probably by searching goog
|
Quote:
They just linked me to a wiki page with server software requirements. I need to know what CPU/RAM/SSD i need to run things smoothly. |
Quote:
|
Quote:
:( |
Quote:
2 GB RAM 2 SATA Hard Drives RAID 1 |
You can get something like this for $200 per month - fully managed
Quad Core Dual Xeon 2x500GB SATA RAID 1 8GB RAM 10TB Bandwidth Get something like this for around $99 per month - fully managed Quad Core Xeon 500GB SATA 4GB RAM 10TB Bandwidth |
ask support they will give you some advice
|
You should keep nats on separate server apart from your your pay sites one
|
Quote:
And then get a very powerful administrative server with NATS, CMS and all the other scripts and databases. How does that sounds? Makes sense? Any comments on a proper setup are greatly appreciated. Thanks. |
I prefer having one server for NATS and one server for the sites. In some cases, I even put the tours on a different server than the members area. I like to isolate my components so that if one component is causing problems, the other are minimally impacted.
Example: members server goes down for whatever reason, surfers can still see the tours and join, though they may be cranky for a bit. ;-) Isolating servers based on component also allows you to tweak each server better to suit its purposes. Example: NATS will need services running that your members area will not, and vice versa. The fewer "unnecessary" services running on each server will likely mean a lesser load and fewer points of failure. As the old saying goes, the fewer moving parts the better. Of course, budget always does come into play. If you can swing the money for a unique NATS server, do it. |
It really depends on how much usage you have on either one of them.
nats and a LAMP CMS can certainly run on the same server, but when you start getting lots of database hits you may want to separate. if you're just starting out get yourself a good host/admin and you'll have no problems running them on the same server and you will save some money for good while as you ramp up sales. The ideal scenario is having one server for each but if A few hundred dollars per month is useful to you and put them on the same server til it doesn't matter |
I have been running nats on the same server with my paysites for 5 years and no issues. If you are planning to have massive traffic I guess that's different, I think the dedicated server is not necessary. You can always get a second server and move it later if it's a problem. (or move your paysites if they start getting so much traffic they overload your nats server)
|
All times are GMT -7. The time now is 10:12 AM. |
Powered by vBulletin® Version 3.8.8
Copyright ©2000 - 2025, vBulletin Solutions, Inc.
©2000-, AI Media Network Inc123