diff --git a/README.md b/README.md index eee6af41ecb..7a09c3655e9 100644 --- a/README.md +++ b/README.md @@ -39,7 +39,7 @@ Provide efficient, stable, secure, low-cost file and image distribution services **CDN:** A CDN server that caches downloaded data from source to avoid downloading same files repeatedly. -**Daemon:** Used for pulling images only. It establishes a proxy between containerd/CRI-O and registry. +**Daemon:** It's a daemon of dfget client. It establishes a proxy between containerd/CRI-O and registry. **Dfget:** The client of Dragonfly used for downloading files. It's similar to wget. diff --git a/docs/README.md b/docs/README.md index f1016a39b0a..df2074923b9 100644 --- a/docs/README.md +++ b/docs/README.md @@ -1,2 +1,6 @@ -# Contributing to Dragonfly Docs +# Dragonfly Document + +[English](./en/README.md) + +[TODO 简体中文](./zh-CN/README.md) diff --git a/docs/en/README.md b/docs/en/README.md new file mode 100644 index 00000000000..6eb5046b334 --- /dev/null +++ b/docs/en/README.md @@ -0,0 +1,76 @@ +# Dragonfly Document + +Dragonfly Document is written, drawn, memorialized representation of all things about Dragonfly. For those who are generally interested in Dragonfly, README.md of this repo is sufficient. While for end users, all details contained in `/docs` is the best guide all should have. And for developers, contents in Developer Guide part is that all need. + +Organization of document is as following: + +* [Quick Start](#Quick-Start) +* [User Guide](#User-Guide) +* [CLI Reference](#CLI-Reference) + * [WIP dfget](./cli-reference/dfget.md) + * [WIP cdnsystem](./cli-reference/cdn.md) + * [WIP scheduler](./cli-reference/scheduler.md) + * [TODO manager](./cli-reference/manager.md) +* [TODO API Reference](#API-Reference) +* [Ecosystem](#Ecosystem) + * [WIP Kubernetes Integration](./ecosystem/Kubernetes-with-Dragonfly.md) + * [WIP Harbor Integration](./ecosystem/Harbor-with-Dragonfly.md) +* [Developer Guide](#Developer-Guide) + * [Design Doc](#Design-Doc) + * [Test Guide](#Test-Guide) + +## How to Contribute Document + +Find `WIP` or `TODO` in this page and follow [CONTRIBUTING](../../CONTRIBUTING.md). + +## Quick Start + +[TODO Quick Started](./quick-start) is exactly what you need if you would give Dragonfly a try. This document includes what are the prerequisites, how to install Dragonfly and how to experience Dragonfly's usage. + +## [WIP] User Guide + +[User Guide](./user-guide) helps all kinds of guidance end users need to experience Dragonfly. Not only the very brief [Quick Start](./quick-start), but the detailed binary installation and configure illustration. In addition, any concept and function which help users understand Dragonfly better would be included as well. + +## [WIP] CLI Reference + +For almost all users, commandline is the first reference you may need. Document in directory [CLI Reference](./cli-reference) is about command detailed usage of Dragonfly CLI including `dfget`, `cdnsystem`, `scheduler` and `manager`. You can get introductions, synopsis, examples, options about command. Last but not least, Dragonfly can guarantee commandline docs is strongly consistent with Dragonfly CLI's source code. What's more, all commandline docs are auto generated via source code. + +## [TODO] API Reference + +Commandline is the easiest way to experience Dragonfly's ability. API extension will bring more further experience of Dragonfly. Commandline is just one kind of combination usage of API, if you wish to hack or take more advantages of Dragonfly, please see [API Reference](./api-reference). Like command line document, all API docs are auto generated via source code. + +## [WIP] Ecosystem + +Ecosystem documents show connections between Dragonfly and popular tool or system in cloud native ecosystem. They guide end users how to experience cloud native systems with Dragonfly, such as other CNCF project Kubernetes and Harbor. + +## [WIP] Developer Guide + +Develop Guide helps (potential) developers/contributors to understand the theory inside Dragonfly rather than the interface it exposes. With better understanding of how Dragonfly is designed, developer could learn source code of Dragonfly much easier and know how to debug, test and hack. + +### [TODO] Design Doc + +[Design Doc](./design) is content all about design of Dragonfly. It includes all things taken into consideration at the very beginning, the architecture designed for all components in Dragonfly, the interactive workflow between components, all APIs in Dragonfly and some technical things else. + +### [TODO] Test Guide + +[Test Guide](./test-guide) is the best reference helping contributors get aware of how to setup testing environment and do it. Currently we can divide test of Dragonfly into four dimensions: + +* unit test; +* API integration test; +* CLI integration test; +* node e2e test. + +For more details, please refer to [test](./test-guide). + +## Conclusion + +The folder `/docs` does not contain all the document about Dragonfly. There are still other really helpful documents in other path of this repo, like: + +* [TODO FAQ.md](../FAQ.md) +* [CHANGELOG.md](../../CHANGELOG.md) +* [TODO ROADMAP.md](../../ROADMAP.md) +* others. + +If you are searching some document and find no one, please do not hesitate to [file an ISSUE](https://github.com/dragonflyoss/Dragonfly2/issues/new/choose) for help. In addition, if you found that there are some incorrect places or typos in document, please help submit a pull request to correct that. + + diff --git a/docs/en/config/dfget.yaml b/docs/en/config/dfget.yaml index c7a1b651f50..b425410db0b 100644 --- a/docs/en/config/dfget.yaml +++ b/docs/en/config/dfget.yaml @@ -5,17 +5,6 @@ alive_time: 0s # daemon gc task running interval gc_interval: 1m0s -# daemon pid location -# in linux, default value is /var/run/dfdaemon.pid -# in macos(just for testing), default value is /tmp/dfdaemon.pid -pid_file: /var/run/dfdaemon.pid - -# daemon lock file location -# same lock file will only allow to run one daemon service -# in linux, default value is /var/run/dfdaemon.lock -# in macos(just for testing), default value is /tmp/dfdaemon.lock -lock_file: /var/run/dfdaemon.lock - # daemon data directory # in linux, default value is $HOME/.dragonfly/dfget-daemon/ # in macos(just for testing), default value is /Users/$USER/.dragonfly/dfdaemon/ diff --git a/docs/en/ecosystem/Harbor-with-Dragonfly.md b/docs/en/ecosystem/Harbor-with-Dragonfly.md new file mode 100644 index 00000000000..ba1ee0f391d --- /dev/null +++ b/docs/en/ecosystem/Harbor-with-Dragonfly.md @@ -0,0 +1,3 @@ +# [WIP] Harbor with Dragonfly + +This document will help you experience how to use dragonfly with harbor. \ No newline at end of file diff --git a/docs/en/ecosystem/Kubernetes-with-Dragonfly.md b/docs/en/ecosystem/Kubernetes-with-Dragonfly.md new file mode 100644 index 00000000000..ded75d7d589 --- /dev/null +++ b/docs/en/ecosystem/Kubernetes-with-Dragonfly.md @@ -0,0 +1 @@ +# [WIP] Kubernetes with Dragonfly \ No newline at end of file diff --git a/docs/en/user-guide/quick-start.md b/docs/en/user-guide/quick-start.md new file mode 100644 index 00000000000..de6f5fdee01 --- /dev/null +++ b/docs/en/user-guide/quick-start.md @@ -0,0 +1,3 @@ +# [WIP] Dragonfly Quick Start + +Dragonfly Quick Start document aims to help you to quick start Dragonfly journey. This experiment is quite easy and simplified. \ No newline at end of file