Hidden files & folders?

Posted:
in macOS edited January 2014
I have been trying to get Apache setup with my custom prefs, (php, cgi etc), but am having trouble finding the config files. I used the terminal and typed in httpd -t or whatever the command was to locate the config files, and it said where they were. I went in to look for them, and even the directories it stated were not there. If they were simply not there, it would not even start up, but it does and works. I am pretty stuck here, so any help/advice would be highly appreciated. Oh yeah, as a sidenote, using Dave I can read some files&folders I cannot see on the mac... Havent looked much with it, cause it was at a friends house, but otherwise I am lost.

Comments

  • Reply 1 of 2
    xeoxeo Posts: 33member
    All directories are visible from the command line. Many folders are hidden in in the Finder and I suspect that's where your problems are. You have several options for accessing those config files.



    First, know they are in /etc/httpd/



    My favorite is to use BBEdit 6.5 and choose "Open Hidden" from the File menu. You can traverse through directories, hidden or not, and find those config files to edit them.



    You can also type "CMD ~" in the finder or from the "Go" menu select "Go to Folder" and type /etc/httpd as the folder. At that point, you should be looking at a folder with all the config files in them.



    Yet another solution is to simply use the command line. Type "cd /etc/httpd" and then type "ls -l" and you'll see all the config files. You can use a command line based text editor like "pico" to edit these files.



    Like I said above, BBEdit is the best solution for editing the files. If you don't have write access to them (like with the httpd.conf file) BBEdit will give you the option to authenticate. It's very convenient and something the Finder should have available, IMO.
  • Reply 2 of 2
    Xeo left one little thing out...



    From the command line, any names that start with a period "." are invisible. To see these, instead of "ls -l" you need to use:



    ls -al



    [ 02-04-2002: Message edited by: starfleetX ]</p>
Sign In or Register to comment.