-
Notifications
You must be signed in to change notification settings - Fork 43
Merge EE docs #3759
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merge EE docs #3759
Conversation
71ffc47
to
98cee5c
Compare
0ee50d9
to
68401a0
Compare
6edef13
to
22e22ba
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍
I've got one general comment: let's maybe check and fix product names and abbreviations across the documentation?
- Tarantool Enterprise Edition or Tarantool EE instead of Tarantool Enterprise
- Tarantool Community Edition instead of open-source Tarantool and similar names.
And what about site header menu items that lead to old location of EE docs? Both site header menu and documentation header menu. |
Here is the PR with redirects (still in progress): https://github.com/tarantool/tarantool.io/pull/1453. So, |
I'd ask devX team about updating the links to decrease the number of redirected requests. They can cause unnecessary load on the website. |
Fixed: |
7eeb2cd
to
c25377f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
f83bb93
to
047096c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for this impressive work!
Please find my notes about the wording and naming in comments.
@@ -90,7 +90,7 @@ There are two functions for managing passwords in Tarantool: | |||
|
|||
* :doc:`/reference/reference_lua/box_schema/user_password` returns a hash of a user's password. | |||
|
|||
Tarantool Enterprise also allows you to improve database security by enforcing the use of strong passwords, setting up a maximum password age, and so on. Learn more from the `Access control <https://www.tarantool.io/en/enterprise_doc/security/#access-control>`__ section. | |||
Tarantool Enterprise Edition also allows you to improve database security by enforcing the use of strong passwords, setting up a maximum password age, and so on. Learn more from the :ref:`Access control <enterprise-access-control>` section. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor: Learn more from ... Access control ...
- we're already in a section with this name :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I hope, these section will be merged at some point )
doc/enterprise/audit.rst
Outdated
Encryption of external iproto traffic | ||
------------------------------------- | ||
|
||
Tarantool Enterprise Edition uses the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tarantool Enterprise Edition uses the | |
Tarantool uses the |
Any Tarantool does this.
doc/enterprise/audit.rst
Outdated
Security audit | ||
============== | ||
|
||
This document will help you audit the security of a Tarantool Enterprise Edition's cluster. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Possessive looks incorrect here. If Tarantool Enterprise Edition
is a product name, then it should be in the simple form, just as Tarantool cluster
, GridGain cluster
(not Tarantool's cluster
).
doc/enterprise/audit_log.rst
Outdated
Audit module | ||
============ | ||
|
||
The Tarantool audit module available in Tarantool Enterprise Edition writes messages that record Tarantool events in plain text, CSV, or JSON format. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The Tarantool audit module available in Tarantool Enterprise Edition writes messages that record Tarantool events in plain text, CSV, or JSON format. | |
The audit module available in Tarantool Enterprise Edition writes messages that record Tarantool events in plain text, CSV, or JSON format. |
doc/enterprise/changelog.rst
Outdated
Versioning policy | ||
----------------- | ||
|
||
A Tarantool Enterprise Edition's SDK version consists of two parts: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure about this wording - Tarantool Enterprise Edition's SDK
. Sounds a bit unnatural to me.
The old Tarantool Enterprise SDK
sound better – it's not the same product (Tarantool EE), but a toolkit for creating application to work with it. Better to check with PMs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
agree
@@ -18,4 +18,4 @@ This reference covers third-party Lua modules for Tarantool. | |||
other | |||
|
|||
For Tarantool Enterprise modules, see the | |||
`Tarantool Enterprise documentation <https://www.tarantool.io/en/enterprise_doc/rocksref/>`_. | |||
:ref:`Tarantool Enterprise Edition <enterprise-rocks>` documentation. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
:ref:`Tarantool Enterprise Edition <enterprise-rocks>` documentation. | |
:ref:`Tarantool EE <enterprise-rocks>` documentation. |
Since we've already mentioned Enterprise explicitly in this sentence.
@@ -10,4 +10,4 @@ that is hosted externally -- mostly on GitHub pages or in READMEs: | |||
* `tracing <https://github.com/tarantool/tracing/>`_ | |||
|
|||
For Tarantool Enterprise modules, see the | |||
`Tarantool Enterprise documentation <https://www.tarantool.io/en/enterprise_doc/rocksref/>`_. | |||
:ref:`Tarantool Enterprise Edition <enterprise-rocks>` documentation. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
:ref:`Tarantool Enterprise Edition <enterprise-rocks>` documentation. | |
:ref:`Tarantool EE <enterprise-rocks>` documentation. |
doc/enterprise/read_views/c_api.rst
Outdated
@@ -0,0 +1,274 @@ | |||
.. _read_views_c_api: | |||
|
|||
C API |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perhaps we need more specific names for C API and Lua API pages. Now they appear first in search results for "C API" and "Lua API" queries across all Tarantool docs, which doesn't seem right.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Definitely. Will rename to Read views: Lua API
and Read views: C API
for now. But, I hope they will be moved to box
reference at some moment.
047096c
to
7302bec
Compare
a8b2774
to
fac4159
Compare
Moved Enterprise documentation from a separate repo to the
doc
repo:https://docs.d.tarantool.io/en/doc/merge-ee-docs/enterprise/
Note that this still PR doesn't include reference for closed source modules. A related issue will be fixed lately: https://github.com/tarantool/enterprise_doc/issues/245.