bookkeeper-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From si...@apache.org
Subject [bookkeeper] branch master updated: ISSUE #453: fix image broken in website
Date Tue, 22 Aug 2017 18:34:51 GMT
This is an automated email from the ASF dual-hosted git repository.

sijie pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/bookkeeper.git


The following commit(s) were added to refs/heads/master by this push:
     new 35cffdf  ISSUE #453: fix image broken in website
35cffdf is described below

commit 35cffdf6a38b5dba702b11e5902d5aa745429b01
Author: Jia Zhai <zhaijia@apache.org>
AuthorDate: Tue Aug 22 11:34:43 2017 -0700

    ISSUE #453: fix image broken in website
    
    Descriptions of the changes in this PR:
    Fix image broken in website
    
    After fix, image works well.
    <img width="1535" alt="default" src="https://user-images.githubusercontent.com/26834121/29500286-ee3e4d88-8651-11e7-80c2-d4febffb0bfe.png">
    
    Author: Jia Zhai <zhaijia@apache.org>
    
    Reviewers: Enrico Olivelli <eolivelli@gmail.com>, Sijie Guo <sijie@apache.org>
    
    This closes #455 from zhaijack/issue_453, closes #453
---
 site/docs/4.5.0/api/distributedlog-api.md  | 4 ++--
 site/docs/4.5.0/deployment/dcos.md         | 8 ++++----
 site/docs/latest/api/distributedlog-api.md | 4 ++--
 site/docs/latest/deployment/dcos.md        | 8 ++++----
 4 files changed, 12 insertions(+), 12 deletions(-)

