mirror of
https://github.com/jazzband/django-configurations.git
synced 2026-03-16 22:20:27 +00:00
Merge pull request #342 from timgates42/bugfix_typos
docs: Fix a few typos
This commit is contained in:
commit
17ca033d33
3 changed files with 3 additions and 3 deletions
|
|
@ -100,7 +100,7 @@ class Configuration(metaclass=ConfigurationBase):
|
|||
http://www.wellfireinteractive.com/blog/easier-12-factor-django/
|
||||
https://gist.github.com/bennylope/2999704
|
||||
"""
|
||||
# check if the class has DOTENV set wether with a path or None
|
||||
# check if the class has DOTENV set whether with a path or None
|
||||
dotenv = getattr(cls, 'DOTENV', None)
|
||||
|
||||
# if DOTENV is falsy we want to disable it
|
||||
|
|
|
|||
|
|
@ -112,7 +112,7 @@ class Value:
|
|||
"""
|
||||
Convert the given value of a environment variable into an
|
||||
appropriate Python representation of the value.
|
||||
This should be overriden when subclassing.
|
||||
This should be overridden when subclassing.
|
||||
"""
|
||||
return value
|
||||
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ Usage patterns
|
|||
|
||||
There are various configuration patterns that can be implemented with
|
||||
django-configurations. The most common pattern is to have a base class
|
||||
and various subclasses based on the enviroment they are supposed to be
|
||||
and various subclasses based on the environment they are supposed to be
|
||||
used in, e.g. in production, staging and development.
|
||||
|
||||
Server specific settings
|
||||
|
|
|
|||
Loading…
Reference in a new issue