Forge Logic_Telegram bots · Mini Apps · turnkey servers
Oleksandr Nechytailo · automation developer
I build Telegram bots and Mini Apps, and deploy and support servers. So everything runs around the clock and doesn’t ping the admin over every little thing.
ls -la ./services/ services: Telegram bots, Mini Apps, servers, Excel
Telegram bots
Bookings, notifications, alerts, admin panels for the owner. I write in Python or PowerShell, depending on what you already run.
Telegram Mini Apps
For when chat buttons aren’t enough. A full interface right inside Telegram: roles, a PIN for important actions, light and dark themes.
Server deployment, setup and support
Windows Server, RDS, Hyper-V, WireGuard. Monitoring, backups you can actually restore from, and control from your phone.
Excel · VBA · Python
Macros, reports, Excel and Word parsing. The stuff someone currently does by hand for hours.
cat ./cases/remote-office.md case studies from real projects
A remote office for 19 workstations
## Summary
In about a week, fully remotely, I brought up a new terminal server for an office: 19 people work through their own VPN, the server is invisible from outside, and nightly copies come with a tested restore.
## Under the hood
316 product cards into Word in one day
## Summary
An archive of 318 folders, each needing a description, specs and reviews copied from a website into an old .doc. By hand that's 26+ hours. The parser produced 316 files in about 2 hours.
## Under the hood
Kids' café bookings in Telegram: from 3–4 to 5–7 parties a week
## Summary
A kids' café took bookings by phone and in messengers. Since the bot launched, parties went from 3–4 to 5–7 a week, and 4–5 of them are booked through the bot.
## Under the hood
19 workstations under control from the owner's phone
## Summary
The office owner called the admin over every little thing. Now he has a Telegram bot with a Mini App panel: he sees who's working, shuts off logins, adds people and restarts the server himself, from his phone.
## Under the hood
ls ./cases/ all cases
./ship.sh --verbose how I work: from brief to handover
- BriefWe dig into the task and agree on what counts as “done”.
- PrototypeI show a mockup or a demo on a test bench before the main code.
- BuildIn small stages. A backup before every change, a rollback for each.
- TestingFirst on a copy of your environment, then on the live one.
- HandoverA guide, I explain how to use it, and I stay in touch.
cat ./stack.json tech and principles
- not a single port open to the outside
- roles and a PIN on everything critical
- a backup before every change
- its own rollback for every stage
- an owner’s guide included