Note that for ad-hoc sharing it may be easier to just run hg serve on the command line. If you’re trying to host it on your local workstation for convenience, the second is easier, because then you can still access the repository from your current user. Which of the two is preferable depends on your situation: if you’re trying to host your repository on a server I would say the first is preferable, it is simpler and a little more secure. If the files are not readable or writable by the group, use the chmod command to make them: chmod -R go+rwX /Users/username/Documents/repository_nameĪnd you can change the group of your repository to _www like so: sudo chown -R :_www /Users/username/Documents/repository_name It should show something like drwxrwxr- in the first column (the middle rw are important) and _www in the fourth. If you type: ls -ld /Users/username/Documents/repository_name In this case you still need to make sure that the _www user has access at all. Note that if you change this, you should not access the repository on the file system from any other user, or else any newly created files will again have the wrong permissions.Īlternatively, explicitly add your user to the trusted section in your nfig: If not, change the user of the directory: sudo chown -R _www:_www /Users/username/Documents/repository_name It should show _www _www in the third and fourth column.
Personal firewall software will often block programs from connecting to the.
#OS X LION FIREWALL INSTALL#
When you type: ls -ld /Users/username/Documents/repository_name Control Click on the Install OS X Mountain Lion app and choose Show. Make the repository owned by the Apache _www user.
#OS X LION FIREWALL MAC OS X#
On a standard Mac OS X Apache install the web user and group are _There are two ways to fix it: This indeed looks like a permissions problem.
#OS X LION FIREWALL HOW TO#
Were I to guess I'd say it was some sort of access or permissions issue but I'm not familiar enough with Apache or Mac OS X Lion to venture a guess as to how to fix it. On the main page I'm getting similar errors in Apache: error accessing repository at /Users/username/Documents/repository_name Well, the directory is valid and there is a valid repository there according to Mercurial (i.e., hg log and similar commands don't error out)
Repository /Users/username/Documents/repository_name not found ipfw was the built-in firewall of Mac OS X until Mac OS X 10.7 Lion in 2011 when it was replaced with the OpenBSD projects PF. So I should be able to get to a repository via but instead I'm getting a nice Mercurial page telling me An error has occured while processing your request: It can either be used as a loadable kernel module or incorporated into the kernel use as a loadable kernel module where possible is highly recommended. I can, however, get a listing of them at where /hg is the ScriptAlias address. It says that I should be able to access a repository at but that doesn't work. I did make the modification that I did not use https because the machine in question is behind my company's firewall. That article is for Snow Leopard (I guess no one's tried to do this on Lion yet?) but it mostly works. I'm trying to get Mercurial to serve using hgwebdir.cgi under Apache on Mac OS X Lion.
0 kommentar(er)
