mirror of
https://github.com/facebook/sapling.git
synced 2024-10-11 01:07:15 +03:00
6d898e296f
I've been using `hg serve --web-conf ...` with a simple '/=projects/**' [paths] configuration for awhile without issue. Let's ditch the need for the manual configuration in this case, and limit the repos served to the actual subrepos. This doesn't attempt to handle the case where a new subrepo appears while the server is running. That could probably be handled with a hook if somebody wants it. But it's such a rare case, it probably doesn't matter for the temporary serves. The main repo is served at '/', just like a repository without subrepos. I'm not sure why the duplicate 'adding ...' lines appear on Linux. They don't appear on Windows (see 3f4ff1bdf101), so they are optional. Subrepositories that are configured with '../path' or absolute paths are not cloneable from the server. (They aren't cloneable locally either, unless they also exist at their configured source, perhaps via the share extension.) They are still served, so that they can be browsed, or cloned individually. If we care about that cloning someday, we can probably just add the extra entries to the webconf dictionary. Even if the entries use '../' to escape the root, only the related subrepositories would end up in the dictionary. |
||
|---|---|---|
| .. | ||
| internals | ||
| bundlespec.txt | ||
| color.txt | ||
| common.txt | ||
| config.txt | ||
| dates.txt | ||
| diffs.txt | ||
| environment.txt | ||
| extensions.txt | ||
| filesets.txt | ||
| glossary.txt | ||
| hg-ssh.8.txt | ||
| hg.1.txt | ||
| hgignore.5.txt | ||
| hgignore.txt | ||
| hgrc.5.txt | ||
| hgweb.txt | ||
| merge-tools.txt | ||
| pager.txt | ||
| patterns.txt | ||
| phases.txt | ||
| revisions.txt | ||
| scripting.txt | ||
| subrepos.txt | ||
| templates.txt | ||
| urls.txt | ||