next »

[mampy]

Lol.. I thought i had problems staying on task.... 

This place is a riot!

Now... if i could only remember my master password to authenticate this mamp install.


@jairez -  did you go mamp or mamp pro?

Im gonna easy mamp it till i hear from you nb's i definitely want to dig into my amiga roots and try the make make install jazz...  did you know that in the man pages for vi there is still a clause for amiga only stuff talk about solid long lasting code... 

Mampy 

[jairez]

did you go mamp or mamp pro?

Just plain MAMP.  The placard on my car says "Cheap Bastard on Board."

Thanks Mampy for the fun ride on this Welcome wagon.  As a resident of "Suburban Tempe" the Raising Arizona was right in my wheelhouse.  In fact, the quote below my picture is from the movie - if anyone else remembers it? 

Classic.

Best of luck and please don't hesitate to let me know if I can be of any help here.  In the meantime, fly low and avoid the radar here!   

    - ja

[mampy]

Thanks,

 I got mamp into the applications folder and started up the main 'thingy' and it
picked port 8888 and 8889 and not 80 and 3389 ... if i try to switch them around
only one or the other will run...     Maybe apache is already running? How would
i find the 'services running' to see if ive got apache installed somewhere else through
itunes or the rss music thingy where would i look?

 I can code a little, can hack and hold my own ... Not much of a mac  expert because they run so well i never had to be.  Id like to get into this php craze evidently its the holy grail?

Mampy

[jairez]

Mampy ... apologies for the delayed response.  Olympic fever has consumed my evenings

Re ports ... I believe any web port number below 1024 requires no authentication and Mamp is trying to stay within the secure port range for Apache and the only thing I can think is that 8888, and 8889 were easy to remember.  Not certain why they went away from 3389 for MySQL, unless the MAMP folks are concerned about stepping on previous MySQL installs.

Since Apache and MySQL do not run as services they should not show up when you run "which apache" and "which MySQL," so if you're seeing anything there then most likely you are indeed running the shared web service (at least).  To double-check, go to System Preferences -> Sharing (under Internet and Network) and see if anything's checked.  Here's what mine looks like (see image).

Hope this helps!  Let me know what's happening here.  Thanks, Mampy.

    -ja

[mampy]

Okay i got mamp installed on port 8888 and the new mysql port .. everything is
fine i even got wordpress and smf installed and opentracker (bitorrent opentracker i will post later but this is good stuff  )

I then looked at the web sharing, which was not on.
For giggles, i turned it on and saw what it did, it
put up some version of apache which i found at
/etc/apache2 and even changed the httpd.conf there
to listen 8080 as opposed to 80 and was able
to successfully connect to localhost:8080/ and
get that cheasy apache welcome screen with the
feather....  the other apache installation.  So now that
i have proven 80 was being used by first apache and i
have successfully changed first apache  (websharing)
to port 8080 i still can get mamp to go port 80.  So Mamp
doesnt block port 80 (for want of making you buy mamp pro)
or anything , you have mamp free running on port 80?

Thanks,
Stumpy Mampy lol

[perkiset]

Mampy - I split this topic off your "hello" thread because it has moved so far from just a hello and should be titled it's own thing. Hope you don't mind.

/p

[mampy]

Lol.. I thought i had problems staying on task.... 

^
|
\_ Like i said....   

Dont mind at all..

Perkiset, perhaps you could answer this question, i cant seem to get this
thing to start on port 80 but i just forwarded port 80 down from my firewall
to port 8888 on the MAMP machine... will this make a difference to an outside
sclient or can i just go forward with port 8888 on the inside NAT 'ed to port 80
to the outside world?

Mampy

[perkiset]

Internal ports make no difference at all, and this is actually a common firewall technique. Every one of my servers serve pages on ports other than 80 ... none of my renderers answer on port 80 at all. Only my front-edge firewalls do, which forward in to different ports. So if you have it started on 8080 or 8888 or whatever, it does not matter.

[mampy]

Excellent. Thank you this solves my problem then
and is more secure to boot?

I am now fully mamped (easy style).

It seems to be working fine.  Wish i could figure out
why port 80 wont bind to my new apache..

Thanks for all your help!

[perkiset]

Probably because the original Apache is still running and has already bound it. If you get to a terminal and do a ps aux while your new apache is not running, I'll bet you still see httpd daemons running.

[mampy]

You mean these lines:

Code:

_www      2819   0.0  0.1    78096   1860   ??  S    11:39AM   0:00.02 /usr/sbin/httpd -D FOREGROUND
_www      2761   0.0  0.1    78096   1868   ??  S    11:37AM   0:00.03 /usr/sbin/httpd -D FOREGROUND
root      2755   0.0  0.2    78096   3428   ??  Ss   11:37AM   0:01.64 /usr/sbin/httpd -D FOREGROUND
root      2679   0.0  0.1    75944    848 s000  S    11:35AM   0:00.10 sh

next question is, can i do a /usr/sbin/httpd stop    or something similar, how to kill the,m off?

[perkiset]

those'r them... if you click off Web Sharing these do not go away? Try clicking it off and restarting... a fresh terminal should show no httpd running when you ps aux. if You do see these running then there is more going on ... apache is starting automatically regardless of the Web Sharing option.

You can kill them if you are root with pkill httpd. You will need to sudo pkill httpd most likely.

[mampy]

I switch httpd.conf to Listen 8081 (some other port not affected by others)
Proved it worked by navigating to port 80 -> no response (good what i wanted)
navigated to port 8081 -> ugly feather thing apache (original) install switched to 8081  like i wanted.


THen i turned off web sharing.  For giggles, i restarted the box.

No httpd this time in ps aux but still if i go to change from port 8888 to
port 80 in the mamp application i gets no love.

  Oh well its working as i have it with the NAT solution.  i sure would like to know what is in the way..   If it wont affect my php programs to have that 8888 -> 80 thing then I can confidently continue and leave this problem to murphy?

Mampy

[perkiset]

yep ... that'll work all just fine.

This is predominantly why I "go to the root" for all of my stuff... something else entirely is messing with you, and I don't know if it's to do with MAMP or Apache or OS-X or or or or ... it's frustrating I agree. However, since you're up and running, all's well, eh?