FusionAuth · vcampitelli · Jan 31, 2024 · Dec 7, 2023 · Dec 7, 2023 · Dec 7, 2023
diff --git a/astro/src/content/docs/_shared/_elasticsearch-ram.mdx b/astro/src/content/docs/_shared/_elasticsearch-ram.mdx
@@ -1 +1 @@
-The RAM required by Elasticsearch depends on your login volume and user/entity counts. If you expect to have a few logins per minute and only a few thousand users/entities, `1GB-2GB` of RAM will be sufficient. If you have more users/entities as well as logins, please size up accordingly. We recommend running load tests of FusionAuth to help determine the amount of RAM that is required for your needs.
+The RAM required by Elasticsearch or OpenSearch depends on your login volume and user/entity counts. If you expect to have a few logins per minute and only a few thousand users/entities, `1GB-2GB` of RAM will be sufficient. If you have more users/entities as well as logins, please size up accordingly. We recommend running load tests of FusionAuth to help determine the amount of RAM that is required for your needs.
diff --git a/astro/src/content/docs/_shared/_elasticsearch-version.mdx b/astro/src/content/docs/_shared/_elasticsearch-version.mdx
@@ -1,3 +1,3 @@
-Versions `>=` 7.6.1 and `<=` 7.17.x are currently supported. Later versions may work as well but may not have been tested for compatibility.
+Elasticsearch Versions `>=` 7.6.1 and `<=` 7.17.x are currently supported. Later versions may work as well but may not have been tested for compatibility.
 
 OpenSearch version 2.x should also function properly with FusionAuth version `>= 1.42.0`.
diff --git a/astro/src/content/docs/_shared/_upgrade-using-docker.mdx b/astro/src/content/docs/_shared/_upgrade-using-docker.mdx
@@ -1,6 +1,6 @@
-To upgrade FusionAuth when running with `docker-compose`:
+To upgrade FusionAuth when running with `docker compose`:
 
