mirror of
https://github.com/strapi/strapi.git
synced 2025-10-30 01:17:28 +00:00
Merge pull request #6489 from strapi/docs/faqUpdateStable
FAQ section of docs update to add notes applied in stable and fix regression
This commit is contained in:
commit
f10cd77aee
@ -37,7 +37,7 @@ At this time and in the future there is no plan to allow model creating or updat
|
||||
|
||||
### Does Strapi handle deploying or migrating of content?
|
||||
|
||||
Strapi does not currently provide any tools for migrating or deploying your data changes between different environments (_ie. from development to production_).
|
||||
Strapi does not currently provide any tools for migrating or deploying your data changes between different environments (_ie. from development to production_). With the exception being the Content-Manager settings, to read more about this option please see the following [CLI documentation](../cli/CLI.md#strapi-configuration-dump-config-dump).
|
||||
|
||||
### User can't login to the admin panel
|
||||
|
||||
@ -64,6 +64,18 @@ If you used `--quickstart` to create your Strapi project, by default this uses t
|
||||
|
||||
It is recommended you use the Heroku PostgreSQL plugin or use something like MongoDB's Atlas for your database. For file uploads, you will need to use one of the 3rd party providers such as Cloudinary or AWS S3.
|
||||
|
||||
### Can I store my Content Manager layout configurations in the model settings
|
||||
|
||||
Currently Strapi does not support this, a `config:dump` and `config:restore` command has been added to make migration of these settings easier when moving between different deployments and environments.
|
||||
|
||||
We don't offer the ability to store these configurations in the model settings for several reasons:
|
||||
|
||||
- It will create conflicts in case of content internationalization and translations in the admin interface.
|
||||
- The layout might be different according to the roles and permissions.
|
||||
- While the model is the same whatever the content created, the contribution interface can be different. For instance, we have an idea to create a mobile application for contributors only. The labels and layout configurations could be different according the device & interface.
|
||||
|
||||
For all these reasons, and others, we think it'll be a mistake and might confuse users if we store the configuration in the model settings file. The final solution is to make the migration and deployment across environment easier.
|
||||
|
||||
### How do I customize a plugin
|
||||
|
||||
Strapi uses a system called [extensions](../concepts/customization.md#plugin-extensions) as plugins are stored in the `node_modules` folder. Due to this extensions work by Strapi detecting newer versions of files and using that as a replacement for the ones stored within the `node_modules`. If you are familiar with React and "ejecting" a file, the concept is similar.
|
||||
@ -76,6 +88,10 @@ Yes you can either follow the following [guide](../plugins/users-permissions.md#
|
||||
|
||||
There is currently no ETA on this migration however.
|
||||
|
||||
### Does Strapi allow me to change the default ID type or name
|
||||
|
||||
No, currently does not have the ability to allow for changing the default id name nor does it allow you to switch the data type (such as UUID on bookshelf and integer on mongoose), support for this is being looked at for Strapi v4.
|
||||
|
||||
### How do I setup SSL with Strapi
|
||||
|
||||
Strapi implements no SSL solution natively, this is due to the fact that it is extremely insecure to directly offer a Node.js application to the public web on a low port.
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user