sharpetronics/jekyll-algolia
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

storing app_id and index_name is not unsecure

Browse Source 
application_id and index_name are publicly available credentials
This commit is contained in:
Ashwin Maroli 2017-11-23 16:24:00 +05:30
parent b090d89312
commit 2ed054c40d
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@ -92,8 +92,6 @@ ALGOLIA_APPLICATION_ID | `your_application_id`
ALGOLIA_API_KEY | `your_api_key` ALGOLIA_API_KEY | `your_api_key`
ALGOLIA_INDEX_NAME | `your_index_name` ALGOLIA_INDEX_NAME | `your_index_name`
### ⚠ Other, unsecure, method ⚠
As a fallback measure, the plugin also checks if `application_id` and As a fallback measure, the plugin also checks if `application_id` and
`index_name` are available under `algolia` key in your `_config.yml` `index_name` are available under `algolia` key in your `_config.yml`
file like this: file like this:
@ -106,6 +104,8 @@ algolia:
index_name: 'your_index_name' index_name: 'your_index_name'
``` ```
### ⚠ Other, unsecure, method ⚠
You can also store your confidential API key in a file named `_algolia_api_key`, You can also store your confidential API key in a file named `_algolia_api_key`,
in your source directory. If you do this we __very, very, very strongly__ in your source directory. If you do this we __very, very, very strongly__
encourage you to make sure the file is not tracked in your versioning system. encourage you to make sure the file is not tracked in your versioning system.