@egraich

Today I got the bot completely ready for shipping! I took a screenshot of it in action, beefed up the README, and did a final test of the CI/CD pipeline on my Nest server.
Now, all I have to do is push the code, and my Nest server handles the rest automatically :D

I finally fully deployed my VoiceBot on the Nest server along with the local telegram-api-server, which lets me process videos up to 2GB! The database is also fully up and running now, starting to collect data. Basically, anyone can now look up @egvoicebot on Telegram, add it to their group, and it’ll just work :D
(Btw, Groq gives me an 8-hour audio processing limit for free!)

Today I decided to add the official telegram-api-server to my Nest project. Why? Because this way my bot will be able to handle videos up to 2GB instead of the generic 20MB limit.
Honestly, this project is teaching me how to work with docker-compose files way better than any of my previous projects :)

I decided to build VoiceBot — a Telegram bot that extracts and transcribes audio from video files, video notes , and standard voice messages.

It’s a pure QoL tool built for that one painfully relatable situation: when your friend refuses to use their keyboard and bombards you with 3-minute voice notes while you are stuck in a meeting, a loud train, or just plain hate listening to audio.
Funnily enough, Telegram actually has this feature built-in… but only if you pay for Telegram Premium :D

Just updated the README once again and added a step-by-step production deployment guide. Also, the bot is now officially running 24/7 for everyone thanks to Nest! ❤

Today I’ve FINALLY completed my CI/CD auto-rebuild pipeline! Now, every single ‘git push’ to my public repositories triggers an instant automated update via a custom webhook system.

I really like visualizing my Linux directory structure as my own production-grade city, planning out neighborhoods and zones well in advance. As a result of this infrastructure layout, I now have 3 isolated Docker containers running flawlessly in my city:

• SlackBot
• TelegramBot
• Webhook Listener

Instead of using bloated, heavy out-of-the-box CI/CD platforms that would easily choke my tiny 2GB RAM Nest server, I deployed a minimal ‘almir/webhook’ image weighing only 19.2 MB. Because of this, my idle server consumes ~300 MB of RAM and takes up a mere ~1.4 GB of disk space :D

It was an unforgettable engineering experience building my own free analog of PaaS platforms like Amvera etc., completely from scratch.

Thank you Hack Club for Nest <3

Today, I decided to set up automatic redeployment for my bots on my favorite Linux-based Nest server , triggering on every git push to their public GitHub repositories <3

I lost a whole day trying to deploy my Telegram bot on Hack Club Nest. In the process, I found a ton of bugs, a broken OpenAI model from Groq 120B, and issues in my .env file (I literally had GROQ_AI_KEY instead of GROQ_API_KEY, lmao). But after a full day of fixes and guides, I finally managed to deploy my TG bot SIMULTANEOUSLY alongside the updated CyberShieldSlackBot (literally split VSCode terminal on photo) :D

I finally fixed all the bugs in my Slack bot while waiting for the Nest application to get approved :D

After getting the Nest server, I connected to a remote server via SSH for the first time in my life (and it’s definitely not my first time using Linux Debian, haha). But right after that, I deployed a Docker container for the first time ever!

I also completely filled the README with guides and setup instructions for users <3

The first version is officially ready! For the first time ever, I’ve created my own GitHub release and bundled the entire game into a 25MB .exe file.

Also upgrade README.

Shipping it in a bit! <3

Spent the last hour trying to port the project to web with pygbag, but no luck so far <3

On the bright side, I added time controls: you can now speed things up by 2x or 4x using numbers keys.

Also, moved everything to a config.py file, so you can easily tweak colors, base FPS, keybindings, and more.

Also fix some F11 bugs.

Finally, fully interactive drawing is now live.
You can left-click to spawn cells and right-click to wipe them out on the fly.

Added a proper pause state on Spacebar too, so you can stop time, comfortably sketch out gliders, spaceships, or any complex structures, and then let them loose.

Also made the window fully resizable, which means you can just hit the square icon to maximize it, or press F11 for a true borderless fullscreen. Had a bit of a nightmare with Windows loop-crashing the resolution scaling at first, but it is completely fixed now.

The grid dynamically auto-adjusts to whatever screen size you throw at it, keeping your current shapes intact while filling the new empty space with random chaos.

I just added a basic PyGame simulation and it looks cool!

With constants, I can easily change the grid size and colors.

Now I want to add the ability to pause the game and draw figures with a mouse click!

I decided to start this project to master NumPy, a useful library for matrix operations in Python.

I’m planning to use PyGame to visualize the game grid.

Also, the game board features wrapped boundaries, meaning cells seamlessly teleport to the opposite side when crossing the edges!

Added third command - /cyberstats, that
shows you usage stats of @CyberShieldBot.
Also send an application for Nest and generated my first ssh keys EVER!

Made a good root for the project with 5 py files. I wanna port my Telegram bot CyberPravoBot to Slack. I deleted a lot of functions, like the admin panel and model switching, but also added some new ones. I really like the shortcuts feature in Slack, so I integrated it into my bot too. Just 3 dots -> Connect to apps -> Scan Message. Right now my bot has only 2 out of 3 commands, but I’m not going to stop.

Final touches, sections, etc.
Egjoy huge minimap of main file in VSCode:)