Your server configuration can move from `./config/environments/{env}/server.json` to `./config/server.js` like shown [here](../concepts/configurations.md#server).
Your database configuration can move from `./config/environments/{env}/database.json` to `./config/database.js` like shown [here](../concepts/configurations.md#database).
"Define the middlewares' load order by putting their name in this array is the right order",
],
after: ['parser', 'router'],
},
settings: {
public: {
path: './public',
maxAge: 60000,
},
},
};
```
You can now move the middleware configurations from `application.json`, `language.json`, `security.json`, `request.json` and `response.json` files directly into the `settings` property.
You can review all possible options the [middleware documentation](../concepts/middlewares.md#configuration-and-activation).
::: tip
If you never configured any middlewares you can delete the file all together. You can also only set the configurations you want to customize and leave the others out.
We applied the same logic from the `middleware` configuration to the `hook` configuration.
First you can create a file `./config/hook.js`, and you can move the content of `./config/.hook.json` into it.
::: tip
If you never configured any hook you can delete the file all together. You can also only set the configurations you want to customize and leave the others out.
Once you have setup your configuration, you can cleanup your database by deleting in the `core_store` model the data with the `key` equal to `plugin_email_provider`.
If you are using the graphql `register` mutation, the input and response types have changed. You can check the code [here](https://github.com/strapi/strapi/pull/6047).
The `changePassword` mutation got renamed to `resetPassword` to reflect what it does. You can check the code [here](https://github.com/strapi/strapi/pull/5655).
Currently using the idAttribute and idAttributeType options can break strapi in many ways. Fixing this is going to require a lot of work on the database and content management layer.
In an effort to make strapi more stable we have decided to remove those broken options for the time being. For users who want unique uuid fields for examples we recommend you create a uuid attribute and use the lifecycles function to populate it.
## Proxy configuration
In order to support hosting strapi with more flexibility, we have changed the way to configure the server proxy options and the admin panel path.
### Proxy
We replaced the `proxy` option found in `./config/server.json` by the `url` option.
This option also makes the `admin.build.backend` option obsolete.
What you can now do is add a path to the url to host strapi in a sub path of your domain.
```js
module.exports = {
//...
url: `https://domain.com:1337/my-strapi-api`,
};
```
::: warning
Adding a sub path to the url doesn't mean your api is going to be prefixed. You will need to host your app behind a proxy and remove the prefix so strapi receives request like if they where made on the root `/` path.
