mirror of
https://github.com/awatertrevi/infisical.git
synced 2026-10-07 05:27:48 +00:00
fix typos
This commit is contained in:
@@ -27,7 +27,7 @@ Now that we've created a project and added a secret to its development environme
|
|||||||
|
|
||||||
## Create a Python app
|
## Create a Python app
|
||||||
|
|
||||||
For this demonstration, we use a minimal Flask application. However, the same principles will apply for any Python application such as those built with Django.
|
For this demonstration, we use a minimal Flask application. However, the same principles will apply to any Python application such as those built with Django.
|
||||||
|
|
||||||
### Create a Flask app
|
### Create a Flask app
|
||||||
|
|
||||||
@@ -103,7 +103,7 @@ At this stage, you know how to fetch secrets from Infisical back to your Python
|
|||||||
Although the SDK requires you to pass in a token, it enables greater efficiency and security
|
Although the SDK requires you to pass in a token, it enables greater efficiency and security
|
||||||
than if you managed dozens of secrets yourself without it. Here're some benefits:
|
than if you managed dozens of secrets yourself without it. Here're some benefits:
|
||||||
|
|
||||||
- You always pull in the right secrets because they're fetched on demand from a centralize source that is Infisical.
|
- You always pull in the right secrets because they're fetched on demand from a centralized source that is Infisical.
|
||||||
- You can use the Infisical which comes with tons of benefits like secret versioning, access controls, audit logs, etc.
|
- You can use the Infisical which comes with tons of benefits like secret versioning, access controls, audit logs, etc.
|
||||||
- You now risk leaking one token that can be revoked instead of dozens of raw secrets.
|
- You now risk leaking one token that can be revoked instead of dozens of raw secrets.
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user