Skip to content
BranchesTags

Repository files navigation

DbProvisioner

DbProvisioner is a lightweight .NET code-first utility designed to run as an ephemeral container within your Docker Compose stack. Its primary goal is to automatically configure database users, passwords, and schemas every time you deploy or restart your stack. It's meant to be used on those scenarios that you make use of a single database for multiple services.

It ensures your database access controls are always in sync with your environment configuration, handling the creation of new users and the cleanup of obsolete ones.

DbProvisioner is currently considered feature complete. It fulfills its primary purpose of synchronizing database users and schemas via environment variables within a containerized environment. But we are open for PRs with added features, please check the CONTRIBUTION.md for more details.

🚀 How it Works

When the container starts, it performs the following logic:

  1. Connects to the target database server (MySQL/MariaDB) using administrative credentials.

  2. Scans Environment Variables to identify desired users and databases (based on variables matching the pattern DB_{NAME}_USERNAME).

  3. Syncs State:

    • Creates users/databases that do not exist.
    • Updates passwords for existing users (ensuring credentials are up to date).
    • GrantsALL PRIVILEGES to the user for their specific database.
    • Removes users found in the database but not in the environment variables (excluding system users like root).

🐳 Docker Compose Integration

This is the recommended way to use DbProvisioner. Add it to your docker-compose.yml alongside your database container.

Note: The provisioner needs to wait for the database to be healthy before running.

services:
# Your Database Servicedb:
image: mariadb:10.6 # or mysql:8environment:
MYSQL_ROOT_PASSWORD: root_secret_passwordhealthcheck:
test: ["CMD", "healthcheck.sh", "--connect", "--innodb_initialized"]interval: 10stimeout: 5sretries: 5# The Provisioner Servicedb-provisioner:
image: ghcr.io/icavalheiro/dbprovisioner:latestdepends_on:
db:
condition: service_healthyenvironment:
DB_HOST: dbDB_USER: rootDB_PASSWORD: root_secret_password# --- Users to Provision ---# Pattern: DB_{NAME}_USERNAME & DB_{NAME}_PASSWORD# Creates database "APP_ONE" and user "app_user"DB_APP_ONE_USERNAME: app_userDB_APP_ONE_PASSWORD: secure_pass_123# Creates database "ANALYTICS" and user "data_svc"DB_ANALYTICS_USERNAME: data_svcDB_ANALYTICS_PASSWORD: another_secure_pass

⚙️ Configuration

The application is configured entirely via Environment Variables.

Connection Settings

These variables tell the provisioner how to connect to the server to perform administrative tasks.

VariableDescriptionDefault
DB_HOSTThe hostname of the database server (e.g., db or localhost).Required
DB_USERAdmin username (usually root).Required
DB_PASSWORDAdmin password.Required
DB_NAMEThe initial database to connect to.mysql

User & Database Definition

The provisioner dynamically parses environment variables to find users to create. It looks for keys starting with DB_ and ending with _USERNAME.

Format:

  • Username:DB_{DB_NAME}_USERNAME
  • Password:DB_{DB_NAME}_PASSWORD

Example: Setting DB_MYSHOP_USERNAME=shop_admin will:

  1. Create a database named MYSHOP.
  2. Create a user named shop_admin.
  3. Grant shop_admin full access to MYSHOP.

🛡️ Safety & Cleanup

  • System Users: The provisioner contains a whitelist of system users (e.g., root, mysql.sys, healthcheck) that it will never delete, even if they are not in your environment variables.
  • Stale Users: Any non-system user found in the database that is not defined in your current environment variables will be dropped. This ensures your database doesn't accumulate "zombie" accounts from old configurations.

🛠️ Built With

  • .NET 10
  • MySqlConnector
  • Docker (Alpine Linux)

About

DbProvisioner is a lightweight .NET code-first utility that automatically configure database users, passwords, and schemas every time you deploy or restart your stack

Resources

Readme
GPL-2.0 license
Activity

Stars

1 star

Watchers

0 watching

Forks

0 forks
Report repository

Releases

