Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://quarkus.io/guides/dev-mode-differences below:

How dev mode differs from a production application

In keeping with the mantra of providing developer joy, Quarkus provides a host of features when dev mode is enabled. The most important features are:

This mightily important feature needs no introduction and has already been mentioned in the architectural differences section.

Quarkus provides a very useful UI accessible from the browser at /q/dev-ui. This UI allows a developer to see the state of the application, but also provides access to various actions that can change that state (depending on the extensions that are present). Examples of such operations are:

• Changing configuration values

• Running Database migration scripts

• Clearing of caches

• Running scheduled operations

• Building a container

In an effort to make development errors very easy to diagnose, Quarkus provides various detailed error pages when running in dev mode.

The quarkus-hibernate-orm extension will run the import.sql script in src/main/resources when Quarkus is running in dev mode. More details can be found here.

When testing or running in dev mode Quarkus can even provide you with a zero config database out of the box, a feature we refer to as Dev Services. More information can be found here.

The quarkus-smallrye-openapi extension will expose the Swagger UI when Quarkus is running in dev mode. Additional information can be found here.

The quarkus-smallrye-graphql extension will expose the GraphQL UI when Quarkus is running in dev mode. More details can be found here.

The quarkus-smallrye-health extension will expose the Health UI when Quarkus is running in dev mode. This section provides additional information.

The quarkus-mailer extension will enable an in-memory mock mail server when Quarkus is running in dev mode. See this for more details.

• The gRPC Reflection Service is enabled in dev mode by default. That lets you use tools such as grpcurl. In production mode, the reflection service is disabled. You can enable it explicitly using quarkus.grpc-server.enable-reflection-service=true.

• In dev mode, quarkus.grpc.server.instances has no effect.

There might be other configuration properties (depending on the extensions added to the application) that have no effect in dev mode.

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4