| Mar | APR | May |
| 12 | ||
| 2022 | 2023 | 2024 |
COLLECTED BY
Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
History is littered with hundreds of conflicts over the future of a community, group, location or business that were "resolved" when one of the parties stepped ahead and destroyed what was there. With the original point of contention destroyed, the debates would fall to the wayside. Archive Team believes that by duplicated condemned data, the conversation and debate can continue, as well as the richness and insight gained by keeping the materials. Our projects have ranged in size from a single volunteer downloading the data to a small-but-critical site, to over 100 volunteers stepping forward to acquire terabytes of user-created data to save for future generations.
The main site for Archive Team is at archiveteam.org and contains up to the date information on various projects, manifestos, plans and walkthroughs.
This collection contains the output of many Archive Team projects, both ongoing and completed. Thanks to the generous providing of disk space by the Internet Archive, multi-terabyte datasets can be made available, as well as in use by the Wayback Machine, providing a path back to lost websites and work.
Our collection has grown to the point of having sub-collections for the type of data we acquire. If you are seeking to browse the contents of these collections, the Wayback Machine is the best first stop. Otherwise, you are free to dig into the stacks to see what you may find.
The Archive Team Panic Downloads are full pulldowns of currently extant websites, meant to serve as emergency backups for needed sites that are in danger of closing, or which will be missed dearly if suddenly lost due to hard drive crashes or server failures.
Collection: Archive Team: URLs
Dynaconf - 3.1.12
Flask
Initializing search
dynaconf/dynaconf
dynaconf/dynaconf
●
Home
●
Configuration
●
Env vars
●
Settings files
●
Secrets
●
Merging
●
Dynamic Variables
●
CLI
●
Validation
●
Flask
●
Initialize the extension
●
Use FLASK_ environment variables
●
Settings files
●
Loading Flask Extensions Dynamically
●
Development extensions
●
Troubleshooting
●
Django
●
Advanced usage
●
FAQ
●
Initialize the extension
●
Use FLASK_ environment variables
●
Settings files
●
Loading Flask Extensions Dynamically
●
Development extensions
●
Troubleshooting
app.config.
As Flask encourages the composition by overriding the config_class attribute this extension follows the patterns of Flask and turns your Flask's app.config in to a dynaconf instance.
app
from flask import Flask
from dynaconf import FlaskDynaconf
app = Flask(__name__)
FlaskDynaconf(app)
init_app as well.
FLASK_ environment variables¶
app.config will work as a dynaconf.settings instance and FLASK_ will be the global prefix for exporting environment variables.
Example:
export FLASK_DEBUG=true # app.config.DEBUG
export FLASK_INTVALUE=1 # app.config['INTVALUE']
export FLASK_MAIL_SERVER='host.com' # app.config.get('MAIL_SERVER')
from flask import Flask
from dynaconf import FlaskDynaconf
app = Flask(__name__)
FlaskDynaconf(app, envvar_prefix="PEANUT")
app.config.
export PEANUT_DEBUG=true # app.config.DEBUG
export PEANUT_INTVALUE=1 # app.config['INTVALUE']
export PEANUT_MAIL_SERVER='host.com' # app.config.get('MAIL_SERVER')
ENVVAR_PREFIX and would only accept uppsercase kwargs (different from Dynaconf(envvar_prefix)). Starting from version X.X.X, kwargs should be case insensitive to improve consistency between Dynaconf and Flask/Django extensions, while keeping backwards compatibility.
flask run) put your settings.toml and .secrets.toml files and then define your environments [default], [development] and [production].
To switch the working environment the FLASK_ENV variable can be used, so FLASK_ENV=development to work
in development mode or FLASK_ENV=production to switch to production.
IMPORTANT: To use $ dynaconf CLI the FLASK_APP must be defined.
IF you don't want to manually create your config files take a look at the CLI
callable that accepts app as first argument. e.g: flask_admin:Adminorcustom_extension.module:instance.init_app and of course the extension must be in Python namespace to be imported.
For extensions initialized just use an entry point object reference like: "flask_admin:Admin" or "extension.module:instance.init_app"
having a settings.toml
[default]
EXTENSIONS = [
"flask_admin:Admin",
"flask_bootstrap:Bootstrap",
"custom_extension.module:init_app"
]
app.py like:
from flask import Flask
from dynaconf import FlaskDynaconf
app = Flask(__name__)
flask_dynaconf = FlaskDynaconf(app, extensions_list="EXTENSIONS")
EXTENSIONS key on settings.
You can also load it lazily.
# at any point in your app startup
app.config.load_extensions()
load_extensions(key="OTHER_NAME") pointing to your list of extensions.
It is also possible to use environment variables to set the extensions to be loaded.
# .env
export FLASK_EXTENSIONS="['flask_admin:Admin']"
[default]
EXTENSIONS = [
"flask_admin:Admin",
"flask_bootstrap:Bootstrap",
"custom_extension.module:init_app"
]
[development]
EXTENSIONS = [
"dynaconf_merge",
"flask_debugtoolbar:DebugToolbar"
]
export FLASK_SKIP_DOTENV=1