Two developers accidentally deploying over each other on a shared staging server can burn an entire afternoon of debugging. Instead of managing a third-party dashboard or screaming in Slack, we turned our Telegram team chat into an instant deploy locker with shared bot state and smart in-place callback edits. Anyone can see live server occupancy and toggle locks with a single tap.
๐ Filename:
command/staging.js๐จโ๐ป Code:
const holder = await BOT.getProp("staging_locked_by").value();
if (holder) {
sendMessage(`๐ด *Staging 1 is LOCKED* by ${holder}`, {
buttons: [{ text: "๐ Release Staging", command: "/unlock_staging" }]
});
} else {
sendMessage("๐ข *Staging 1 is AVAILABLE* for testing.", {
buttons: [{ text: "๐ Claim Staging", command: "/lock_staging" }]
});
}๐ Filename:
command/lock_staging.js๐จโ๐ป Code:
if (isCallback) {
answerCallback("Environment claimed!", false);
}
const claimant = user.first_name || user.username || "Anonymous Dev";
BOT.setProp("staging_locked_by", claimant);
editCallbackMessage(`๐ด *Staging 1 is LOCKED* by ${claimant}`, [
{ text: "๐ Release Staging", command: "/unlock_staging" }
]);๐ Filename:
command/unlock_staging.js๐จโ๐ป Code:
if (isCallback) {
answerCallback("Environment released!", false);
}
BOT.deleteProp("staging_locked_by");
editCallbackMessage("๐ข *Staging 1 is AVAILABLE* for testing.", [
{ text: "๐ Claim Staging", command: "/lock_staging" }
]);๐ก Always call
answerCallback first in your callback handlers to dismiss the Telegram button loading spinner immediately.โ ๏ธ Note: Shared status across all users is handled automatically via BOT.setProp, which syncs to your configured Firebase Realtime DB without any manual database setup.#FlexGram
