{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/60dbd81b3462415caaeb21f999769850\" frameborder=\"0\" width=\"816\" height=\"612\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":612,"width":816,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":612,"thumbnail_width":816,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/60dbd81b3462415caaeb21f999769850-00001.gif","duration":608.04,"title":"Meilisearch - Security","description":"For security\n1. Console access is not required.\n2. Only one port needs to be open, which is going to serve https\n3. The master API key will be used to create minimum-necessary permissioned client keys\n\t1. These can be set to expire\n4. There is multitenancy and tenant-tokens if we want to host private information. I recommend this just be used for content - products and related, not PII.\n5. Links to the repos in question, and a quick overview of how they're used\n\nhttps://docs.meilisearch.com/learn/what_is_meilisearch/telemetry.html \nhttps://docs.meilisearch.com/learn/security/master_api_keys.html \nhttps://docs.meilisearch.com/reference/api/keys.html#key-object \nhttps://docs.meilisearch.com/learn/cookbooks/running_production.html"}