K55
Well-known member
So, you want to host a website on your circa 1989 Macintosh?
I hope you're ready for :O , because making a 30 year old chunk of hardware work reliably with modern networks is a huge pita.
What you'll need:
It's very useful on getting your connection setup.
Common problems to work around
Dynamic IP on home server:
This is 2 problems really, your Mac having a dynamic IP on your home network, and your home router having a dynamic IP on the internet.
Go into your router settings, and find the IP that's assigned to your Mac, and set it to static. This means that through resets, and DHCP refreshes,
your Mac will have the same IP on your home network.
On the other hand, unless you're paying your ISP, you most likely have a dynamic IP at home also, so if your router ever goes offline, you could get a random new IP
Have a look at http://www.makeuseof.com/tag/5-best-dynamic-dns-providers-can-lookup-free-today/ to find a good dynamic DNS service to set up, makes life a lot easier.
Actually hosting a website :^)
Ok. Now that you've presumably spent $300 on getting your Mac setup and a few dozen hours connecting it to the internet, we're ready for step 2, actually hosting a website~
Machttp configuration stuff/tips
This is just some notes I have on making it work reliably. If I don't mention anything here, its better left as default:
Hopefully this information is useful to someone. Happy hosting!
I hope you're ready for :O , because making a 30 year old chunk of hardware work reliably with modern networks is a huge pita.
What you'll need:
- A fast mac, this basically restricts you to a SE with a accelerator or a SE/30 (preferably with a accelerator)
- A fast hard drive, to be able to actually read without having a long drive spinup time
- A Ethernet card . There are other methods of connecting a mac to the internet, but I'd recommend the easiest method
- Software, namely MacHTTP (discussed below)
- A̶̶̶ ̶̶̶p̶̶̶l̶̶̶u̶̶̶s̶̶̶h̶̶̶ ̶̶̶s̶̶̶t̶̶̶e̶̶̶v̶̶̶e̶̶̶ ̶̶̶j̶̶̶o̶̶̶b̶̶̶s̶̶̶ ̶̶̶d̶̶̶o̶̶̶l̶̶̶l̶̶̶ ̶̶̶t̶̶̶o̶̶̶ ̶̶̶p̶̶̶u̶̶̶n̶̶̶c̶̶̶h̶̶̶ ̶̶̶e̶̶̶v̶̶̶e̶̶̶r̶̶̶y̶̶̶t̶̶̶i̶̶̶m̶̶̶e̶̶̶ ̶̶̶y̶̶̶o̶̶̶u̶̶̶ ̶̶̶g̶̶̶e̶̶̶t̶̶̶ ̶̶̶a̶̶̶ ̶̶̶b̶̶̶u̶̶̶s̶̶̶ ̶̶̶e̶̶̶r̶̶̶r̶̶̶o̶̶̶r̶̶̶ ̶̶̶a̶̶̶n̶̶̶d̶̶̶ ̶̶̶c̶̶̶r̶̶̶a̶̶̶s̶̶̶h̶̶̶
It's very useful on getting your connection setup.
Common problems to work around
Dynamic IP on home server:
This is 2 problems really, your Mac having a dynamic IP on your home network, and your home router having a dynamic IP on the internet.
Go into your router settings, and find the IP that's assigned to your Mac, and set it to static. This means that through resets, and DHCP refreshes,
your Mac will have the same IP on your home network.
On the other hand, unless you're paying your ISP, you most likely have a dynamic IP at home also, so if your router ever goes offline, you could get a random new IP
Have a look at http://www.makeuseof.com/tag/5-best-dynamic-dns-providers-can-lookup-free-today/ to find a good dynamic DNS service to set up, makes life a lot easier.
Actually hosting a website :^)
Ok. Now that you've presumably spent $300 on getting your Mac setup and a few dozen hours connecting it to the internet, we're ready for step 2, actually hosting a website~
- Download http://www.machttp.org/downloads/machttp/MacHTTP261.sit.hqx and unpack it to your Mac.
- Put the files for your site in the same folder as the machttp executable
- Configure machttp as per tips below
- Run machttp and see if it works
- Keep trying to fix machttp every time it breaks
Machttp configuration stuff/tips
This is just some notes I have on making it work reliably. If I don't mention anything here, its better left as default:
- DUMP_BUF_SIZE = the max size of a http packet that gets sent. It says 256-10240, but 256 is the only value that wont saturate the cpu loading a page over 1kb in size
- NO_DNS = Uncomment this, unless you want to have your Mac spend 20 secs a connection trying to figure out DNS traceroutes
- USE_THREADS = 100% want this to be enabled. Can use right away on system 7.5, 7.0->7.1.3 use the extension @ http://www.pure-mac.com/appud.html#threadman instead
- No, you can't put CSS in a separate file, it's too slow, and fails to load 90% of the time :-/
- Speaking of files, don't try and be cheeky and compress your page by removing endlines, because those are used by machttp to segment your transmitted packets, and you'll end up transmitting a 5kb packet and G̶E̶T̶ ̶A̶ ̶B̶U̶S̶ ̶E̶R̶R̶O̶R̶ ̶A̶H̶H̶H̶
Hopefully this information is useful to someone. Happy hosting!
Last edited by a moderator: