Merge pull request #530 from mkurz/fix_readme

mkurz · web-flow · commit 37ce9d01a295 · 2024-01-23T14:12:58.000+01:00
Oops! It's Pekko HTTP not Akka HTTP
diff --git a/play-java-chatroom-example/README.md b/play-java-chatroom-example/README.md
@@ -63,7 +63,7 @@ Go to <http://localhost:9000> and open it in two different browsers.  Typing int
 
 ## Server backend
 
-By default, the project uses the Akka HTTP Server backend. To switch to the Netty Server backend, enable the `PlayNettyServer` sbt plugin in the `build.sbt` file.
+By default, the project uses the Pekko HTTP Server backend. To switch to the Netty Server backend, enable the `PlayNettyServer` sbt plugin in the `build.sbt` file.
 In the `build.sbt` of this project, you'll find a commented line for this setting; simply uncomment it to make the switch.
 For more detailed information, refer to the Play Framework [documentation](https://www.playframework.com/documentation/3.0.x/Server).
 
diff --git a/play-java-compile-di-example/README.md b/play-java-compile-di-example/README.md
@@ -19,7 +19,7 @@ Then go to the server at <http://localhost:9000> to see "Hello".
 
 ## Server backend
 
-By default, the project uses the Akka HTTP Server backend. To switch to the Netty Server backend, enable the `PlayNettyServer` sbt plugin in the `build.sbt` file.
+By default, the project uses the Pekko HTTP Server backend. To switch to the Netty Server backend, enable the `PlayNettyServer` sbt plugin in the `build.sbt` file.
 In the `build.sbt` of this project, you'll find a commented line for this setting; simply uncomment it to make the switch.
 For more detailed information, refer to the Play Framework [documentation](https://www.playframework.com/documentation/3.0.x/Server).
 
diff --git a/play-java-dagger2-example/README.md b/play-java-dagger2-example/README.md
@@ -14,7 +14,7 @@ Go to http://localhost:9000/ws to see the WS client pull the time from a remote
 
 ## Server backend
 
-By default, the project uses the Akka HTTP Server backend. To switch to the Netty Server backend, enable the `PlayNettyServer` sbt plugin in the `build.sbt` file.
+By default, the project uses the Pekko HTTP Server backend. To switch to the Netty Server backend, enable the `PlayNettyServer` sbt plugin in the `build.sbt` file.
 In the `build.sbt` of this project, you'll find a commented line for this setting; simply uncomment it to make the switch.
 For more detailed information, refer to the Play Framework [documentation](https://www.playframework.com/documentation/3.0.x/Server).
 
diff --git a/play-java-ebean-example/README.md b/play-java-ebean-example/README.md
@@ -8,7 +8,7 @@ The GitHub location for this project is inside:
 
 ## Server backend
 
-By default, the project uses the Akka HTTP Server backend. To switch to the Netty Server backend, enable the `PlayNettyServer` sbt plugin in the `build.sbt` file.
+By default, the project uses the Pekko HTTP Server backend. To switch to the Netty Server backend, enable the `PlayNettyServer` sbt plugin in the `build.sbt` file.
 In the `build.sbt` of this project, you'll find a commented line for this setting; simply uncomment it to make the switch.
 For more detailed information, refer to the Play Framework [documentation](https://www.playframework.com/documentation/3.0.x/Server).
 
diff --git a/play-java-fileupload-example/README.md b/play-java-fileupload-example/README.md
@@ -95,6 +95,6 @@ abstract Function<Multipart.FileInfo, Accumulator<ByteString, Http.MultipartForm
 
 ## Server backend
 
-By default, the project uses the Akka HTTP Server backend. To switch to the Netty Server backend, enable the `PlayNettyServer` sbt plugin in the `build.sbt` file.
+By default, the project uses the Pekko HTTP Server backend. To switch to the Netty Server backend, enable the `PlayNettyServer` sbt plugin in the `build.sbt` file.
 In the `build.sbt` of this project, you'll find a commented line for this setting; simply uncomment it to make the switch.
 For more detailed information, refer to the Play Framework [documentation](https://www.playframework.com/documentation/3.0.x/Server).
diff --git a/play-java-forms-example/README.md b/play-java-forms-example/README.md
@@ -14,7 +14,7 @@ And open <http://localhost:9000/>
 
 ## Server backend
 
-By default, the project uses the Akka HTTP Server backend. To switch to the Netty Server backend, enable the `PlayNettyServer` sbt plugin in the `build.sbt` file.
+By default, the project uses the Pekko HTTP Server backend. To switch to the Netty Server backend, enable the `PlayNettyServer` sbt plugin in the `build.sbt` file.
 In the `build.sbt` of this project, you'll find a commented line for this setting; simply uncomment it to make the switch.
 For more detailed information, refer to the Play Framework [documentation](https://www.playframework.com/documentation/3.0.x/Server).
 
diff --git a/play-java-hello-world-tutorial/README.md b/play-java-hello-world-tutorial/README.md
@@ -38,6 +38,6 @@ The Play application responds: `Welcome to the Hello World Tutorial!`
 
 ## Server backend
 
-By default, the project uses the Akka HTTP Server backend. To switch to the Netty Server backend, enable the `PlayNettyServer` sbt plugin in the `build.sbt` file.
+By default, the project uses the Pekko HTTP Server backend. To switch to the Netty Server backend, enable the `PlayNettyServer` sbt plugin in the `build.sbt` file.
 In the `build.sbt` of this project, you'll find a commented line for this setting; simply uncomment it to make the switch.
 For more detailed information, refer to the Play Framework [documentation](https://www.playframework.com/documentation/3.0.x/Server).
diff --git a/play-java-jpa-example/README.md b/play-java-jpa-example/README.md
@@ -10,6 +10,6 @@ Please see the Play documentation for more details:
 
 ## Server backend
 
-By default, the project uses the Akka HTTP Server backend. To switch to the Netty Server backend, enable the `PlayNettyServer` sbt plugin in the `build.sbt` file.
+By default, the project uses the Pekko HTTP Server backend. To switch to the Netty Server backend, enable the `PlayNettyServer` sbt plugin in the `build.sbt` file.
 In the `build.sbt` of this project, you'll find a commented line for this setting; simply uncomment it to make the switch.
 For more detailed information, refer to the Play Framework [documentation](https://www.playframework.com/documentation/3.0.x/Server).
diff --git a/play-java-pekko-cluster-example/README.md b/play-java-pekko-cluster-example/README.md
@@ -34,7 +34,7 @@ but it doesn't demonstrate the [`Pekko Cluster Bootstrap`](https://pekko.apache.
 
 ## Server backend
 
-By default, the project uses the Akka HTTP Server backend. To switch to the Netty Server backend, enable the `PlayNettyServer` sbt plugin in the `build.sbt` file.
+By default, the project uses the Pekko HTTP Server backend. To switch to the Netty Server backend, enable the `PlayNettyServer` sbt plugin in the `build.sbt` file.
 In the `build.sbt` of this project, you'll find a commented line for this setting; simply uncomment it to make the switch.
 For more detailed information, refer to the Play Framework [documentation](https://www.playframework.com/documentation/3.0.x/Server).
 
diff --git a/play-java-rest-api-example/README.md b/play-java-rest-api-example/README.md
@@ -48,6 +48,6 @@ That will contain your load test results.
 
 ## Server backend
 
-By default, the project uses the Akka HTTP Server backend. To switch to the Netty Server backend, enable the `PlayNettyServer` sbt plugin in the `build.sbt` file.
+By default, the project uses the Pekko HTTP Server backend. To switch to the Netty Server backend, enable the `PlayNettyServer` sbt plugin in the `build.sbt` file.
 In the `build.sbt` of this project, you'll find a commented line for this setting; simply uncomment it to make the switch.
 For more detailed information, refer to the Play Framework [documentation](https://www.playframework.com/documentation/3.0.x/Server).
diff --git a/play-java-starter-example/README.md b/play-java-starter-example/README.md
@@ -52,6 +52,6 @@ There are several demonstration files available in this template.
 
 ## Server backend
 
-By default, the project uses the Akka HTTP Server backend. To switch to the Netty Server backend, enable the `PlayNettyServer` sbt plugin in the `build.sbt` file.
+By default, the project uses the Pekko HTTP Server backend. To switch to the Netty Server backend, enable the `PlayNettyServer` sbt plugin in the `build.sbt` file.
 In the `build.sbt` of this project, you'll find a commented line for this setting; simply uncomment it to make the switch.
 For more detailed information, refer to the Play Framework [documentation](https://www.playframework.com/documentation/3.0.x/Server).
diff --git a/play-java-streaming-example/README.md b/play-java-streaming-example/README.md
@@ -8,6 +8,6 @@ Please see the documentation at:
 
 ## Server backend
 
-By default, the project uses the Akka HTTP Server backend. To switch to the Netty Server backend, enable the `PlayNettyServer` sbt plugin in the `build.sbt` file.
+By default, the project uses the Pekko HTTP Server backend. To switch to the Netty Server backend, enable the `PlayNettyServer` sbt plugin in the `build.sbt` file.
 In the `build.sbt` of this project, you'll find a commented line for this setting; simply uncomment it to make the switch.
 For more detailed information, refer to the Play Framework [documentation](https://www.playframework.com/documentation/3.0.x/Server).
diff --git a/play-java-websocket-example/README.md b/play-java-websocket-example/README.md
@@ -8,7 +8,7 @@ There are also tests showing how Junit and Pekko Testkit are used to test actors
 
 ## Server backend
 
-By default, the project uses the Akka HTTP Server backend. To switch to the Netty Server backend, enable the `PlayNettyServer` sbt plugin in the `build.sbt` file.
+By default, the project uses the Pekko HTTP Server backend. To switch to the Netty Server backend, enable the `PlayNettyServer` sbt plugin in the `build.sbt` file.
 In the `build.sbt` of this project, you'll find a commented line for this setting; simply uncomment it to make the switch.
 For more detailed information, refer to the Play Framework [documentation](https://www.playframework.com/documentation/3.0.x/Server).
 
diff --git a/play-scala-anorm-example/README.md b/play-scala-anorm-example/README.md
@@ -4,7 +4,7 @@ This is an example Play application that uses Scala on the front end, and commun
 
 ## Server backend
 
-By default, the project uses the Akka HTTP Server backend. To switch to the Netty Server backend, enable the `PlayNettyServer` sbt plugin in the `build.sbt` file.
+By default, the project uses the Pekko HTTP Server backend. To switch to the Netty Server backend, enable the `PlayNettyServer` sbt plugin in the `build.sbt` file.
 In the `build.sbt` of this project, you'll find a commented line for this setting; simply uncomment it to make the switch.
 For more detailed information, refer to the Play Framework [documentation](https://www.playframework.com/documentation/3.0.x/Server).
 
diff --git a/play-scala-chatroom-example/README.md b/play-scala-chatroom-example/README.md
@@ -69,7 +69,7 @@ Go to <http://localhost:9000> and open it in two different browsers.  Typing int
 
 ## Server backend
 
-By default, the project uses the Akka HTTP Server backend. To switch to the Netty Server backend, enable the `PlayNettyServer` sbt plugin in the `build.sbt` file.
+By default, the project uses the Pekko HTTP Server backend. To switch to the Netty Server backend, enable the `PlayNettyServer` sbt plugin in the `build.sbt` file.
 In the `build.sbt` of this project, you'll find a commented line for this setting; simply uncomment it to make the switch.
 For more detailed information, refer to the Play Framework [documentation](https://www.playframework.com/documentation/3.0.x/Server).
 
diff --git a/play-scala-compile-di-example/README.md b/play-scala-compile-di-example/README.md
@@ -49,7 +49,7 @@ class ServerSpec extends PlaySpec
 
 ## Server backend
 
-By default, the project uses the Akka HTTP Server backend. To switch to the Netty Server backend, enable the `PlayNettyServer` sbt plugin in the `build.sbt` file.
+By default, the project uses the Pekko HTTP Server backend. To switch to the Netty Server backend, enable the `PlayNettyServer` sbt plugin in the `build.sbt` file.
 In the `build.sbt` of this project, you'll find a commented line for this setting; simply uncomment it to make the switch.
 For more detailed information, refer to the Play Framework [documentation](https://www.playframework.com/documentation/3.0.x/Server).
 
diff --git a/play-scala-fileupload-example/README.md b/play-scala-fileupload-example/README.md
@@ -6,7 +6,7 @@ Play's Scala API for `parse.multipartFormData` uses a `BodyParser[MultipartFormD
 
 ## Server backend
 
-By default, the project uses the Akka HTTP Server backend. To switch to the Netty Server backend, enable the `PlayNettyServer` sbt plugin in the `build.sbt` file.
+By default, the project uses the Pekko HTTP Server backend. To switch to the Netty Server backend, enable the `PlayNettyServer` sbt plugin in the `build.sbt` file.
 In the `build.sbt` of this project, you'll find a commented line for this setting; simply uncomment it to make the switch.
 For more detailed information, refer to the Play Framework [documentation](https://www.playframework.com/documentation/3.0.x/Server).
 
diff --git a/play-scala-forms-example/README.md b/play-scala-forms-example/README.md
@@ -14,7 +14,7 @@ And open [http://localhost:9000/](http://localhost:9000/)
 
 ## Server backend
 
-By default, the project uses the Akka HTTP Server backend. To switch to the Netty Server backend, enable the `PlayNettyServer` sbt plugin in the `build.sbt` file.
+By default, the project uses the Pekko HTTP Server backend. To switch to the Netty Server backend, enable the `PlayNettyServer` sbt plugin in the `build.sbt` file.
 In the `build.sbt` of this project, you'll find a commented line for this setting; simply uncomment it to make the switch.
 For more detailed information, refer to the Play Framework [documentation](https://www.playframework.com/documentation/3.0.x/Server).
 
diff --git a/play-scala-hello-world-tutorial/README.md b/play-scala-hello-world-tutorial/README.md
@@ -38,6 +38,6 @@ The Play application responds: `Welcome to the Hello World Tutorial!`
 
 ## Server backend
 
-By default, the project uses the Akka HTTP Server backend. To switch to the Netty Server backend, enable the `PlayNettyServer` sbt plugin in the `build.sbt` file.
+By default, the project uses the Pekko HTTP Server backend. To switch to the Netty Server backend, enable the `PlayNettyServer` sbt plugin in the `build.sbt` file.
 In the `build.sbt` of this project, you'll find a commented line for this setting; simply uncomment it to make the switch.
 For more detailed information, refer to the Play Framework [documentation](https://www.playframework.com/documentation/3.0.x/Server).
diff --git a/play-scala-isolated-slick-example/README.md b/play-scala-isolated-slick-example/README.md
@@ -44,6 +44,6 @@ Now go to <http://localhost:9000>, and you will see the list of users in the dat
 
 ## Server backend
 
-By default, the project uses the Akka HTTP Server backend. To switch to the Netty Server backend, enable the `PlayNettyServer` sbt plugin in the `build.sbt` file.
+By default, the project uses the Pekko HTTP Server backend. To switch to the Netty Server backend, enable the `PlayNettyServer` sbt plugin in the `build.sbt` file.
 In the `build.sbt` of this project, you'll find a commented line for this setting; simply uncomment it to make the switch.
 For more detailed information, refer to the Play Framework [documentation](https://www.playframework.com/documentation/3.0.x/Server).
diff --git a/play-scala-log4j2-example/README.md b/play-scala-log4j2-example/README.md
@@ -6,7 +6,7 @@ Please see [Using a custom logging framework](https://www.playframework.com/docu
 
 ## Server backend
 
-By default, the project uses the Akka HTTP Server backend. To switch to the Netty Server backend, enable the `PlayNettyServer` sbt plugin in the `build.sbt` file.
+By default, the project uses the Pekko HTTP Server backend. To switch to the Netty Server backend, enable the `PlayNettyServer` sbt plugin in the `build.sbt` file.
 In the `build.sbt` of this project, you'll find a commented line for this setting; simply uncomment it to make the switch.
 For more detailed information, refer to the Play Framework [documentation](https://www.playframework.com/documentation/3.0.x/Server).
 
diff --git a/play-scala-macwire-di-example/README.md b/play-scala-macwire-di-example/README.md
@@ -10,6 +10,6 @@ For further details, please see:
 
 ## Server backend
 
-By default, the project uses the Akka HTTP Server backend. To switch to the Netty Server backend, enable the `PlayNettyServer` sbt plugin in the `build.sbt` file.
+By default, the project uses the Pekko HTTP Server backend. To switch to the Netty Server backend, enable the `PlayNettyServer` sbt plugin in the `build.sbt` file.
 In the `build.sbt` of this project, you'll find a commented line for this setting; simply uncomment it to make the switch.
 For more detailed information, refer to the Play Framework [documentation](https://www.playframework.com/documentation/3.0.x/Server).
diff --git a/play-scala-rest-api-example/README.md b/play-scala-rest-api-example/README.md
@@ -18,7 +18,7 @@ Play will start up on the HTTP port at <http://localhost:9000/>.   You don't nee
 
 ## Server backend
 
-By default, the project uses the Akka HTTP Server backend. To switch to the Netty Server backend, enable the `PlayNettyServer` sbt plugin in the `build.sbt` file.
+By default, the project uses the Pekko HTTP Server backend. To switch to the Netty Server backend, enable the `PlayNettyServer` sbt plugin in the `build.sbt` file.
 In the `build.sbt` of this project, you'll find a commented line for this setting; simply uncomment it to make the switch.
 For more detailed information, refer to the Play Framework [documentation](https://www.playframework.com/documentation/3.0.x/Server).
 
diff --git a/play-scala-secure-session-example/README.md b/play-scala-secure-session-example/README.md
@@ -52,7 +52,7 @@ Then go to <http://localhost:9000> to see the server.
 
 ## Server backend
 
-By default, the project uses the Akka HTTP Server backend. To switch to the Netty Server backend, enable the `PlayNettyServer` sbt plugin in the `build.sbt` file.
+By default, the project uses the Pekko HTTP Server backend. To switch to the Netty Server backend, enable the `PlayNettyServer` sbt plugin in the `build.sbt` file.
 In the `build.sbt` of this project, you'll find a commented line for this setting; simply uncomment it to make the switch.
 For more detailed information, refer to the Play Framework [documentation](https://www.playframework.com/documentation/3.0.x/Server).
 
diff --git a/play-scala-slick-example/README.md b/play-scala-slick-example/README.md
@@ -23,7 +23,7 @@ To see an example of a Play application using Slick outside the play application
 
 ## Server backend
 
-By default, the project uses the Akka HTTP Server backend. To switch to the Netty Server backend, enable the `PlayNettyServer` sbt plugin in the `build.sbt` file.
+By default, the project uses the Pekko HTTP Server backend. To switch to the Netty Server backend, enable the `PlayNettyServer` sbt plugin in the `build.sbt` file.
 In the `build.sbt` of this project, you'll find a commented line for this setting; simply uncomment it to make the switch.
 For more detailed information, refer to the Play Framework [documentation](https://www.playframework.com/documentation/3.0.x/Server).
 
diff --git a/play-scala-starter-example/README.md b/play-scala-starter-example/README.md
@@ -16,7 +16,7 @@ There are several demonstration files available in this template.
 
 ## Server backend
 
-By default, the project uses the Akka HTTP Server backend. To switch to the Netty Server backend, enable the `PlayNettyServer` sbt plugin in the `build.sbt` file.
+By default, the project uses the Pekko HTTP Server backend. To switch to the Netty Server backend, enable the `PlayNettyServer` sbt plugin in the `build.sbt` file.
 In the `build.sbt` of this project, you'll find a commented line for this setting; simply uncomment it to make the switch.
 For more detailed information, refer to the Play Framework [documentation](https://www.playframework.com/documentation/3.0.x/Server).
 
diff --git a/play-scala-streaming-example/README.md b/play-scala-streaming-example/README.md
@@ -18,6 +18,6 @@ Once the application has been compiled and the server started, your application
 
 ## Server backend
 
-By default, the project uses the Akka HTTP Server backend. To switch to the Netty Server backend, enable the `PlayNettyServer` sbt plugin in the `build.sbt` file.
+By default, the project uses the Pekko HTTP Server backend. To switch to the Netty Server backend, enable the `PlayNettyServer` sbt plugin in the `build.sbt` file.
 In the `build.sbt` of this project, you'll find a commented line for this setting; simply uncomment it to make the switch.
 For more detailed information, refer to the Play Framework [documentation](https://www.playframework.com/documentation/3.0.x/Server).
diff --git a/play-scala-websocket-example/README.md b/play-scala-websocket-example/README.md
@@ -6,7 +6,7 @@ The Websocket API is built on Pekko Streams, and so is async, non-blocking, and
 
 ## Server backend
 
-By default, the project uses the Akka HTTP Server backend. To switch to the Netty Server backend, enable the `PlayNettyServer` sbt plugin in the `build.sbt` file.
+By default, the project uses the Pekko HTTP Server backend. To switch to the Netty Server backend, enable the `PlayNettyServer` sbt plugin in the `build.sbt` file.
 In the `build.sbt` of this project, you'll find a commented line for this setting; simply uncomment it to make the switch.
 For more detailed information, refer to the Play Framework [documentation](https://www.playframework.com/documentation/3.0.x/Server).
 
