The Complete Strapi™ Course with Plugins and Deployment - Admin Configuration

The video tutorial discusses the configuration of two key elements in the admin panel: the AUTH JWT token and the URL key. It explains the importance of setting these keys correctly for both development and production environments. The tutorial highlights the need to switch from a relative to an absolute URL when deploying the admin panel on a separate server. It also emphasizes the significance of the admin URL for user communication, such as password resets. Finally, it addresses the importance of consistent naming for JWT secrets in configuration files.

What is the purpose of the AUTH JWT token functionality in the admin configuration?

• To set the server URL

• To generate JWT tokens for the admin funnel

• To configure the database connection

• To manage user roles

Why is the URL key important in the admin configuration?

• It configures the user authentication method

• It specifies the server's IP address

• It sets the location where the admin panel is accessible

• It determines the database type

What happens when the URL key contains a relative path?

• It is ignored in production

• It gets appended to the server URL

• It causes an error

• It replaces the server URL

When should the admin URL be set to an absolute URL?

• When the admin panel is deployed to a separate server

• When using a local development environment

• When the admin panel is on the same server as the Strapi API

• When the server URL is unknown

What is the implication of setting an absolute URL for the admin panel?

• The admin panel is restricted to local access

• The admin URL becomes independent of the server URL

• The server URL is automatically updated

• The admin panel becomes inaccessible

Why is it important to ensure consistent naming of JWT secret environment variables?

• To avoid server crashes

• To ensure the admin panel functions correctly

• To maintain database integrity

• To prevent unauthorized access

What should you do if you notice different names for JWT secret variables in your code?

• Delete the variables

• Create a new variable

• Ignore the difference

• Ensure the names match