- #Mamp pro port 80 apache conflict pdf
- #Mamp pro port 80 apache conflict install
- #Mamp pro port 80 apache conflict code
Library/Server/Migrated/private/etc/apache2/original/nf Library/Server/Migrated/private/etc/apache2/nf Since I have MAMP now, /Applications/MAMP/conf/apacheĪlso one in /Applications/MAMP PRO./MAMP PRO.app/Contesnts/Resources/ In fact on my system they are in SEVERAL locations. Since it is merely a unix type command line executable it should run fine from a terminal shell and take a filename as input.Īlso, while i'm sure this is not the case, you are hitting not just hitting the file itself directly right?Īs for osx installed apache, and MAMP apache, the only real difference is that the setup files are in different locations. IF not you will probably see some type of error that might give a clue. In the file, something simple to test would be cool. irev since we added those extentions to the addhandler line) Place a file in your /Applications/MAMP/htdocs folder named something like test.lc (or. If MAMP is running, shut it down, and restart. Change it to add ExecCGI as an option so that it looks like this: Options Indexes FollowSymLinks ExecCGI irevġ0) add another line right after that looks as follows: Action lc-script /cgi-bin/livecode-serverġ2) there should be a line in that section for Options. cgiĩ) add a line after the #addhandler that looks as follows: AddHandler lc-script. Search for AddHandler and locate the line that looks like #AddHandler cgi-script. (read, write, exe by me, readable only by group and everyone)Ħ) switch to the conf directory /Applications/MAMP/conf/apacheħ) edit nf with whatever editor you wish, I use vi but anything that doesn't hork the line endings should be fine Permissions are 755 though I suspect 744 would work ok too. permissions are 755 (chmod 755 livecode-server)ĥ) I have the 2 folders and their contents also owned by me and admin.
#Mamp pro port 80 apache conflict install
I know you've already got it installed but i'm going to go through all the steps I took to get there.ġ) install mamp (drag the folder to applicationsģ) copy livecode-server and its 2 folders (externals and drivers) to /Applications/MAMP/cgi-bin (and changed to cgi-bin)Ĥ) check permissions and ownership of livecode-server I have mine set with me as owner, admin as group. Downloaded mamp, installed it, i'm ignoring mamp pro and editing files by hand. php and at least it displays the html parts.
#Mamp pro port 80 apache conflict code
The code inside the LiveCode markup does nothing. lc file? I can name the file index.crapola and it performs the same when called explicitly. The apache log files do not indicate any kind of issue.Ĭould it be the combination or the components of Mountain Lion or MAMP Pro instead of an older version of OS X and MAMP?Īm confused also with the changing filename suffixes. But I still cannot discern where the problem is.
I've followed the directions in Simon's living document.
#Mamp pro port 80 apache conflict pdf
I followed the directions in the PDF that comes with the server. I also have MAMP Pro and have done everything that I can think of to get LiveCodeServer to work, but to no avail. I am creating a development machine with an iMac running the latest OS X 10.8.
0 kommentar(er)