Packages

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { // Add copy buttons to all 
 blocks
(function() {
function addCopyButtons() {
document.querySelectorAll('pre code').forEach(function(codeBlock) {
if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;
codeBlock.parentElement.setAttribute('data-copy-added', 'true');
var btn = document.createElement('button');
btn.textContent = 'Copy';
btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';
btn.onmouseover = function() { this.style.opacity = '1'; };
btn.onmouseout = function() { this.style.opacity = '0.7'; };
btn.onclick = function() {
navigator.clipboard.writeText(codeBlock.textContent).then(function() {
btn.textContent = 'Copied!';
setTimeout(function() { btn.textContent = 'Copy'; }, 1500);
});
};
codeBlock.parentElement.style.position = 'relative';
codeBlock.parentElement.appendChild(btn);
});
}
addCopyButtons();
// Re-run on dynamic content
var observer = new MutationObserver(addCopyButtons);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '
GitHub - icavalheiro/DbProvisioner: DbProvisioner is a lightweight .NET code-first utility that automatically configure database users, passwords, and schemas every time you deploy or restart your stack · GitHub
Skip to content
BranchesTags
Repository files navigation
DbProvisioner
DbProvisioner is a lightweight .NET code-first utility designed to run as an ephemeral container within your Docker Compose stack. Its primary goal is to automatically configure database users, passwords, and schemas every time you deploy or restart your stack. It's meant to be used on those scenarios that you make use of a single database for multiple services.
It ensures your database access controls are always in sync with your environment configuration, handling the creation of new users and the cleanup of obsolete ones.
DbProvisioner is currently considered feature complete. It fulfills its primary purpose of synchronizing database users and schemas via environment variables within a containerized environment. But we are open for PRs with added features, please check the CONTRIBUTION.md for more details.
🚀 How it Works
When the container starts, it performs the following logic:
  1. Connects to the target database server (MySQL/MariaDB) using administrative credentials.
  2. Scans Environment Variables to identify desired users and databases (based on variables matching the pattern DB_{NAME}_USERNAME).
  3. Syncs State:
    • Creates users/databases that do not exist.
    • Updates passwords for existing users (ensuring credentials are up to date).
    • GrantsALL PRIVILEGES to the user for their specific database.
    • Removes users found in the database but not in the environment variables (excluding system users like root).
🐳 Docker Compose Integration
This is the recommended way to use DbProvisioner. Add it to your docker-compose.yml alongside your database container.
Note: The provisioner needs to wait for the database to be healthy before running.
services:
# Your Database Servicedb:
image: mariadb:10.6 # or mysql:8environment:
MYSQL_ROOT_PASSWORD: root_secret_passwordhealthcheck:
test: ["CMD", "healthcheck.sh", "--connect", "--innodb_initialized"]interval: 10stimeout: 5sretries: 5# The Provisioner Servicedb-provisioner:
image: ghcr.io/icavalheiro/dbprovisioner:latestdepends_on:
db:
condition: service_healthyenvironment:
DB_HOST: dbDB_USER: rootDB_PASSWORD: root_secret_password# --- Users to Provision ---# Pattern: DB_{NAME}_USERNAME & DB_{NAME}_PASSWORD# Creates database "APP_ONE" and user "app_user"DB_APP_ONE_USERNAME: app_userDB_APP_ONE_PASSWORD: secure_pass_123# Creates database "ANALYTICS" and user "data_svc"DB_ANALYTICS_USERNAME: data_svcDB_ANALYTICS_PASSWORD: another_secure_pass
⚙️ Configuration
The application is configured entirely via Environment Variables.
Connection Settings
These variables tell the provisioner how to connect to the server to perform administrative tasks.
VariableDescriptionDefault
DB_HOSTThe hostname of the database server (e.g., db or localhost).Required
DB_USERAdmin username (usually root).Required
DB_PASSWORDAdmin password.Required
DB_NAMEThe initial database to connect to.mysql
User & Database Definition
The provisioner dynamically parses environment variables to find users to create. It looks for keys starting with DB_ and ending with _USERNAME.
Format:
  • Username:DB_{DB_NAME}_USERNAME
  • Password:DB_{DB_NAME}_PASSWORD
Example: Setting DB_MYSHOP_USERNAME=shop_admin will:
  1. Create a database named MYSHOP.
  2. Create a user named shop_admin.
  3. Grant shop_admin full access to MYSHOP.
🛡️ Safety & Cleanup
  • System Users: The provisioner contains a whitelist of system users (e.g., root, mysql.sys, healthcheck) that it will never delete, even if they are not in your environment variables.
  • Stale Users: Any non-system user found in the database that is not defined in your current environment variables will be dropped. This ensures your database doesn't accumulate "zombie" accounts from old configurations.
🛠️ Built With
  • .NET 10
  • MySqlConnector
  • Docker (Alpine Linux)
About
DbProvisioner is a lightweight .NET code-first utility that automatically configure database users, passwords, and schemas every time you deploy or restart your stack
Resources
Readme
GPL-2.0 license
Activity
Stars
1 star
Watchers
0 watching
Forks
0 forks
Report repository
Releases
Packages
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Force GitHub README to respect dark mode
(function() {
var style = document.createElement('style');
style.textContent = '
.markdown-body {
color-scheme: dark light;
}
.markdown-body pre { background: #161b22 !important; }
.markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }
.markdown-body table th, .markdown-body table td { border-color: #30363d !important; }
.markdown-body img { background: #0d1117; }
.markdown-body blockquote { border-left-color: #8b949e; }
.markdown-body hr { border-color: #30363d; }
';
document.head.appendChild(style);
})();
}
} catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
GitHub - icavalheiro/DbProvisioner: DbProvisioner is a lightweight .NET code-first utility that automatically configure database users, passwords, and schemas every time you deploy or restart your stack · GitHub
Skip to content
BranchesTags
Repository files navigation
DbProvisioner
DbProvisioner is a lightweight .NET code-first utility designed to run as an ephemeral container within your Docker Compose stack. Its primary goal is to automatically configure database users, passwords, and schemas every time you deploy or restart your stack. It's meant to be used on those scenarios that you make use of a single database for multiple services.
It ensures your database access controls are always in sync with your environment configuration, handling the creation of new users and the cleanup of obsolete ones.
DbProvisioner is currently considered feature complete. It fulfills its primary purpose of synchronizing database users and schemas via environment variables within a containerized environment. But we are open for PRs with added features, please check the CONTRIBUTION.md for more details.
🚀 How it Works
When the container starts, it performs the following logic:
  1. Connects to the target database server (MySQL/MariaDB) using administrative credentials.
  2. Scans Environment Variables to identify desired users and databases (based on variables matching the pattern DB_{NAME}_USERNAME).
  3. Syncs State:
    • Creates users/databases that do not exist.
    • Updates passwords for existing users (ensuring credentials are up to date).
    • GrantsALL PRIVILEGES to the user for their specific database.
    • Removes users found in the database but not in the environment variables (excluding system users like root).
🐳 Docker Compose Integration
This is the recommended way to use DbProvisioner. Add it to your docker-compose.yml alongside your database container.
Note: The provisioner needs to wait for the database to be healthy before running.
services:
# Your Database Servicedb:
image: mariadb:10.6 # or mysql:8environment:
MYSQL_ROOT_PASSWORD: root_secret_passwordhealthcheck:
test: ["CMD", "healthcheck.sh", "--connect", "--innodb_initialized"]interval: 10stimeout: 5sretries: 5# The Provisioner Servicedb-provisioner:
image: ghcr.io/icavalheiro/dbprovisioner:latestdepends_on:
db:
condition: service_healthyenvironment:
DB_HOST: dbDB_USER: rootDB_PASSWORD: root_secret_password# --- Users to Provision ---# Pattern: DB_{NAME}_USERNAME & DB_{NAME}_PASSWORD# Creates database "APP_ONE" and user "app_user"DB_APP_ONE_USERNAME: app_userDB_APP_ONE_PASSWORD: secure_pass_123# Creates database "ANALYTICS" and user "data_svc"DB_ANALYTICS_USERNAME: data_svcDB_ANALYTICS_PASSWORD: another_secure_pass
⚙️ Configuration
The application is configured entirely via Environment Variables.
Connection Settings
These variables tell the provisioner how to connect to the server to perform administrative tasks.
VariableDescriptionDefault
DB_HOSTThe hostname of the database server (e.g., db or localhost).Required
DB_USERAdmin username (usually root).Required
DB_PASSWORDAdmin password.Required
DB_NAMEThe initial database to connect to.mysql
User & Database Definition
The provisioner dynamically parses environment variables to find users to create. It looks for keys starting with DB_ and ending with _USERNAME.
Format:
  • Username:DB_{DB_NAME}_USERNAME
  • Password:DB_{DB_NAME}_PASSWORD
Example: Setting DB_MYSHOP_USERNAME=shop_admin will:
  1. Create a database named MYSHOP.
  2. Create a user named shop_admin.
  3. Grant shop_admin full access to MYSHOP.
🛡️ Safety & Cleanup
  • System Users: The provisioner contains a whitelist of system users (e.g., root, mysql.sys, healthcheck) that it will never delete, even if they are not in your environment variables.
  • Stale Users: Any non-system user found in the database that is not defined in your current environment variables will be dropped. This ensures your database doesn't accumulate "zombie" accounts from old configurations.
🛠️ Built With
  • .NET 10
  • MySqlConnector
  • Docker (Alpine Linux)
About
DbProvisioner is a lightweight .NET code-first utility that automatically configure database users, passwords, and schemas every time you deploy or restart your stack
Resources
Readme
GPL-2.0 license
Activity
Stars
1 star
Watchers
0 watching
Forks
0 forks
Report repository
Releases
Packages
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Highlight search terms from Google/DuckDuckGo/Bing referrer
(function() {
var ref = document.referrer;
var terms = [];
if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {
var url = new URL(ref);
var q = url.searchParams.get('q') || url.searchParams.get('p');
if (q) {
terms = q.split(/\s+/).filter(function(t) { return t.length > 2; });
}
}
if (terms.length === 0) return;
var style = document.createElement('style');
style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';
document.head.appendChild(style);
function highlight(node) {
if (node.nodeType === 3) { // text node
var text = node.textContent;
var found = false;
terms.forEach(function(term) {
var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\]\\]/g, '\\') + ')', 'gi');
if (regex.test(text)) {
found = true;
var frag = document.createDocumentFragment();
var parts = text.split(regex);
parts.forEach(function(part, i) {
if (i % 2 === 0) {
frag.appendChild(document.createTextNode(part));
} else {
var span = document.createElement('span');
span.className = 'userscript-highlight';
span.textContent = part;
frag.appendChild(span);
}
});
node.parentNode.replaceChild(frag, node);
}
});
} else if (node.nodeType === 1 && node.childNodes) { // element
var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];
if (!skipTags.includes(node.tagName)) {
Array.from(node.childNodes).forEach(highlight);
}
}
}
highlight(document.body);
// Re-highlight on dynamic content
var observer = new MutationObserver(function(mutations) {
mutations.forEach(function(m) {
m.addedNodes.forEach(function(node) {
if (node.nodeType === 1 || node.nodeType === 3) highlight(node);
});
});
});
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
GitHub - icavalheiro/DbProvisioner: DbProvisioner is a lightweight .NET code-first utility that automatically configure database users, passwords, and schemas every time you deploy or restart your stack · GitHub
Skip to content
BranchesTags
Repository files navigation
DbProvisioner
DbProvisioner is a lightweight .NET code-first utility designed to run as an ephemeral container within your Docker Compose stack. Its primary goal is to automatically configure database users, passwords, and schemas every time you deploy or restart your stack. It's meant to be used on those scenarios that you make use of a single database for multiple services.
It ensures your database access controls are always in sync with your environment configuration, handling the creation of new users and the cleanup of obsolete ones.
DbProvisioner is currently considered feature complete. It fulfills its primary purpose of synchronizing database users and schemas via environment variables within a containerized environment. But we are open for PRs with added features, please check the CONTRIBUTION.md for more details.
🚀 How it Works
When the container starts, it performs the following logic:
  1. Connects to the target database server (MySQL/MariaDB) using administrative credentials.
  2. Scans Environment Variables to identify desired users and databases (based on variables matching the pattern DB_{NAME}_USERNAME).
  3. Syncs State:
    • Creates users/databases that do not exist.
    • Updates passwords for existing users (ensuring credentials are up to date).
    • GrantsALL PRIVILEGES to the user for their specific database.
    • Removes users found in the database but not in the environment variables (excluding system users like root).
🐳 Docker Compose Integration
This is the recommended way to use DbProvisioner. Add it to your docker-compose.yml alongside your database container.
Note: The provisioner needs to wait for the database to be healthy before running.
services:
# Your Database Servicedb:
image: mariadb:10.6 # or mysql:8environment:
MYSQL_ROOT_PASSWORD: root_secret_passwordhealthcheck:
test: ["CMD", "healthcheck.sh", "--connect", "--innodb_initialized"]interval: 10stimeout: 5sretries: 5# The Provisioner Servicedb-provisioner:
image: ghcr.io/icavalheiro/dbprovisioner:latestdepends_on:
db:
condition: service_healthyenvironment:
DB_HOST: dbDB_USER: rootDB_PASSWORD: root_secret_password# --- Users to Provision ---# Pattern: DB_{NAME}_USERNAME & DB_{NAME}_PASSWORD# Creates database "APP_ONE" and user "app_user"DB_APP_ONE_USERNAME: app_userDB_APP_ONE_PASSWORD: secure_pass_123# Creates database "ANALYTICS" and user "data_svc"DB_ANALYTICS_USERNAME: data_svcDB_ANALYTICS_PASSWORD: another_secure_pass
⚙️ Configuration
The application is configured entirely via Environment Variables.
Connection Settings
These variables tell the provisioner how to connect to the server to perform administrative tasks.
VariableDescriptionDefault
DB_HOSTThe hostname of the database server (e.g., db or localhost).Required
DB_USERAdmin username (usually root).Required
DB_PASSWORDAdmin password.Required
DB_NAMEThe initial database to connect to.mysql
User & Database Definition
The provisioner dynamically parses environment variables to find users to create. It looks for keys starting with DB_ and ending with _USERNAME.
Format:
  • Username:DB_{DB_NAME}_USERNAME
  • Password:DB_{DB_NAME}_PASSWORD
Example: Setting DB_MYSHOP_USERNAME=shop_admin will:
  1. Create a database named MYSHOP.
  2. Create a user named shop_admin.
  3. Grant shop_admin full access to MYSHOP.
🛡️ Safety & Cleanup
  • System Users: The provisioner contains a whitelist of system users (e.g., root, mysql.sys, healthcheck) that it will never delete, even if they are not in your environment variables.
  • Stale Users: Any non-system user found in the database that is not defined in your current environment variables will be dropped. This ensures your database doesn't accumulate "zombie" accounts from old configurations.
🛠️ Built With
  • .NET 10
  • MySqlConnector
  • Docker (Alpine Linux)
About
DbProvisioner is a lightweight .NET code-first utility that automatically configure database users, passwords, and schemas every time you deploy or restart your stack
Resources
Readme
GPL-2.0 license
Activity
Stars
1 star
Watchers
0 watching
Forks
0 forks
Report repository
Releases
Packages
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Strip utm_, fbclid, gclid, etc. from all links on page
(function() {
var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',
'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',
'ref', 'ref_src', 'source', 'medium', 'campaign'];
function cleanUrl(url) {
try {
var u = new URL(url, window.location.origin);
var changed = false;
trackingParams.forEach(function(p) {
if (u.searchParams.has(p)) {
u.searchParams.delete(p);
changed = true;
}
});
return changed ? u.toString() : url;
} catch (e) {
return url;
}
}
function cleanLinks() {
document.querySelectorAll('a[href]').forEach(function(a) {
var clean = cleanUrl(a.href);
if (clean !== a.href) a.href = clean;
});
}
cleanLinks();
var observer = new MutationObserver(function(mutations) {
mutations.forEach(function(m) {
m.addedNodes.forEach(function(node) {
if (node.nodeType === 1) {
if (node.tagName === 'A') cleanLinks();
node.querySelectorAll('a[href]').forEach(function(a) {
var clean = cleanUrl(a.href);
if (clean !== a.href) a.href = clean;
});
}
});
});
});
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); }
})();
(function(){
try {
var __m = "youtube.com";
var __re = new RegExp('^' + "youtube\\.com" + '
GitHub - icavalheiro/DbProvisioner: DbProvisioner is a lightweight .NET code-first utility that automatically configure database users, passwords, and schemas every time you deploy or restart your stack · GitHub
Skip to content
BranchesTags
Repository files navigation
DbProvisioner
DbProvisioner is a lightweight .NET code-first utility designed to run as an ephemeral container within your Docker Compose stack. Its primary goal is to automatically configure database users, passwords, and schemas every time you deploy or restart your stack. It's meant to be used on those scenarios that you make use of a single database for multiple services.
It ensures your database access controls are always in sync with your environment configuration, handling the creation of new users and the cleanup of obsolete ones.
DbProvisioner is currently considered feature complete. It fulfills its primary purpose of synchronizing database users and schemas via environment variables within a containerized environment. But we are open for PRs with added features, please check the CONTRIBUTION.md for more details.
🚀 How it Works
When the container starts, it performs the following logic:
  1. Connects to the target database server (MySQL/MariaDB) using administrative credentials.
  2. Scans Environment Variables to identify desired users and databases (based on variables matching the pattern DB_{NAME}_USERNAME).
  3. Syncs State:
    • Creates users/databases that do not exist.
    • Updates passwords for existing users (ensuring credentials are up to date).
    • GrantsALL PRIVILEGES to the user for their specific database.
    • Removes users found in the database but not in the environment variables (excluding system users like root).
🐳 Docker Compose Integration
This is the recommended way to use DbProvisioner. Add it to your docker-compose.yml alongside your database container.
Note: The provisioner needs to wait for the database to be healthy before running.
services:
# Your Database Servicedb:
image: mariadb:10.6 # or mysql:8environment:
MYSQL_ROOT_PASSWORD: root_secret_passwordhealthcheck:
test: ["CMD", "healthcheck.sh", "--connect", "--innodb_initialized"]interval: 10stimeout: 5sretries: 5# The Provisioner Servicedb-provisioner:
image: ghcr.io/icavalheiro/dbprovisioner:latestdepends_on:
db:
condition: service_healthyenvironment:
DB_HOST: dbDB_USER: rootDB_PASSWORD: root_secret_password# --- Users to Provision ---# Pattern: DB_{NAME}_USERNAME & DB_{NAME}_PASSWORD# Creates database "APP_ONE" and user "app_user"DB_APP_ONE_USERNAME: app_userDB_APP_ONE_PASSWORD: secure_pass_123# Creates database "ANALYTICS" and user "data_svc"DB_ANALYTICS_USERNAME: data_svcDB_ANALYTICS_PASSWORD: another_secure_pass
⚙️ Configuration
The application is configured entirely via Environment Variables.
Connection Settings
These variables tell the provisioner how to connect to the server to perform administrative tasks.
VariableDescriptionDefault
DB_HOSTThe hostname of the database server (e.g., db or localhost).Required
DB_USERAdmin username (usually root).Required
DB_PASSWORDAdmin password.Required
DB_NAMEThe initial database to connect to.mysql
User & Database Definition
The provisioner dynamically parses environment variables to find users to create. It looks for keys starting with DB_ and ending with _USERNAME.
Format:
  • Username:DB_{DB_NAME}_USERNAME
  • Password:DB_{DB_NAME}_PASSWORD
Example: Setting DB_MYSHOP_USERNAME=shop_admin will:
  1. Create a database named MYSHOP.
  2. Create a user named shop_admin.
  3. Grant shop_admin full access to MYSHOP.
🛡️ Safety & Cleanup
  • System Users: The provisioner contains a whitelist of system users (e.g., root, mysql.sys, healthcheck) that it will never delete, even if they are not in your environment variables.
  • Stale Users: Any non-system user found in the database that is not defined in your current environment variables will be dropped. This ensures your database doesn't accumulate "zombie" accounts from old configurations.
🛠️ Built With
  • .NET 10
  • MySqlConnector
  • Docker (Alpine Linux)
About
DbProvisioner is a lightweight .NET code-first utility that automatically configure database users, passwords, and schemas every time you deploy or restart your stack
Resources
Readme
GPL-2.0 license
Activity
Stars
1 star
Watchers
0 watching
Forks
0 forks
Report repository
Releases
Packages
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Auto-enable theater mode on YouTube
(function() {
function tryTheater() {
var btn = document.querySelector('button[aria-label="Theater mode"], ytd-player #player button[title="Theater mode"]');
if (btn && !btn.classList.contains('activated')) {
btn.click();
}
}
// Try immediately
tryTheater();
// Try after navigation (SPA)
var lastUrl = location.href;
setInterval(function() {
if (location.href !== lastUrl) {
lastUrl = location.href;
setTimeout(tryTheater, 500);
}
}, 1000);
// Also try on player load
var observer = new MutationObserver(tryTheater);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
GitHub - icavalheiro/DbProvisioner: DbProvisioner is a lightweight .NET code-first utility that automatically configure database users, passwords, and schemas every time you deploy or restart your stack · GitHub
Skip to content
BranchesTags
Repository files navigation
DbProvisioner
DbProvisioner is a lightweight .NET code-first utility designed to run as an ephemeral container within your Docker Compose stack. Its primary goal is to automatically configure database users, passwords, and schemas every time you deploy or restart your stack. It's meant to be used on those scenarios that you make use of a single database for multiple services.
It ensures your database access controls are always in sync with your environment configuration, handling the creation of new users and the cleanup of obsolete ones.
DbProvisioner is currently considered feature complete. It fulfills its primary purpose of synchronizing database users and schemas via environment variables within a containerized environment. But we are open for PRs with added features, please check the CONTRIBUTION.md for more details.
🚀 How it Works
When the container starts, it performs the following logic:
  1. Connects to the target database server (MySQL/MariaDB) using administrative credentials.
  2. Scans Environment Variables to identify desired users and databases (based on variables matching the pattern DB_{NAME}_USERNAME).
  3. Syncs State:
    • Creates users/databases that do not exist.
    • Updates passwords for existing users (ensuring credentials are up to date).
    • GrantsALL PRIVILEGES to the user for their specific database.
    • Removes users found in the database but not in the environment variables (excluding system users like root).
🐳 Docker Compose Integration
This is the recommended way to use DbProvisioner. Add it to your docker-compose.yml alongside your database container.
Note: The provisioner needs to wait for the database to be healthy before running.
services:
# Your Database Servicedb:
image: mariadb:10.6 # or mysql:8environment:
MYSQL_ROOT_PASSWORD: root_secret_passwordhealthcheck:
test: ["CMD", "healthcheck.sh", "--connect", "--innodb_initialized"]interval: 10stimeout: 5sretries: 5# The Provisioner Servicedb-provisioner:
image: ghcr.io/icavalheiro/dbprovisioner:latestdepends_on:
db:
condition: service_healthyenvironment:
DB_HOST: dbDB_USER: rootDB_PASSWORD: root_secret_password# --- Users to Provision ---# Pattern: DB_{NAME}_USERNAME & DB_{NAME}_PASSWORD# Creates database "APP_ONE" and user "app_user"DB_APP_ONE_USERNAME: app_userDB_APP_ONE_PASSWORD: secure_pass_123# Creates database "ANALYTICS" and user "data_svc"DB_ANALYTICS_USERNAME: data_svcDB_ANALYTICS_PASSWORD: another_secure_pass
⚙️ Configuration
The application is configured entirely via Environment Variables.
Connection Settings
These variables tell the provisioner how to connect to the server to perform administrative tasks.
VariableDescriptionDefault
DB_HOSTThe hostname of the database server (e.g., db or localhost).Required
DB_USERAdmin username (usually root).Required
DB_PASSWORDAdmin password.Required
DB_NAMEThe initial database to connect to.mysql
User & Database Definition
The provisioner dynamically parses environment variables to find users to create. It looks for keys starting with DB_ and ending with _USERNAME.
Format:
  • Username:DB_{DB_NAME}_USERNAME
  • Password:DB_{DB_NAME}_PASSWORD
Example: Setting DB_MYSHOP_USERNAME=shop_admin will:
  1. Create a database named MYSHOP.
  2. Create a user named shop_admin.
  3. Grant shop_admin full access to MYSHOP.
🛡️ Safety & Cleanup
  • System Users: The provisioner contains a whitelist of system users (e.g., root, mysql.sys, healthcheck) that it will never delete, even if they are not in your environment variables.
  • Stale Users: Any non-system user found in the database that is not defined in your current environment variables will be dropped. This ensures your database doesn't accumulate "zombie" accounts from old configurations.
🛠️ Built With
  • .NET 10
  • MySqlConnector
  • Docker (Alpine Linux)
About
DbProvisioner is a lightweight .NET code-first utility that automatically configure database users, passwords, and schemas every time you deploy or restart your stack
Resources
Readme
GPL-2.0 license
Activity
Stars
1 star
Watchers
0 watching
Forks
0 forks
Report repository
Releases
Packages
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Remove or un-stick sticky/fixed headers that block content
(function() {
function unstick() {
document.querySelectorAll('header, nav, [role="banner"], .header, .navbar, .sticky, .fixed-top, [style*="position: fixed"], [style*="position:sticky"]').forEach(function(el) {
if (el.style.position === 'fixed' || el.style.position === 'sticky' || getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {
el.style.position = 'static';
el.style.top = 'auto';
el.style.zIndex = 'auto';
}
});
}
unstick();
var observer = new MutationObserver(unstick);
observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });
})();
}
} catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
GitHub - icavalheiro/DbProvisioner: DbProvisioner is a lightweight .NET code-first utility that automatically configure database users, passwords, and schemas every time you deploy or restart your stack · GitHub
Skip to content
BranchesTags
Repository files navigation
DbProvisioner
DbProvisioner is a lightweight .NET code-first utility designed to run as an ephemeral container within your Docker Compose stack. Its primary goal is to automatically configure database users, passwords, and schemas every time you deploy or restart your stack. It's meant to be used on those scenarios that you make use of a single database for multiple services.
It ensures your database access controls are always in sync with your environment configuration, handling the creation of new users and the cleanup of obsolete ones.
DbProvisioner is currently considered feature complete. It fulfills its primary purpose of synchronizing database users and schemas via environment variables within a containerized environment. But we are open for PRs with added features, please check the CONTRIBUTION.md for more details.
🚀 How it Works
When the container starts, it performs the following logic:
  1. Connects to the target database server (MySQL/MariaDB) using administrative credentials.
  2. Scans Environment Variables to identify desired users and databases (based on variables matching the pattern DB_{NAME}_USERNAME).
  3. Syncs State:
    • Creates users/databases that do not exist.
    • Updates passwords for existing users (ensuring credentials are up to date).
    • GrantsALL PRIVILEGES to the user for their specific database.
    • Removes users found in the database but not in the environment variables (excluding system users like root).
🐳 Docker Compose Integration
This is the recommended way to use DbProvisioner. Add it to your docker-compose.yml alongside your database container.
Note: The provisioner needs to wait for the database to be healthy before running.
services:
# Your Database Servicedb:
image: mariadb:10.6 # or mysql:8environment:
MYSQL_ROOT_PASSWORD: root_secret_passwordhealthcheck:
test: ["CMD", "healthcheck.sh", "--connect", "--innodb_initialized"]interval: 10stimeout: 5sretries: 5# The Provisioner Servicedb-provisioner:
image: ghcr.io/icavalheiro/dbprovisioner:latestdepends_on:
db:
condition: service_healthyenvironment:
DB_HOST: dbDB_USER: rootDB_PASSWORD: root_secret_password# --- Users to Provision ---# Pattern: DB_{NAME}_USERNAME & DB_{NAME}_PASSWORD# Creates database "APP_ONE" and user "app_user"DB_APP_ONE_USERNAME: app_userDB_APP_ONE_PASSWORD: secure_pass_123# Creates database "ANALYTICS" and user "data_svc"DB_ANALYTICS_USERNAME: data_svcDB_ANALYTICS_PASSWORD: another_secure_pass
⚙️ Configuration
The application is configured entirely via Environment Variables.
Connection Settings
These variables tell the provisioner how to connect to the server to perform administrative tasks.
VariableDescriptionDefault
DB_HOSTThe hostname of the database server (e.g., db or localhost).Required
DB_USERAdmin username (usually root).Required
DB_PASSWORDAdmin password.Required
DB_NAMEThe initial database to connect to.mysql
User & Database Definition
The provisioner dynamically parses environment variables to find users to create. It looks for keys starting with DB_ and ending with _USERNAME.
Format:
  • Username:DB_{DB_NAME}_USERNAME
  • Password:DB_{DB_NAME}_PASSWORD
Example: Setting DB_MYSHOP_USERNAME=shop_admin will:
  1. Create a database named MYSHOP.
  2. Create a user named shop_admin.
  3. Grant shop_admin full access to MYSHOP.
🛡️ Safety & Cleanup
  • System Users: The provisioner contains a whitelist of system users (e.g., root, mysql.sys, healthcheck) that it will never delete, even if they are not in your environment variables.
  • Stale Users: Any non-system user found in the database that is not defined in your current environment variables will be dropped. This ensures your database doesn't accumulate "zombie" accounts from old configurations.
🛠️ Built With
  • .NET 10
  • MySqlConnector
  • Docker (Alpine Linux)
About
DbProvisioner is a lightweight .NET code-first utility that automatically configure database users, passwords, and schemas every time you deploy or restart your stack
Resources
Readme
GPL-2.0 license
Activity
Stars
1 star
Watchers
0 watching
Forks
0 forks
Report repository
Releases
Packages
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Universal Dark Mode - works on any site
(function() {
var enabled = true;
function applyDarkMode() {
if (!enabled) return;
// Create style element if it doesn't exist
var style = document.getElementById('universal-dark-mode-style');
if (!style) {
style = document.createElement('style');
style.id = 'universal-dark-mode-style';
document.head.appendChild(style);
}
// Dark mode CSS - inverts colors but preserves images/video
style.textContent = '
/* Invert everything except media */
html {
filter: invert(1) hue-rotate(180deg) !important;
background: #1a1a2e !important;
}
/* Restore images, videos, iframes, canvas */
img, video, iframe, canvas, svg, picture, [style*="background-image"] {
filter: invert(1) hue-rotate(180deg) !important;
}
/* Preserve specific elements that should not be inverted */
.no-dark-mode, .no-dark-mode *,
[data-theme="light"], [data-theme="light"],
.ace_editor, .ace_editor *,
.CodeMirror, .CodeMirror *,
.monaco-editor, .monaco-editor *,
.markdown-body pre, .markdown-body pre *,
.highlight, .highlight *,
pre code, pre code * {
filter: none !important;
}
/* Fix common UI elements */
.modal, .popup, .dropdown-menu, .tooltip, .popover {
filter: invert(1) hue-rotate(180deg) !important;
background: #2d2d44 !important;
border-color: #444 !important;
}
/* Scrollbars */
::-webkit-scrollbar { background: #1a1a2e !important; }
::-webkit-scrollbar-thumb { background: #444 !important; }
::-webkit-scrollbar-thumb:hover { background: #555 !important; }
/* Selection */
::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }
::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }
';
}
function removeDarkMode() {
var style = document.getElementById('universal-dark-mode-style');
if (style) style.remove();
}
// Toggle with Alt+Shift+D
document.addEventListener('keydown', function(e) {
if (e.altKey && e.shiftKey && e.key === 'D') {
e.preventDefault();
enabled = !enabled;
if (enabled) {
applyDarkMode();
console.log('[Universal Dark Mode] Enabled');
} else {
removeDarkMode();
console.log('[Universal Dark Mode] Disabled');
}
}
});
// Apply on load
applyDarkMode();
// Re-apply on dynamic content
var observer = new MutationObserver(function(mutations) {
if (enabled && !document.getElementById('universal-dark-mode-style')) {
applyDarkMode();
}
});
observer.observe(document.head, { childList: true });
console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');
})();
}
} catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); }
})();
})();
GitHub - icavalheiro/DbProvisioner: DbProvisioner is a lightweight .NET code-first utility that automatically configure database users, passwords, and schemas every time you deploy or restart your stack · GitHub
Skip to content
BranchesTags
Repository files navigation
DbProvisioner
DbProvisioner is a lightweight .NET code-first utility designed to run as an ephemeral container within your Docker Compose stack. Its primary goal is to automatically configure database users, passwords, and schemas every time you deploy or restart your stack. It's meant to be used on those scenarios that you make use of a single database for multiple services.
It ensures your database access controls are always in sync with your environment configuration, handling the creation of new users and the cleanup of obsolete ones.
DbProvisioner is currently considered feature complete. It fulfills its primary purpose of synchronizing database users and schemas via environment variables within a containerized environment. But we are open for PRs with added features, please check the CONTRIBUTION.md for more details.
🚀 How it Works
When the container starts, it performs the following logic:
  1. Connects to the target database server (MySQL/MariaDB) using administrative credentials.
  2. Scans Environment Variables to identify desired users and databases (based on variables matching the pattern DB_{NAME}_USERNAME).
  3. Syncs State:
    • Creates users/databases that do not exist.
    • Updates passwords for existing users (ensuring credentials are up to date).
    • GrantsALL PRIVILEGES to the user for their specific database.
    • Removes users found in the database but not in the environment variables (excluding system users like root).
