Use absolute doc urls

Author: Zinidia

docs/backend/README.md

@@ -1,5 +1,5 @@
 # Obstor Backend
-Obstor Backend adds S3 and [other supported protocol](../protocols/README.md) compatibility to third-party cloud storage providers.
+Obstor Backend adds S3 and [other supported protocol](https://obstor.net/docs/protocols) compatibility to third-party cloud storage providers.
 
 ## Supported Backends
 - [NAS](nas.md)
@@ -10,6 +10,6 @@ Obstor Backend adds S3 and [other supported protocol](../protocols/README.md) co
 - [SFTP](sftp.md)
 
 ## Explore Further
-- [Supported Protocols](../protocols/README.md) - S3, SFTP, and more
+- [Supported Protocols](https://obstor.net/docs/protocols) - S3, SFTP, and more
 - [`mc` command-line interface](https://obstor.net/docs/obstor-client-quickstart-guide)
 - [`aws` command-line interface](https://obstor.net/docs/aws-cli-with-obstor)

docs/backend/azure.md

@@ -1,5 +1,5 @@
 # Obstor Azure Backend
-Obstor Backend adds S3 and [other supported protocol](../protocols/README.md) compatibility to Microsoft Azure Blob Storage.
+Obstor Backend adds S3 and [other supported protocol](https://obstor.net/docs/protocols) compatibility to Microsoft Azure Blob Storage.
 
 ## Run Obstor Backend for Microsoft Azure Blob Storage
 ### Using Docker
@@ -53,7 +53,7 @@ Other limitations:
 - Bucket notification APIs are not supported.
 
 ## Explore Further
-- [Supported Protocols](../protocols/README.md) - S3, SFTP, and more
+- [Supported Protocols](https://obstor.net/docs/protocols) - S3, SFTP, and more
 - [`mc` command-line interface](https://obstor.net/docs/obstor-client-quickstart-guide)
 - [`aws` command-line interface](https://obstor.net/docs/aws-cli-with-obstor)
 - [`minio-go` Go SDK](https://obstor.net/docs/golang-client-quickstart-guide)

docs/backend/gcs.md

@@ -1,6 +1,6 @@
 # Obstor GCS Backend
 
-Obstor GCS Backend allows you to access Google Cloud Storage (GCS) with S3-compatible APIs and [other supported protocols](../protocols/README.md)
+Obstor GCS Backend allows you to access Google Cloud Storage (GCS) with S3-compatible APIs and [other supported protocols](https://obstor.net/docs/protocols)
 
 - [Run Obstor Backend for GCS](#run-obstor-backend-for-gcs)
 - [Test Using Browser Dashboard](#test-using-obstor-browser)
@@ -83,7 +83,7 @@ Other limitations:
 * Bucket notification APIs are not supported.
 
 ## <a name="explore-further"></a>4. Explore Further
-- [Supported Protocols](../protocols/README.md) - S3, SFTP, and more
+- [Supported Protocols](https://obstor.net/docs/protocols) - S3, SFTP, and more
 - [`mc` command-line interface](https://obstor.net/docs/obstor-client-quickstart-guide)
 - [`aws` command-line interface](https://obstor.net/docs/aws-cli-with-obstor)
 - [`minio-go` Go SDK](https://obstor.net/docs/golang-client-quickstart-guide)

docs/backend/hdfs.md

@@ -1,5 +1,5 @@
 # Obstor HDFS Backend
-Obstor HDFS backend adds S3 API and [other supported protocol](../protocols/README.md) support to Hadoop HDFS filesystem. Applications can use both the S3 and file APIs concurrently without requiring any data migration. Since the backend is stateless and shared-nothing, you may elastically provision as many Obstor instances as needed to distribute the load.
+Obstor HDFS backend adds S3 API and [other supported protocol](https://obstor.net/docs/protocols) support to Hadoop HDFS filesystem. Applications can use both the S3 and file APIs concurrently without requiring any data migration. Since the backend is stateless and shared-nothing, you may elastically provision as many Obstor instances as needed to distribute the load.
 
 > NOTE: Intention of this backend implementation it to make it easy to migrate your existing data on HDFS clusters to Obstor clusters using standard tools like `mc` or `aws-cli`, if the goal is to use HDFS perpetually we recommend that HDFS should be used directly for all write operations.
 
@@ -101,7 +101,7 @@ Backend inherits the following limitations of HDFS storage layer:
 - Concurrent multipart operations are not supported (HDFS lacks safe locking support, or poorly implemented)
 
 ## Explore Further
-- [Supported Protocols](../protocols/README.md) - S3, SFTP, and more
+- [Supported Protocols](https://obstor.net/docs/protocols) - S3, SFTP, and more
 - [`mc` command-line interface](https://obstor.net/docs/obstor-client-quickstart-guide)
 - [`aws` command-line interface](https://obstor.net/docs/aws-cli-with-obstor)
 - [`minio-go` Go SDK](https://obstor.net/docs/golang-client-quickstart-guide)

docs/backend/nas.md

@@ -1,6 +1,6 @@
 # Obstor NAS Backend
 
-Obstor Backend adds S3 and [other supported protocol](../protocols/README.md) compatibility to NAS storage. You may run multiple obstor instances on the same shared NAS volume as a distributed object backend.
+Obstor Backend adds S3 and [other supported protocol](https://obstor.net/docs/protocols) compatibility to NAS storage. You may run multiple obstor instances on the same shared NAS volume as a distributed object backend.
 
 ## Run Obstor Backend for NAS Storage
 
@@ -93,7 +93,7 @@ NAS backend implementation allows symlinks on regular files,
 *Directory symlinks is not and will not be supported as there are no safe ways to handle them.*
 
 ## Explore Further
-- [Supported Protocols](../protocols/README.md) - S3, SFTP, and more
+- [Supported Protocols](https://obstor.net/docs/protocols) - S3, SFTP, and more
 - [`mc` command-line interface](https://obstor.net/docs/obstor-client-quickstart-guide)
 - [`aws` command-line interface](https://obstor.net/docs/aws-cli-with-obstor)
 - [`minio-go` Go SDK](https://obstor.net/docs/golang-client-quickstart-guide)

docs/backend/s3.md

@@ -128,7 +128,7 @@ With Obstor S3 backend, you can use Obstor browser to explore AWS S3 based objec
 
 ## Explore Further
 
-- [Supported Protocols](../protocols/README.md) - S3, SFTP, and more
+- [Supported Protocols](https://obstor.net/docs/protocols) - S3, SFTP, and more
 - [`mc` command-line interface](https://obstor.net/docs/obstor-client-quickstart-guide)
 - [`aws` command-line interface](https://obstor.net/docs/aws-cli-with-obstor)
 - [`minio-go` Go SDK](https://obstor.net/docs/golang-client-quickstart-guide)

docs/backend/sftp.md

@@ -1,8 +1,8 @@
 # Obstor SFTP Backend
 
-Obstor SFTP Backend adds S3 and [other supported protocol](../protocols/README.md) compatibility to any existing SFTP server. Use your SFTP server as the storage backend while accessing data through the S3 API and other supported protocols.
+Obstor SFTP Backend adds S3 and [other supported protocol](https://obstor.net/docs/protocols) compatibility to any existing SFTP server. Use your SFTP server as the storage backend while accessing data through the S3 API and other supported protocols.
 
-> Looking for the built-in SFTP server? See [SFTP Protocol](../protocols/sftp.md).
+> Looking for the built-in SFTP server? See [SFTP Protocol](https://obstor.net/docs/protocols/sftp).
 
 ## Run Obstor Backend for SFTP Storage
 
@@ -100,8 +100,8 @@ mc cp myfile.txt mysftp/newbucket/myfile.txt
 
 ## Explore Further
 
-- [Supported Protocols](../protocols/README.md) - S3, SFTP, and more
-- [Obstor Distributed Mode](../distributed/README.md)
-- [TLS Configuration](../tls/README.md)
-- [IAM & Policies](../multi-user/README.md)
-- [SFTP Protocol](../protocols/sftp.md) - built-in SFTP server for accessing Obstor via SFTP
+- [Supported Protocols](https://obstor.net/docs/protocols) - S3, SFTP, and more
+- [Obstor Distributed Mode](https://obstor.net/docs/distributed)
+- [TLS Configuration](https://obstor.net/docs/tls)
+- [IAM & Policies](https://obstor.net/docs/multi-user)
+- [SFTP Protocol](https://obstor.net/docs/protocols/sftp) - built-in SFTP server for accessing Obstor via SFTP

docs/config/README.md

@@ -86,7 +86,7 @@ obstor server /data
 ```
 
 ### Storage Class
-By default, parity for objects with standard storage class is set to `N/2`, and parity for objects with reduced redundancy storage class objects is set to `2`. Read more about storage class support in Obstor server [here](../erasure/storage-class/README.md).
+By default, parity for objects with standard storage class is set to `N/2`, and parity for objects with reduced redundancy storage class objects is set to `2`. Read more about storage class support in Obstor server [here](https://obstor.net/docs/erasure/storage-class).
 
 ```
 KEY:
@@ -172,7 +172,7 @@ OBSTOR_ETCD_COMMENT          (sentence)  optionally add a comment to this settin
 ```
 
 ### API
-By default, there is no limitation on the number of concurrent requests that a server/cluster processes at the same time. However, it is possible to impose such limitation using the API subsystem. Read more about throttling limitation in Obstor server [here](../throttle/README.md).
+By default, there is no limitation on the number of concurrent requests that a server/cluster processes at the same time. However, it is possible to impose such limitation using the API subsystem. Read more about throttling limitation in Obstor server [here](https://obstor.net/docs/throttle).
 
 ```
 KEY:

docs/deployment/cluster/README.md

@@ -16,7 +16,7 @@ The default replication factor is **3** - every block is stored on 3 independent
 
 This model provides strong consistency (read-after-write, list-after-write) while tolerating individual drive and node failures.
 
-> **NOTE:** Block-level replication differs from erasure coding. Replication stores full copies of each block, trading storage efficiency for simplicity and faster recovery. For erasure-coded deployments, see [Erasure Code Guide](../../erasure/README.md).
+> **NOTE:** Block-level replication differs from erasure coding. Replication stores full copies of each block, trading storage efficiency for simplicity and faster recovery. For erasure-coded deployments, see [Erasure Code Guide](https://obstor.net/docs/erasure).
 
 ## Node Quotas
 

docs/distributed/README.md

@@ -8,15 +8,15 @@ Obstor in distributed mode can help you setup a highly-available storage system
 
 ### Data protection
 
-Distributed Obstor provides protection against multiple node/drive failures and [bit rot](../erasure/README.md#what-is-bit-rot-protection) using [erasure code](https://obstor.net/docs/obstor-erasure-code-quickstart-guide). As the minimum disks required for distributed Obstor is 4 (same as minimum disks required for erasure coding), erasure code automatically kicks in as you launch distributed Obstor.
+Distributed Obstor provides protection against multiple node/drive failures and [bit rot](https://obstor.net/docs/erasure#what-is-bit-rot-protection) using [erasure code](https://obstor.net/docs/obstor-erasure-code-quickstart-guide). As the minimum disks required for distributed Obstor is 4 (same as minimum disks required for erasure coding), erasure code automatically kicks in as you launch distributed Obstor.
 
 ### High availability
 
 A stand-alone Obstor server would go down if the server hosting the disks goes offline. In contrast, a distributed Obstor setup with _m_ servers and _n_ disks will have your data safe as long as _m/2_ servers or _m*n_/2 or more disks are online.
 
 For example, an 16-server distributed setup with 200 disks per node would continue serving files, up to 4 servers can be offline in default configuration i.e around 800 disks down Obstor would continue to read and write objects.
 
-Refer to sizing guide for more understanding on default values chosen depending on your erasure stripe size [here](SIZING.md). Parity settings can be changed using [storage classes](../erasure/storage-class).
+Refer to sizing guide for more understanding on default values chosen depending on your erasure stripe size [here](https://obstor.net/docs/distributed/sizing). Parity settings can be changed using [storage classes](https://obstor.net/docs/erasure/storage-class).
 
 ### Consistency Guarantees