Hey, I'm not a hosting company or a sysadmin. I'm a developer. So much configuring before even testing my apps is not developing. It's just a pain in the butt.
Sorry for the extra post but I just found this image that shows what I was talking about for the php mapping. It's within the properties of the virtualhost website you are working with that you got to by right clicking the icon for it:) There would be a.php entry in there with the path going to your php executable.
...but the point is that IIS seems more intuitive because that's the environment in which the parent's comfortable.
No, actually it is more intuitive because you don't have to know how to do something before you do it with IIS since it's a GUI. You can click around and find the settings to change. When editing conf files, you have to already know everything you can set there and what each does, and where to type it, or look it up which seems to take quite a while for me.
Ok, you got me on the remote access. I'm developing on my machine first so it's nice to use the GUI but once the project moves to the server I use Remote Desktop or something to access the IIS config GUI. Our Remote Desktop is quite fast, but yes that is a clunky way of doing things. So how do you do it? Do you edit text files over SSH? That's pretty darn clunky too.
Actually it's very easy to create a virtual host in IIS. There are friendly icons on the left for each of your websites and you can create a new one right there. As for PHP, well I got that working with IIS a while ago so it works with all my virtualhosts currently but to add or remove PHP interpreting once it's already set up, you just go to your virtualhost's properties and then click the configuration button on the home directory page, and it lists all the mappings of various types of files. Edit the mapping for the.php extension (delete it or set it to the php executable).
duh you dummy dumbass, how could you not know that??!!
lol
Actually with the regular windows installation of Apache httpd, the wizard asks if you want to install it as a service I believe. Anyway it just happens very easily so I guess that's another advantage of MS, this time Windows vs Linux.
It's like the installation docs intentionally withhold useful information to increase the fun!
Haha, amen. It did take me more than a day and lots of hair pulling to get it all working the way I wanted. You can bet I saved how I set those up and also the most useful websites I used. Something is seriously wrong when I have to google all day to find a step by step method after going over the "real" documentation over and over and getting frustrated as hell.
This goes for virtually every non-default configuration of Apache and IIS but here are a couple examples.
Allowing only certain IP addresses to access a website: Apache - 1. Research on the web how this is done using Google. 2. Find something called "mod_authz_host" and an example of its use here http://httpd.apache.org/docs/2.2/mod/mod_authz_hos t.html . 3. Get confused by all the different examples. 4. Attempt to insert "code" into httpd.conf to limit access to certain IP addresses. 5. Test to see if it worked. 6. Research, edit, test more as needed.
IIS - 1. Click a few buttons 2. Enter IP addresses allowed. 3. Test (it works first try as expected since editing was intuitive).
Use SSL: Apache - 1. Research on the web how this is done using Google (lots of research). 2. Install something called OpenSSL 3. Copy a few files to a windows directory 4. Find an openssl.cnf file that doesn't exist with the OpenSSL install for some reason. 5. Create a SSL certificate using command line. 6. Due to legal/political constraints, download a different copy of Apache with SSL from a strange 3rd party website and replace current copy of Apache that you had installed. 7. Make several changes to httpd.conf file. 8. Install this new Apache as a service using command line if needed. 9. Make several more changes to httpd.conf file (uncommenting LoadModule line, including ssl.conf in an IfModule thing). 10. Copy the certificate files made earlier to an Apache directory. 11. Edit ssl.conf file on several lines to identify server name, document root directory, then also include the certificate path. 12. Restart Apache, pray it works.
IIS - 1. Go to website properties using GUI 2. Click Directory Security tab 3. Click Server Certificate 4. Follow Web Server Certificate Wizard to create certificate.
For extra credit, require SSL connection - In Directory Security tab, Secure Communication area, click Edit, and check the Require secure channel SSL checkbox. I gave up on that for Apache and figured out some way to just forward requests to https (a bit of a hack it seems).
Things just seem more intuitive when using IIS rather than editing conf files and hoping things work in Apache. There is a lot less frustration. It's a shame. Yes I did look for 3rd party Apache config GUIs and couldn't find anything that looked good.
I consider the few inches of air around my face to be temporarily my posession. I would let you know if you talked on the phone with that space for a significantly annoying amount of time.
Am I the only one annoyed by how the links show up within the slashdot blurbs? The words that are contained in the link aren't what the link goes to half the time. What do you think a link for "one tenth of the cost" will go to? WTF. There could just be one or two links at the bottom of the blurb that actually contain text relevant to the target of the link so you know what you might see if you click that link.
Yeah that stinks too, same dueling compressions but with more hassle even.
I was on the Apple hate bandwagon but I'm coming off now I think. I am definitely willing to use ITMS, I just wish other players would support AAC or they would sell MP3 on iTunes.
Not only that, but just about every player that can handle MP3 can also handle LC AAC.
Sandisk doesn't show AAC for their players on their website. They are the #2 MP3 player company. I'm too lazy to check others like Creative or Samsung.
This company and several others are working to make wireless internet access for wide areas available and it's particularly suited to developing countries where they don't have a wired infrastructure already like the US does.
Woohoo, University of Illinois: "Unless subject to any of the exceptions specified below or in Section 4(c), creators retain all rights to traditional academic copyrightable works as defined in Section 2(b) above."
Well there is a burden for Viacom to find every single video that infringes their copyright on someone else's site as well. As they see it, it's not their fault that someone else is hosting all their copyrighted stuff and making money off of it so why do they have to police the internets looking for every instance of that when it's clearly illegal. Rather than having them searching every website all the time for things like this, maybe they should have some sort of way to notify everyone ahead of time what content they own that they don't allow everyone to show without permission. Oh yeah, isn't that a copyright?
Slashdot Mirror
Hey, I'm not a hosting company or a sysadmin. I'm a developer. So much configuring before even testing my apps is not developing. It's just a pain in the butt.
Well, I don't think I can use my favorite text editor that way so it's not the exact same, is it.
Sorry for the extra post but I just found this image that shows what I was talking about for the php mapping. It's within the properties of the virtualhost website you are working with that you got to by right clicking the icon for it :) .php entry in there with the path going to your php executable.
_ iis.png
There would be a
http://www.direct-link-ads.com/Images/html_to_asp
Ok, you got me on the remote access. I'm developing on my machine first so it's nice to use the GUI but once the project moves to the server I use Remote Desktop or something to access the IIS config GUI. Our Remote Desktop is quite fast, but yes that is a clunky way of doing things. So how do you do it? Do you edit text files over SSH? That's pretty darn clunky too.
Actually it's very easy to create a virtual host in IIS. There are friendly icons on the left for each of your websites and you can create a new one right there. As for PHP, well I got that working with IIS a while ago so it works with all my virtualhosts currently but to add or remove PHP interpreting once it's already set up, you just go to your virtualhost's properties and then click the configuration button on the home directory page, and it lists all the mappings of various types of files. Edit the mapping for the
duh you dummy dumbass, how could you not know that??!!
lol
Actually with the regular windows installation of Apache httpd, the wizard asks if you want to install it as a service I believe. Anyway it just happens very easily so I guess that's another advantage of MS, this time Windows vs Linux.
Haha, amen. It did take me more than a day and lots of hair pulling to get it all working the way I wanted. You can bet I saved how I set those up and also the most useful websites I used.
Something is seriously wrong when I have to google all day to find a step by step method after going over the "real" documentation over and over and getting frustrated as hell.
Damn right. Those jobs didn't exist when I graduated in 2002.
I prefer Apache since it's free but....
s t.html .
This goes for virtually every non-default configuration of Apache and IIS but here are a couple examples.
Allowing only certain IP addresses to access a website:
Apache -
1. Research on the web how this is done using Google.
2. Find something called "mod_authz_host" and an example of its use here http://httpd.apache.org/docs/2.2/mod/mod_authz_ho
3. Get confused by all the different examples.
4. Attempt to insert "code" into httpd.conf to limit access to certain IP addresses.
5. Test to see if it worked.
6. Research, edit, test more as needed.
IIS -
1. Click a few buttons
2. Enter IP addresses allowed.
3. Test (it works first try as expected since editing was intuitive).
Use SSL:
Apache -
1. Research on the web how this is done using Google (lots of research).
2. Install something called OpenSSL
3. Copy a few files to a windows directory
4. Find an openssl.cnf file that doesn't exist with the OpenSSL install for some reason.
5. Create a SSL certificate using command line.
6. Due to legal/political constraints, download a different copy of Apache with SSL from a strange 3rd party website and replace current copy of Apache that you had installed.
7. Make several changes to httpd.conf file.
8. Install this new Apache as a service using command line if needed.
9. Make several more changes to httpd.conf file (uncommenting LoadModule line, including ssl.conf in an IfModule thing).
10. Copy the certificate files made earlier to an Apache directory.
11. Edit ssl.conf file on several lines to identify server name, document root directory, then also include the certificate path.
12. Restart Apache, pray it works.
IIS -
1. Go to website properties using GUI
2. Click Directory Security tab
3. Click Server Certificate
4. Follow Web Server Certificate Wizard to create certificate.
For extra credit, require SSL connection - In Directory Security tab, Secure Communication area, click Edit, and check the Require secure channel SSL checkbox. I gave up on that for Apache and figured out some way to just forward requests to https (a bit of a hack it seems).
Things just seem more intuitive when using IIS rather than editing conf files and hoping things work in Apache. There is a lot less frustration. It's a shame. Yes I did look for 3rd party Apache config GUIs and couldn't find anything that looked good.
Our Beees shall block out the sun!
AAAAAAAAAAAAHAHAHA
You has laughed too hard
You has died
I consider the few inches of air around my face to be temporarily my posession. I would let you know if you talked on the phone with that space for a significantly annoying amount of time.
Perhaps we should contract the chimpanzees to help us with this crisis.
You Six Piece Chicken McNobody!
Yeah, I HATE clear type. I want my text to be razor sharp, not fuzzy. The damn thing keeps turning back on by itself too!
Am I the only one annoyed by how the links show up within the slashdot blurbs? The words that are contained in the link aren't what the link goes to half the time. What do you think a link for "one tenth of the cost" will go to? WTF. There could just be one or two links at the bottom of the blurb that actually contain text relevant to the target of the link so you know what you might see if you click that link.
iFaaaaaarrrt in your general direction
Yeah that stinks too, same dueling compressions but with more hassle even.
I was on the Apple hate bandwagon but I'm coming off now I think. I am definitely willing to use ITMS, I just wish other players would support AAC or they would sell MP3 on iTunes.
That's stupid. They are different lossy compressions so they will sound like shit if you do that. It's not an option.
Sandisk doesn't show AAC for their players on their website. They are the #2 MP3 player company. I'm too lazy to check others like Creative or Samsung.
Time for a new business model.
500 GB drives are at $110 now if you're a slickdealer.
http://www.globetel.net/
This company and several others are working to make wireless internet access for wide areas available and it's particularly suited to developing countries where they don't have a wired infrastructure already like the US does.
Woohoo, University of Illinois:
"Unless subject to any of the exceptions specified below or in Section 4(c), creators retain all rights to traditional academic copyrightable works as defined in Section 2(b) above."
Well there is a burden for Viacom to find every single video that infringes their copyright on someone else's site as well. As they see it, it's not their fault that someone else is hosting all their copyrighted stuff and making money off of it so why do they have to police the internets looking for every instance of that when it's clearly illegal. Rather than having them searching every website all the time for things like this, maybe they should have some sort of way to notify everyone ahead of time what content they own that they don't allow everyone to show without permission. Oh yeah, isn't that a copyright?