[EAGLE-1072] Fixing SHA link

{% comment %}
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements.  See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
The ASF licenses this file to you under the Apache License, Version 2.0
(the "License"); you may not use this file except in compliance with
the License.  You may obtain a copy of the License at


Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
See the License for the specific language governing permissions and
limitations under the License.
{% endcomment %}

Be sure to do all of the following to help us incorporate your contribution
quickly and easily:

 - [ ] Make sure the PR title is formatted like:
   `[EAGLE-<Jira issue #>] Description of pull request`
 - [ ] Make sure tests pass via `mvn clean verify`. (Even better, enable
       Travis-CI on your fork and ensure the whole test matrix passes).
 - [ ] Replace `<Jira issue #>` in the title with the actual Jira issue
       number, if there is one.
 - [ ] If this contribution is large, please file an Apache
       [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.txt).


Author: Colm O hEigeartaigh <coheigea@apache.org>

Closes #974 from coheigea/EAGLE-1072.
1 file changed
tree: 432afe682690634e8e42650acc810effb41704b4
  1. .github/
  2. _includes/
  3. _layouts/
  4. _posts/
  5. _sass/
  6. _site/
  7. css/
  8. data/
  9. fonts/
  10. images/
  11. js/
  12. .gitignore
  13. .travis.yml
  14. _config.yml
  15. about.md
  16. ambari-plugin-install.md
  17. application-configuration.md
  18. cloudera-integration.md
  19. community.md
  20. deployment-in-production.md
  21. deployment-in-sandbox.md
  22. development-in-intellij.md
  23. development-in-macosx.md
  24. development-quick-guide.md
  25. documentation.md
  26. download-latest.md
  27. download.md
  28. ecosystem.md
  29. FAQ.md
  30. feed.xml
  31. get-started-with-docker.md
  32. hbase-auth-activity-monitoring.md
  33. hbase-data-activity-monitoring.md
  34. hdfs-auth-activity-monitoring.md
  35. hdfs-data-activity-monitoring.md
  36. hive-query-activity-monitoring.md
  37. import-hdfs-auditLog.md
  38. index.html
  39. install.md
  40. introduction.md
  41. jmx-metric-monitoring.md
  42. mapr-integration.md
  43. metadata-api.md
  44. policy-capabilities.md
  45. quick-start-0.3.0.md
  46. quick-start.md
  47. README.md
  48. security.md
  49. serviceconfiguration.md
  50. setup-env.md
  51. standalone-install.md
  52. terminology.md
  53. tutorial-classfication-0.3.0.md
  54. tutorial-classfication.md
  55. tutorial-ldap.md
  56. tutorial-notificationplugin.md
  57. tutorial-policy.md
  58. tutorial-site-0.3.0.md
  59. tutorial-site.md
  60. tutorial-topologymanagement.md
  61. tutorial-userprofile.md
  62. usecases.md
  63. user-profile-ml.md

Eagle Documentation Site

Welcome to the Apache Eagle documentation!


Install jekyll gem

$ gem install jekyll

Generate the site, and start a server locally:

$ jekyll serve -w

The -w option tells jekyll to watch for changes to files and regenerate the site automatically when any content changes.

Point your browser to http://localhost:4000

By default, jekyll will generate the site in a _site directory.

Editing documentations

  1. Create a markdown file and add following content in header

     layout: doc
     title:  "Eagle Overview" 
     permalink: /docs/some-new-doc.html
     More content here ..
  2. Register the link in documentations sidebar navigation

       - category: "Some category"
           - title: Some new doc
             url: /docs/some-new-doc.html

Publishing the Apache Website

In order to publish the website, you must have committer access to Eagle's subversion repository.

The Eagle website is published using Apache svnpubsub. Any changes committed to subversion will be automatically published to eagle.apache.org.

To publish changes, tell jekyll to generate the site in the publish directory of subversion, then commit the changes:

cd docs
jekyll build -d /path/to/svn/repo/publish
cd /path/to/svn/repo/publish
svn commit