Topic: Server Maintenance Friday, 05/15/09

[dschwab9]

I have plans to implement a light weight http server on a separate machine to serve static content (images, css, etc). I don't see us migrating away from apache for the dynamic content though.

[Blind Bandit]

I have plans to implement a light weight http server on a separate machine to serve static content (images, css, etc). I don't see us migrating away from apache for the dynamic content though.

Understandable.  Thanks for all the hard work.

[Ashdaw]

Thanks for the heads up. Nice to see that the site is looked after by such dedicated people

[Kenny01]

Good job guys.

[Vaѕh]

Derek, does that mean no site at all or the forum in maintenance mode?

No site at all. The servers will be physically in my car being moved, and I don't have a cat5 cable long enough to move them running 

If it's a few miles you'd be limited to.. what.. 300 feet anyway? :p  *gives dschab9 a fiber cable and some repeaters*

[Andrew0493]

Excellent work.

[vbgamer45]

Great work! That was fast and smooth.

[uberjon]

Just out of curiosity has SMF thought about using lightspeed web sever to reduce load?

Also I hope you didn't have to much work to do.

Do all that by yourself seems rather hard.

well in my opinion, doing that on the SMF site while apache is still so popular isn't the best of ideas.. afterall the SMF home site is the last place a "build" is tested on the teams side, before closed beta etc..

doing so could perhaps leave a bug or something for a larger population?

or if i have things mixed up (like what kind of issues a different webserver software could cause) it could at the least trick the team into thinking there is a bug when its really lightspeed?

[Blind Bandit]

Just out of curiosity has SMF thought about using lightspeed web sever to reduce load?

Also I hope you didn't have to much work to do.

Do all that by yourself seems rather hard.

well in my opinion, doing that on the SMF site while apache is still so popular isn't the best of ideas.. afterall the SMF home site is the last place a "build" is tested on the teams side, before closed beta etc..

doing so could perhaps leave a bug or something for a larger population?

or if i have things mixed up (like what kind of issues a different webserver software could cause) it could at the least trick the team into thinking there is a bug when its really lightspeed?

The issue wouldn't be bugs.  The issue would be if something wasn't available as an option in litespeed.  Such as a module or option.  But litespeed can reduce load.  And resoruce usage.  There also other free options too.  But I don't want to drag this topic off course.

[tooman]

good luck

i love smf

[Stallyon]

Duuh...We moved? I didn't even notice. I was asleep.

[A.SK]

I have plans to implement a light weight http server on a separate machine to serve static content (images, css, etc). I don't see us migrating away from apache for the dynamic content though.

Good work, is it separated dschwab9.