diff --git a/site/docs/4.5.0/api/distributedlog-api.md b/site/docs/4.5.0/api/distributedlog-api.md
index 7bb4029..c143384 100644
--- a/site/docs/4.5.0/api/distributedlog-api.md
+++ b/site/docs/4.5.0/api/distributedlog-api.md
@@ -13,7 +13,7 @@ DistributedLog (DL) maintains sequences of records in categories called
*logs* (
 
 The diagram below illustrates how the DistributedLog API works with BookKeeper:
 
-![DistributedLog API](../../../img/distributedlog.png)
+![DistributedLog API]({{ site.baseurl }}img/distributedlog.png)
 
 ## Logs
 
@@ -21,7 +21,7 @@ A *log* in DistributedLog is an ordered, immutable sequence of *log records*.
 
 The diagram below illustrates the anatomy of a log stream:
 
-![DistributedLog log](../../../img/logs.png)
+![DistributedLog log]({{ site.baseurl }}img/logs.png)
 
 ### Log records
 
diff --git a/site/docs/4.5.0/deployment/dcos.md b/site/docs/4.5.0/deployment/dcos.md
index 5f0c732..3e17438 100644
--- a/site/docs/4.5.0/deployment/dcos.md
+++ b/site/docs/4.5.0/deployment/dcos.md
@@ -41,25 +41,25 @@ The bookie that is automatically started up uses the host mode of the
network an
 
 To watch BookKeeper start up, click on the **Services** tab in the DC/OS [user interface](https://docs.mesosphere.com/latest/gui/)
and you should see the `bookkeeper` package listed:
 
-![DC/OS services](../../../img/dcos/services.png)
+![DC/OS services]({{ site.baseurl }}img/dcos/services.png)
 
 ### Tasks
 
 To see which tasks have started, click on the `bookkeeper` service and you'll see an interface
that looks like this;
 
-![DC/OS tasks](../../../img/dcos/tasks.png)
+![DC/OS tasks]({{ site.baseurl }}img/dcos/tasks.png)
 
 ## Scaling BookKeeper
 
 Once the first {% pop bookie %} has started up, you can click on the **Scale** tab to scale
up your BookKeeper ensemble by adding more bookies (or scale down the ensemble by removing
bookies).
 
-![DC/OS scale](../../../img/dcos/scale.png)
+![DC/OS scale]({{ site.baseurl }}img/dcos/scale.png)
 
 ## ZooKeeper Exhibitor
 
 ZooKeeper contains the information for all bookies in the ensemble. When deployed on DC/OS,
BookKeeper uses a ZooKeeper instance provided by DC/OS. You can access a visual UI for ZooKeeper
using [Exhibitor](https://github.com/soabase/exhibitor/wiki), which is available at [http://master.dcos/exhibitor](http://master.dcos/exhibitor).
 
-![ZooKeeper Exhibitor](../../../img/dcos/exhibitor.png)
+![ZooKeeper Exhibitor]({{ site.baseurl }}img/dcos/exhibitor.png)
 
 You should see a listing of IP/host information for all bookies under the `messaging/bookkeeper/ledgers/available`
node.
 
diff --git a/site/docs/latest/api/distributedlog-api.md b/site/docs/latest/api/distributedlog-api.md
index 0b12e1d..466bcd8 100644
--- a/site/docs/latest/api/distributedlog-api.md
+++ b/site/docs/latest/api/distributedlog-api.md
@@ -13,7 +13,7 @@ DistributedLog (DL) maintains sequences of records in categories called
*logs* (
 
 The diagram below illustrates how the DistributedLog API works with BookKeeper:
 
-![DistributedLog API](../../../img/distributedlog.png)
+![DistributedLog API]({{ site.baseurl }}img/distributedlog.png)
 
 ## Logs
 
@@ -21,7 +21,7 @@ A *log* in DistributedLog is an ordered, immutable sequence of *log records*.
 
 The diagram below illustrates the anatomy of a log stream:
 
-![DistributedLog log](../../../img/logs.png)
+![DistributedLog log]({{ site.baseurl }}img/logs.png)
 
 ### Log records
 
diff --git a/site/docs/latest/deployment/dcos.md b/site/docs/latest/deployment/dcos.md
index da8b115..dab023d 100644
--- a/site/docs/latest/deployment/dcos.md
+++ b/site/docs/latest/deployment/dcos.md
@@ -41,25 +41,25 @@ The bookie that is automatically started up uses the host mode of the
network an
 
 To watch BookKeeper start up, click on the **Services** tab in the DC/OS [user interface](https://docs.mesosphere.com/latest/gui/)
and you should see the `bookkeeper` package listed:
 
-![DC/OS services](../../../img/dcos/services.png)
+![DC/OS services]({{ site.baseurl }}img/dcos/services.png)
 
 ### Tasks
 
 To see which tasks have started, click on the `bookkeeper` service and you'll see an interface
that looks like this;
 
-![DC/OS tasks](../../../img/dcos/tasks.png)
+![DC/OS tasks]({{ site.baseurl }}img/dcos/tasks.png)
 
 ## Scaling BookKeeper
 
 Once the first {% pop bookie %} has started up, you can click on the **Scale** tab to scale
up your BookKeeper ensemble by adding more bookies (or scale down the ensemble by removing
bookies).
 
-![DC/OS scale](../../../img/dcos/scale.png)
+![DC/OS scale]({{ site.baseurl }}img/dcos/scale.png)
 
 ## ZooKeeper Exhibitor
 
 ZooKeeper contains the information for all bookies in the ensemble. When deployed on DC/OS,
BookKeeper uses a ZooKeeper instance provided by DC/OS. You can access a visual UI for ZooKeeper
using [Exhibitor](https://github.com/soabase/exhibitor/wiki), which is available at [http://master.dcos/exhibitor](http://master.dcos/exhibitor).
 
-![ZooKeeper Exhibitor](../../../img/dcos/exhibitor.png)
+![ZooKeeper Exhibitor]({{ site.baseurl }}img/dcos/exhibitor.png)
 
 You should see a listing of IP/host information for all bookies under the `messaging/bookkeeper/ledgers/available`
node.
 

-- 
To stop receiving notification emails like this one, please contact
['"commits@bookkeeper.apache.org" <commits@bookkeeper.apache.org>'].

Mime
View raw message