Skip to content

Conversation

andreyaksenov
Copy link
Contributor

@andreyaksenov andreyaksenov commented Oct 6, 2023

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.

PR for redirects is in the tarantool.io repo: https://github.com/tarantool/tarantool.io/pull/1453. Should be merged AFTER this PR.

@andreyaksenov andreyaksenov force-pushed the merge-ee-docs branch 2 times, most recently from 71ffc47 to 98cee5c Compare October 6, 2023 12:00
@andreyaksenov andreyaksenov linked an issue Oct 6, 2023 that may be closed by this pull request
19 tasks
@andreyaksenov andreyaksenov force-pushed the merge-ee-docs branch 27 times, most recently from 0ee50d9 to 68401a0 Compare October 11, 2023 08:39
@andreyaksenov andreyaksenov marked this pull request as ready for review October 11, 2023 09:49
@andreyaksenov andreyaksenov requested review from p7nov and xuniq October 11, 2023 09:49
@andreyaksenov andreyaksenov force-pushed the merge-ee-docs branch 3 times, most recently from 6edef13 to 22e22ba Compare October 11, 2023 12:23
Copy link
Contributor

@p7nov p7nov left a 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.

@p7nov
Copy link
Contributor

p7nov commented Oct 12, 2023

And what about site header menu items that lead to old location of EE docs? Both site header menu and documentation header menu.

@andreyaksenov
Copy link
Contributor Author

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, /enterprise_doc/ should be redirected to a new section.
I think, we can leave old EE links in Documentation drop-downs as is and update them later when restructuring docs.

@p7nov
Copy link
Contributor

p7nov commented Oct 12, 2023

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): tarantool/tarantool.io#1453. So, /enterprise_doc/ should be redirected to a new section. I think, we can leave old EE links in Documentation drop-downs as is and update them later when restructuring docs.

I'd ask devX team about updating the links to decrease the number of redirected requests. They can cause unnecessary load on the website.

@andreyaksenov
Copy link
Contributor Author

I'd ask devX team about updating the links to decrease the number of redirected requests.

Fixed:
https://github.com/tarantool/tarantool.io/pull/1453/commits/e6f3342a356e7ad55b2f4381f56de8e2e7ef7744

Copy link
Contributor

@xuniq xuniq left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

@andreyaksenov andreyaksenov force-pushed the merge-ee-docs branch 2 times, most recently from f83bb93 to 047096c Compare October 12, 2023 15:11
Copy link
Contributor

@p7nov p7nov left a 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.
Copy link
Contributor

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 :)

Copy link
Contributor Author

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 )

Encryption of external iproto traffic
-------------------------------------

Tarantool Enterprise Edition uses the
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Tarantool Enterprise Edition uses the
Tarantool uses the

Any Tarantool does this.

Security audit
==============

This document will help you audit the security of a Tarantool Enterprise Edition's cluster.
Copy link
Contributor

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).

Audit module
============

The Tarantool audit module available in Tarantool Enterprise Edition writes messages that record Tarantool events in plain text, CSV, or JSON format.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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.

Versioning policy
-----------------

A Tarantool Enterprise Edition's SDK version consists of two parts:
Copy link
Contributor

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.

Copy link
Contributor Author

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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
: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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
:ref:`Tarantool Enterprise Edition <enterprise-rocks>` documentation.
:ref:`Tarantool EE <enterprise-rocks>` documentation.

@@ -0,0 +1,274 @@
.. _read_views_c_api:

C API
Copy link
Contributor

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.

Copy link
Contributor Author

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.

@andreyaksenov andreyaksenov merged commit 0423ded into latest Oct 16, 2023
@andreyaksenov andreyaksenov deleted the merge-ee-docs branch October 16, 2023 12:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Epic] Merging CE and EE documentation
4 participants