You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/thehive/installation/deploying-a-cluster.md
+5-5Lines changed: 5 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -2,13 +2,13 @@
2
2
3
3
!!! Note
4
4
- This documentation applies to TheHive versions 5.4 and later. For earlier versions, [please refer to the Akka Configuration](../configuration/akka.md).
5
-
- This documentation applies for a fresh installationm for a new instance.
5
+
- This documentation applies for a fresh installation for a new instance.
6
6
7
7
This guide presents configuration examples for setting up a fault-tolerant cluster for TheHive. Each cluster comprises three active nodes, featuring:
8
8
9
9
- Cassandra for the database
10
10
- Elasticsearch for the indexing engine
11
-
- NFS (recommanded), or S3 file storage (for example MINIO)
11
+
- NFS (recommended), or S3 file storage (for example MINIO)
12
12
- TheHive
13
13
- Haproxy (to demonstrate load balancing)
14
14
- Keepalived (to demonstrate virtual IP setup)
@@ -164,7 +164,7 @@ To initialize the database, perform the following steps:
164
164
165
165
!!! Info "to prevent security issue, the cassandra default user will be removed from the base."
166
166
167
-
2.**Configure the system authentification replication**: Before creating a new users, you have to modify the default replication factor for the keyspace system_auth using the following cql command:
167
+
2.**Configure the system authentication replication**: Before creating a new users, you have to modify the default replication factor for the keyspace system_auth using the following cql command:
168
168
169
169
!!! Example ""
170
170
```sql
@@ -494,7 +494,7 @@ To set up a shared file storage for TheHive in a clustered environment, several
TheHive utilizes the pekko toolkit to effectively manage clusters and enhance scalability. pekko facilitates efficient management of threads and multi-processing, enabling TheHive to handle concurrent tasks seamlessly.
497
+
TheHive utilizes the Pekko toolkit to effectively manage clusters and enhance scalability. Pekko facilitates efficient management of threads and multi-processing, enabling TheHive to handle concurrent tasks seamlessly.
498
498
499
499
!!! Note
500
500
Apache Pekko is a toolkit designed for building highly concurrent, distributed, and resilient message-driven applications for Java and Scala.
@@ -507,7 +507,7 @@ TheHive utilizes the pekko toolkit to effectively manage clusters and enhance sc
507
507
508
508
### Configuration
509
509
#### Cluster
510
-
When configuring TheHive for a clustered environment, it's essential to configure pekko to ensure efficient management of the cluster by the application.
510
+
When configuring TheHive for a clustered environment, it's essential to configure Pekko to ensure efficient management of the cluster by the application.
511
511
512
512
In this guide, we assume that node 1 serves as the master node. Begin by configuring the ``pekko`` component in the ``/etc/thehive/application.conf`` file of each node as follows:
Copy file name to clipboardExpand all lines: docs/thehive/installation/upgrade-from-5.x.md
+6-6Lines changed: 6 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ Before proceeding with the upgrade, please keep the following points in mind:
13
13
14
14
1.**Database Backup**: We strongly recommend performing a full database backup before upgrading. For detailed instructions on how to perform a backup, please refer to the backup instructions.
15
15
16
-
2.**Downgrade Limitation**: Once upgraded to TheHive 5.4, your instance cannot be downgraded. This means reverting to a previous version of TheHive 5 will require restoring your data from the backup.
16
+
2.**Downgrade Limitation**: Once upgraded to TheHive 5.5, your instance cannot be downgraded. This means reverting to a previous version of TheHive 5 will require restoring your data from the backup.
17
17
18
18
3. When upgrading an existing TheHive 5.x instance, the first application launch will trigger a database evolution, including schema and data updates. This operation may take some time depending on your database size.
19
19
@@ -23,7 +23,7 @@ Before proceeding with the upgrade, please keep the following points in mind:
23
23
24
24
## Overview
25
25
26
-
This guide provides step-by-step instructions for upgrading an existing TheHive 5.x instance to TheHive 5.4.x.
26
+
This guide provides step-by-step instructions for upgrading an existing TheHive 5.x instance to TheHive 5.5.x.
27
27
28
28
---
29
29
@@ -43,7 +43,7 @@ TheHive 5.x deliverables are hosted in distinct package repositories. Depending
43
43
2. Edit the file ``/etc/apt/sources.list.d/strangebee.list`` and adjust the repository address as follows:
44
44
45
45
```bash
46
-
deb [arch=all signed-by=/usr/share/keyrings/strangebee-archive-keyring.gpg] https://deb.strangebee.com thehive-5.4 main
46
+
deb [arch=all signed-by=/usr/share/keyrings/strangebee-archive-keyring.gpg] https://deb.strangebee.com thehive-5.5 main
47
47
```
48
48
49
49
3. Install TheHive package:
@@ -68,7 +68,7 @@ TheHive 5.x deliverables are hosted in distinct package repositories. Depending
@@ -82,10 +82,10 @@ TheHive 5.x deliverables are hosted in distinct package repositories. Depending
82
82
83
83
=== "Docker"
84
84
85
-
Update your existing TheHive 5.x Docker stack (docker-compose file or similar) using the image named ``strangebee/thehive:5.4``
85
+
Update your existing TheHive 5.x Docker stack (docker-compose file or similar) using the image named ``strangebee/thehive:5.5``
86
86
87
87
!!! Note "Important note"
88
-
Ensure that you update your Docker tags accordingly. The strangebee/thehive:latest tag is deprecated and remains associated with TheHive 5.0.x versions. A new strangebee/thehive:5.4 tag is now available and associated with the latest 5.4.x version.
88
+
Ensure that you update your Docker tags accordingly. The strangebee/thehive:latest tag is deprecated and remains associated with TheHive 5.0.x versions. A new strangebee/thehive:5.5 tag is now available and associated with the latest 5.5.x version.
0 commit comments