CryptoIkra — Telegram store + landing page + WebApp "Wheel of Fortune"
CryptoIkra — a comprehensive sales and promotion mechanics system "turnkey": Telegram bot + landing page + WebApp + API + database + production deployment.
The user places an order in Telegram (catalog → cart → order), and the promotion mechanic "Wheel of Fortune" operates as a Telegram WebApp with results recorded on the server in PostgreSQL (not just random on the front end). All parts are deployed on a VPS under one domain with HTTPS and auto-start of services.
What has been implemented
1) Telegram bot (Python / Aiogram + PostgreSQL)
Product catalog by categories, product cards, selection of options/weights.
Cart: adding/removing, changing quantity, error protection (going "into the negative", repeated clicks).
Order placement: collecting client data, saving the order and its contents in the database.
Bonus system (coins): accrual/deduction, balance display, events.
Media support: photos + text + inline buttons (uniform message style).
Admin functions: newsletters and management, stabilization of project structure and imports.
2) Landing page (React + TypeScript + Vite)
Marketing page of the project on the domain.
Sections: product description, advantages, use cases, CTA transition to Telegram.
Assembly and deployment of static files, correct caching for updates.
3) WebApp "Wheel of Fortune" (React + TypeScript + Vite)
Telegram mini app: prize wheel, result UI, modals.
Integration with API/database — recording spin results and awarding prizes/bonuses.
Logic prepared for prize probability (weights).
4) API service (FastAPI + Uvicorn)
Backend for WebApp: endpoints for data retrieval and spin saving.
Connection to PostgreSQL (single database with the bot).
Deployed as a separate service and proxied through Nginx at /api/.
5) Infrastructure and deployment (VPS / Ubuntu)
Domain and DNS, HTTPS via Certbot (Let’s Encrypt) + auto-renewal.
Nginx reverse-proxy on one domain:
/ — landing
/wheel/ — WebApp
/api/ — API
Autostart via systemd: Telegram bot and API.
PostgreSQL: schema/permissions/service connections.
Caching configured: HTML without cache, static (JS/CSS) with long cache and versioning.
Challenges and solutions
Stabilization of cart and order logic (order is correctly completed, cart is not lost).
Protection against typical Telegram API errors (message is not modified), repeated actions, and incorrect states.
One domain for multiple applications without conflicts (landing + WebApp + API).
Real server recording of promotional results in the database.
Stack
Python, Aiogram, FastAPI, asyncpg/SQLAlchemy (async), PostgreSQL, React, TypeScript, Vite, Nginx, Certbot, systemd, Ubuntu VPS.
#telegrambot #aiogram #fastapi #react #typescript #postgresql #nginx #vps #webapp #landing #ecommerce #devops
The user places an order in Telegram (catalog → cart → order), and the promotion mechanic "Wheel of Fortune" operates as a Telegram WebApp with results recorded on the server in PostgreSQL (not just random on the front end). All parts are deployed on a VPS under one domain with HTTPS and auto-start of services.
What has been implemented
1) Telegram bot (Python / Aiogram + PostgreSQL)
Product catalog by categories, product cards, selection of options/weights.
Cart: adding/removing, changing quantity, error protection (going "into the negative", repeated clicks).
Order placement: collecting client data, saving the order and its contents in the database.
Bonus system (coins): accrual/deduction, balance display, events.
Media support: photos + text + inline buttons (uniform message style).
Admin functions: newsletters and management, stabilization of project structure and imports.
2) Landing page (React + TypeScript + Vite)
Marketing page of the project on the domain.
Sections: product description, advantages, use cases, CTA transition to Telegram.
Assembly and deployment of static files, correct caching for updates.
3) WebApp "Wheel of Fortune" (React + TypeScript + Vite)
Telegram mini app: prize wheel, result UI, modals.
Integration with API/database — recording spin results and awarding prizes/bonuses.
Logic prepared for prize probability (weights).
4) API service (FastAPI + Uvicorn)
Backend for WebApp: endpoints for data retrieval and spin saving.
Connection to PostgreSQL (single database with the bot).
Deployed as a separate service and proxied through Nginx at /api/.
5) Infrastructure and deployment (VPS / Ubuntu)
Domain and DNS, HTTPS via Certbot (Let’s Encrypt) + auto-renewal.
Nginx reverse-proxy on one domain:
/ — landing
/wheel/ — WebApp
/api/ — API
Autostart via systemd: Telegram bot and API.
PostgreSQL: schema/permissions/service connections.
Caching configured: HTML without cache, static (JS/CSS) with long cache and versioning.
Challenges and solutions
Stabilization of cart and order logic (order is correctly completed, cart is not lost).
Protection against typical Telegram API errors (message is not modified), repeated actions, and incorrect states.
One domain for multiple applications without conflicts (landing + WebApp + API).
Real server recording of promotional results in the database.
Stack
Python, Aiogram, FastAPI, asyncpg/SQLAlchemy (async), PostgreSQL, React, TypeScript, Vite, Nginx, Certbot, systemd, Ubuntu VPS.
#telegrambot #aiogram #fastapi #react #typescript #postgresql #nginx #vps #webapp #landing #ecommerce #devops
Dnepr 
Available for hire
Offer work