Current Path: > > opt > cloudlinux > venv > lib > > python3.11 > site-packages > alembic > templates > multidb
Operation : Linux host59.registrar-servers.com 4.18.0-513.18.1.lve.2.el8.x86_64 #1 SMP Sat Mar 30 15:36:11 UTC 2024 x86_64 Software : Apache Server IP : 198.54.126.42 | Your IP: 216.73.216.135 Domains : 1034 Domain(s) Permission : [ 0755 ]
| Name | Type | Size | Last Modified | Actions |
|---|---|---|---|---|
| __pycache__ | Directory | - | - | |
| README | File | 606 bytes | April 17 2025 13:10:59. | |
| alembic.ini.mako | File | 3500 bytes | April 17 2025 13:10:59. | |
| env.py | File | 4230 bytes | April 17 2025 13:10:59. | |
| script.py.mako | File | 965 bytes | April 17 2025 13:10:59. |
Rudimentary multi-database configuration. Multi-DB isn't vastly different from generic. The primary difference is that it will run the migrations N times (depending on how many databases you have configured), providing one engine name and associated context for each run. That engine name will then allow the migration to restrict what runs within it to just the appropriate migrations for that engine. You can see this behavior within the mako template. In the provided configuration, you'll need to have `databases` provided in alembic's config, and an `sqlalchemy.url` provided for each engine name.
SILENT KILLER Tool