🐳 Docker Compose Integration
This is the recommended way to use DbProvisioner. Add it to your docker-compose.yml alongside your database container.
Note: The provisioner needs to wait for the database to be healthy before running.
services:
# Your Database Servicedb:
image: mariadb:10.6 # or mysql:8environment:
MYSQL_ROOT_PASSWORD: root_secret_passwordhealthcheck:
test: ["CMD", "healthcheck.sh", "--connect", "--innodb_initialized"]interval: 10stimeout: 5sretries: 5# The Provisioner Servicedb-provisioner:
image: ghcr.io/icavalheiro/dbprovisioner:latestdepends_on:
db:
condition: service_healthyenvironment:
DB_HOST: dbDB_USER: rootDB_PASSWORD: root_secret_password# --- Users to Provision ---# Pattern: DB_{NAME}_USERNAME & DB_{NAME}_PASSWORD# Creates database "APP_ONE" and user "app_user"DB_APP_ONE_USERNAME: app_userDB_APP_ONE_PASSWORD: secure_pass_123# Creates database "ANALYTICS" and user "data_svc"DB_ANALYTICS_USERNAME: data_svcDB_ANALYTICS_PASSWORD: another_secure_pass
⚙️ Configuration
The application is configured entirely via Environment Variables.
Connection Settings
These variables tell the provisioner how to connect to the server to perform administrative tasks.
VariableDescriptionDefault
DB_HOSTThe hostname of the database server (e.g., db or localhost).Required
DB_USERAdmin username (usually root).Required
DB_PASSWORDAdmin password.Required
DB_NAMEThe initial database to connect to.mysql
User & Database Definition
The provisioner dynamically parses environment variables to find users to create. It looks for keys starting with DB_ and ending with _USERNAME.
Format:
  • Username:DB_{DB_NAME}_USERNAME
  • Password:DB_{DB_NAME}_PASSWORD
Example: Setting DB_MYSHOP_USERNAME=shop_admin will:
  1. Create a database named MYSHOP.
  2. Create a user named shop_admin.
  3. Grant shop_admin full access to MYSHOP.
🛡️ Safety & Cleanup
  • System Users: The provisioner contains a whitelist of system users (e.g., root, mysql.sys, healthcheck) that it will never delete, even if they are not in your environment variables.
  • Stale Users: Any non-system user found in the database that is not defined in your current environment variables will be dropped. This ensures your database doesn't accumulate "zombie" accounts from old configurations.
🛠️ Built With
  • .NET 10
  • MySqlConnector
  • Docker (Alpine Linux)
About
DbProvisioner is a lightweight .NET code-first utility that automatically configure database users, passwords, and schemas every time you deploy or restart your stack
Resources
Readme
GPL-2.0 license
Activity
Stars
1 star
Watchers
0 watching
Forks
0 forks
Report repository
Releases
Packages
Contributors
Languages