You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@allura.apache.org by br...@apache.org on 2015/08/20 23:20:27 UTC
allura git commit: [#6797] update REST API docs link
Repository: allura
Updated Branches:
refs/heads/master a24b4dfaa -> 0a673b1e4
[#6797] update REST API docs link
Project: http://git-wip-us.apache.org/repos/asf/allura/repo
Commit: http://git-wip-us.apache.org/repos/asf/allura/commit/0a673b1e
Tree: http://git-wip-us.apache.org/repos/asf/allura/tree/0a673b1e
Diff: http://git-wip-us.apache.org/repos/asf/allura/diff/0a673b1e
Branch: refs/heads/master
Commit: 0a673b1e4e8c322a5cf20bc34723adc1f98e4710
Parents: a24b4df
Author: Dave Brondsema <da...@brondsema.net>
Authored: Thu Aug 20 17:20:20 2015 -0400
Committer: Dave Brondsema <da...@brondsema.net>
Committed: Thu Aug 20 17:20:20 2015 -0400
----------------------------------------------------------------------
Allura/docs/getting_started/administration.rst | 6 +++++-
Allura/docs/platform/scm.rst | 4 ++--
2 files changed, 7 insertions(+), 3 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/allura/blob/0a673b1e/Allura/docs/getting_started/administration.rst
----------------------------------------------------------------------
diff --git a/Allura/docs/getting_started/administration.rst b/Allura/docs/getting_started/administration.rst
index fc56e5a..1571cb6 100644
--- a/Allura/docs/getting_started/administration.rst
+++ b/Allura/docs/getting_started/administration.rst
@@ -285,8 +285,12 @@ that this documentation also covers some SourceForge features that are not part
Public API Documentation
========================
-Allura's web api is currently documented at https://sourceforge.net/p/forge/documentation/Allura%20API/
+All url endpoints are prefixed with /rest/ and the path to the project and tool.
+For example, in order to access a wiki installed in the 'test' project with the mount point 'docs' the API endpoint would be /rest/p/test/docs.
+
+`Explore Allura's REST API documentation here. <https://anypoint.mulesoft.com/apiplatform/forge-allura/#/portals/organizations/86c00a85-31e6-4302-b36d-049ca5d042fd/apis/32370/versions/33732>`_
+You can also try the API live there.
Client Scripts
==============
http://git-wip-us.apache.org/repos/asf/allura/blob/0a673b1e/Allura/docs/platform/scm.rst
----------------------------------------------------------------------
diff --git a/Allura/docs/platform/scm.rst b/Allura/docs/platform/scm.rst
index d8ab6d6..7569046 100644
--- a/Allura/docs/platform/scm.rst
+++ b/Allura/docs/platform/scm.rst
@@ -103,8 +103,8 @@ Last Commit Logic
Determining which commit was the last to touch a given set of files or
directories can be complicated, depending on the specific SCM tool.
Git and Mercurial require manually walking up the commit history to
-discover this information, while SVN can return it all from a singlle
-`info2` command (though the SVN call will be signficantly slower than
+discover this information, while SVN can return it all from a single
+`info2` command (though the SVN call will be significantly slower than
any individual call to Git or Mercurial). Because this can sometimes
be costly to generate, it is cached via the `allura.model.repository.LastCommit`
model. This will generate the data on demand by calling the underlying