-1. Stop the instance: `docker-compose down`.
+1. Stop the instance: `docker compose down`.
 2. Modify the `docker-compose.yml` file to point to the version of FusionAuth you want. You can see [available tags](https://hub.docker.com/r/fusionauth/fusionauth-app).
-3. Start it up: `docker-compose up`.
+3. Start it up: `docker compose up -d`.
 4. Log in to the administrative UI.
diff --git a/astro/src/content/docs/get-started/download-and-install/_docker-compose-files.mdx b/astro/src/content/docs/get-started/download-and-install/_docker-compose-files.mdx
@@ -16,7 +16,8 @@ Edit these files as needed. The stock `.env` file will contain the following val
             title="The .env file" />
 
 ```shell title="Starting FusionAuth"
-docker compose up
+docker compose up -d
+docker compose logs -f
 ```
 
 Now you can visit `http://localhost:9011` and configure FusionAuth.

diff --git a/astro/src/content/docs/get-started/download-and-install/docker.mdx b/astro/src/content/docs/get-started/download-and-install/docker.mdx
diff --git a/astro/src/content/docs/lifecycle/manage-users/search/switch-search-engines.mdx b/astro/src/content/docs/lifecycle/manage-users/search/switch-search-engines.mdx
@@ -10,7 +10,7 @@ import DataFieldDataTypeChanges from 'src/content/docs/_shared/_data-field-data-
 As of version 1.16.0, FusionAuth has the concept of a search engine type. There are two valid values:
 
 * `database`
-* `elasticsearch`
+* `elasticsearch` (for Elasticsearch or OpenSearch)
 
 They have different [strengths and limitations](/docs/get-started/core-concepts/users#user-search). This tutorial walks you through the process of changing your FusionAuth search engine. Reasons for doing so vary. You may be simplifying your deployment strategy with the database search engine. Or perhaps you need the advanced searching options of Elasticsearch after your application has grown. Either way, it's an easy switch.
 

diff --git a/astro/src/content/docs/lifecycle/manage-users/user-actions.mdx b/astro/src/content/docs/lifecycle/manage-users/user-actions.mdx
@@ -226,7 +226,7 @@ extra_hosts:
 * Run the following commands in a new terminal in the folder to restart FusionAuth with mail capabilities. **Be warned:** This might reset your existing FusionAuth database.
 
 ```
-docker-compose down && docker-compose up;
+docker compose down && docker compose up;
 ```
 </Aside>
 

diff --git a/astro/src/content/json/exampleapps.json b/astro/src/content/json/exampleapps.json
@@ -137,6 +137,12 @@
     "description": "Examples of Kickstart, a way to configure FusionAuth at startup",
     "language": "config"
   },
+  {
+    "url": "https://github.com/FusionAuth/fusionauth-example-docker-compose",
+    "name": "Docker Compose",
+    "description": "Docker Compose examples, different ways to configure and run FusionAuth",
+    "language": "config"
+  },
   {
     "url": "https://github.com/FusionAuth/fusionauth-theme-helper",
     "name": "Theme Helper",

diff --git a/astro/src/content/quickstarts/quickstart-dotnet-api.mdx b/astro/src/content/quickstarts/quickstart-dotnet-api.mdx
@@ -60,7 +60,7 @@ This will start three containers, one each for FusionAuth, Postgres, and Elastic
 Here you are using a bootstrapping feature of FusionAuth, called [Kickstart](/docs/get-started/download-and-install/development/kickstart). When FusionAuth starts for the first time, it will look at the `kickstart/kickstart.json` file and configure FusionAuth to your specified state.
 
 <Aside type="note">
-If you ever want to reset the FusionAuth system, delete the volumes created by docker-compose by executing `docker compose down -v`, then re-run `docker compose up -d`.
+If you ever want to reset the FusionAuth system, delete the volumes created by Docker Compose by executing `docker compose down -v`, then re-run `docker compose up -d`.
 </Aside>
 
 FusionAuth will be initially configured with these settings:

diff --git a/astro/src/content/quickstarts/quickstart-dotnet-web.mdx b/astro/src/content/quickstarts/quickstart-dotnet-web.mdx
@@ -67,7 +67,7 @@ docker compose up -d
 Here you are using a bootstrapping feature of FusionAuth, called [Kickstart](/docs/get-started/download-and-install/development/kickstart) When FusionAuth comes up for the first time, it will look at the `kickstart/kickstart.json` file and configure FusionAuth to a certain initial state.
 
 <Aside type="note">
-If you ever want to reset the FusionAuth system, delete the volumes created by docker-compose by executing `docker compose down -v`, then re-run `docker compose up -d`.
+If you ever want to reset the FusionAuth system, delete the volumes created by Docker Compose by executing `docker compose down -v`, then re-run `docker compose up -d`.
 </Aside>
 
 FusionAuth will be initially configured with these settings:

diff --git a/astro/src/content/quickstarts/quickstart-golang-api.mdx b/astro/src/content/quickstarts/quickstart-golang-api.mdx
@@ -58,7 +58,7 @@ docker compose up -d
 Here you are using a bootstrapping feature of FusionAuth, called [Kickstart](/docs/get-started/download-and-install/development/kickstart). When FusionAuth comes up for the first time, it will look at the `kickstart/kickstart.json` file and configure FusionAuth to a certain initial state.
 
 <Aside type="note">
-If you ever want to reset the FusionAuth system, delete the volumes created by docker-compose by executing `docker-compose down -v`, then re-run `docker-compose up -d`.
+If you ever want to reset the FusionAuth system, delete the volumes created by Docker Compose by executing `docker compose down -v`, then re-run `docker compose up -d`.
 </Aside>
 
 FusionAuth will be initially configured with these settings:

diff --git a/astro/src/content/quickstarts/quickstart-golang-web.mdx b/astro/src/content/quickstarts/quickstart-golang-web.mdx
@@ -61,7 +61,7 @@ variables configuration file (.env). Assuming you have Docker installed on your
 FusionAuth up on your machine with:
 
 ```
-docker-compose up -d
+docker compose up -d
 ```
 
 This will start three containers, once each for FusionAuth, Postgres, and Elastic.
@@ -71,8 +71,8 @@ When FusionAuth comes up for the first time, it will look at the `kickstart/kick
 configure FusionAuth to a certain initial state.
 
 <Aside type="note">
-If you ever want to reset the FusionAuth system, delete the volumes created by docker-compose by
-executing `docker-compose down -v`, then re-run `docker-compose up -d`.
+If you ever want to reset the FusionAuth system, delete the volumes created by Docker Compose by
+executing `docker compose down -v`, then re-run `docker compose up -d`.
 </Aside>
 
 FusionAuth will be configured with these settings

diff --git a/astro/src/content/quickstarts/quickstart-java-springboot-api.mdx b/astro/src/content/quickstarts/quickstart-java-springboot-api.mdx
@@ -56,7 +56,7 @@ docker compose up -d
 Here you are using a bootstrapping feature of FusionAuth, called [Kickstart](/docs/get-started/download-and-install/development/kickstart). When FusionAuth comes up for the first time, it will look at the `kickstart/kickstart.json` file and configure FusionAuth to a certain initial state.
 
 <Aside type="note">
-If you ever want to reset the FusionAuth system, delete the volumes created by docker-compose by executing `docker-compose down -v`, then re-run `docker-compose up -d`.
+If you ever want to reset the FusionAuth system, delete the volumes created by Docker Compose by executing `docker compose down -v`, then re-run `docker compose up -d`.
 </Aside>
 
 FusionAuth will be initially configured with these settings:
@@ -429,7 +429,7 @@ You can always pull down a complete running application and compare what's diffe
 ```
 git clone https://github.com/FusionAuth/fusionauth-quickstart-java-springboot-api.git
 cd fusionauth-quickstart-java-springboot-api
-docker-compose up -d
+docker compose up -d
 cd complete-app
 ./mvnw package spring-boot:run
 ```

diff --git a/astro/src/content/quickstarts/quickstart-javascript-angular-web.mdx b/astro/src/content/quickstarts/quickstart-javascript-angular-web.mdx
@@ -73,7 +73,7 @@ When FusionAuth comes up for the first time, it will look at the `kickstart/kick
 configure FusionAuth to a certain initial state.
 
 <Aside type="note">
-    If you ever want to reset the FusionAuth system, delete the volumes created by docker-compose by
+    If you ever want to reset the FusionAuth system, delete the volumes created by Docker Compose by
     executing `docker compose down -v`, then re-run `docker compose up -d`.
 </Aside>
 

diff --git a/astro/src/content/quickstarts/quickstart-javascript-react-web.mdx b/astro/src/content/quickstarts/quickstart-javascript-react-web.mdx
@@ -73,7 +73,7 @@ When FusionAuth comes up for the first time, it will look at the `kickstart/kick
 configure FusionAuth to a certain initial state.
 
 <Aside type="note">
-    If you ever want to reset the FusionAuth system, delete the volumes created by docker-compose by
+    If you ever want to reset the FusionAuth system, delete the volumes created by Docker Compose by
     executing `docker compose down -v`, then re-run `docker compose up -d`.
 </Aside>
 

diff --git a/astro/src/content/quickstarts/quickstart-javascript-vue-web.mdx b/astro/src/content/quickstarts/quickstart-javascript-vue-web.mdx
@@ -73,7 +73,7 @@ When FusionAuth comes up for the first time, it will look at the `kickstart/kick
 configure FusionAuth to a certain initial state.
 
 <Aside type="note">
-    If you ever want to reset the FusionAuth system, delete the volumes created by docker-compose by
+    If you ever want to reset the FusionAuth system, delete the volumes created by Docker Compose by
     executing `docker compose down -v`, then re-run `docker compose up -d`.
 </Aside>
 

diff --git a/astro/src/content/quickstarts/quickstart-php-drupal-web.mdx b/astro/src/content/quickstarts/quickstart-php-drupal-web.mdx
@@ -188,7 +188,7 @@ docker compose up -d
 Here you are using a bootstrapping feature of FusionAuth, called [Kickstart](/docs/v1/tech/installation-guide/kickstart). When FusionAuth comes up for the first time, it will look at the `kickstart/kickstart.json` file and configure FusionAuth to a certain initial state.
 
 <Aside type="note">
- If you ever want to reset the FusionAuth system, delete the volumes created by docker-compose by executing `docker compose down -v`, then re-run `docker compose up -d`.
+ If you ever want to reset the FusionAuth system, delete the volumes created by Docker Compose by executing `docker compose down -v`, then re-run `docker compose up -d`.
 </Aside>
 
 FusionAuth will be initially configured with these settings:

diff --git a/astro/src/content/quickstarts/quickstart-python-django-web.mdx b/astro/src/content/quickstarts/quickstart-python-django-web.mdx
@@ -65,15 +65,15 @@ You'll find a Docker Compose file `docker-compose.yml` and an environment variab
 Assuming you have Docker installed, you can start FusionAuth on your machine with the following.
 
 ```
-docker-compose up -d
+docker compose up -d
 ```
 
 This will start three containers, one each for FusionAuth, Postgres, and Elasticsearch.
 
 Here you are using a bootstrapping feature of FusionAuth, called [Kickstart](/docs/get-started/download-and-install/development/kickstart). When FusionAuth starts for the first time, it will look at the `kickstart/kickstart.json` file and configure FusionAuth to your specified state.
 
 <Aside type="note">
-If you ever want to reset the FusionAuth system, delete the volumes created by `docker-compose` by executing `docker-compose down -v`, then rerun `docker-compose up -d`.
+If you ever want to reset the FusionAuth system, delete the volumes created by `docker-compose` by executing `docker compose down -v`, then rerun `docker compose up -d`.
 </Aside>
 
 FusionAuth will be configured with these settings:

diff --git a/astro/src/content/quickstarts/quickstart-ruby-on-rails-api.mdx b/astro/src/content/quickstarts/quickstart-ruby-on-rails-api.mdx
@@ -60,7 +60,7 @@ docker compose up -d
 Here you are using a bootstrapping feature of FusionAuth, called [Kickstart](/docs/get-started/download-and-install/development/kickstart). When FusionAuth comes up for the first time, it will look at the `kickstart/kickstart.json` file and configure FusionAuth to a certain initial state.
 
 <Aside type="note">
-If you ever want to reset the FusionAuth system, delete the volumes created by docker-compose by executing `docker-compose down -v`, then re-run `docker-compose up -d`.
+If you ever want to reset the FusionAuth system, delete the volumes created by Docker Compose by executing `docker compose down -v`, then re-run `docker compose up -d`.
 </Aside>
 
 FusionAuth will be initially configured with these settings:
@@ -397,7 +397,7 @@ You can always pull down a complete running application and compare what's diffe
 ```
 git clone https://github.com/FusionAuth/fusionauth-quickstart-ruby-on-rails-api.git
 cd fusionauth-quickstart-ruby-on-rails-api
-docker-compose up -d
+docker compose up -d
 cd complete-application
 bundle install
 bundle e rails s -p 4001

diff --git a/astro/src/content/quickstarts/quickstart-ruby-rails-web.mdx b/astro/src/content/quickstarts/quickstart-ruby-rails-web.mdx
@@ -70,7 +70,7 @@ docker compose up -d
 Here you are using a bootstrapping feature of FusionAuth, called [Kickstart](/docs/get-started/download-and-install/development/kickstart). When FusionAuth comes up for the first time, it will look at the `kickstart/kickstart.json` file and configure FusionAuth to a certain initial state.
 
 <Aside type="note">
-If you ever want to reset the FusionAuth system, delete the volumes created by docker-compose by executing `docker compose down -v`, then re-run `docker compose up -d`.
+If you ever want to reset the FusionAuth system, delete the volumes created by Docker Compose by executing `docker compose down -v`, then re-run `docker compose up -d`.
 </Aside>
 
 FusionAuth will be initially configured with these settings:
@@ -280,7 +280,7 @@ You can always pull down a complete running application and compare what's diffe
   {(value) => (
     <Code lang="shell" code={`git clone https://github.com/FusionAuth/fusionauth-quickstart-ruby-on-rails-web.git
 cd fusionauth-quickstart-ruby-on-rails-web
-docker-compose up -d
+docker compose up -d
 cd complete-app
 bundle install
 OP_SECRET_KEY=${value} bundle exec rails s`}/>