mirror of https://gitee.com/bigwinds/arangodb
updated docs
This commit is contained in:
parent
1e6fe40149
commit
52079ba667
|
@ -90,7 +90,6 @@ documents.
|
|||
The `_from` and `_to` attributes will of course be preserved and are still required when
|
||||
saving edges.
|
||||
|
||||
|
||||
!SECTION AQL
|
||||
|
||||
!SUBSECTION Edges handling
|
||||
|
@ -848,6 +847,19 @@ in 3.0 because the changes in server behavior controlled by this option were cha
|
|||
even before ArangoDB 2.0. This should have left enough time for client applications
|
||||
to adapt to the new behavior, making the option superfluous in 3.0.
|
||||
|
||||
!SECTION Authentication
|
||||
|
||||
The default value for `--server.authentication` is now `true` in the configuration
|
||||
files shipped with ArangoDB. This means the server will be started with authentication
|
||||
enabled by default, requiring all client connections to provide authentication data
|
||||
when connecting to ArangoDB. Previous ArangoDB versions used the setting
|
||||
`--server.disable-authentication true`, effectively disabling authentication by default.
|
||||
|
||||
Though enabling the authentication is recommended for production setups, it may be
|
||||
overkill in a development environment. To turn off authentication, the option
|
||||
`--server.authentication` can be set to `false` in ArangoDB's configuration file or
|
||||
on the command-line.
|
||||
|
||||
!SECTION Web Admin Interface
|
||||
|
||||
The JavaScript shell has been removed from ArangoDB's web interface. The functionality
|
||||
|
|
Loading…
Reference in New Issue