rma80070

Man, this is a grind but worth it. The URL shortener finally feels like something I could actually deploy somewhere people use.

Ditched JSON for Real Database

First thing: goodbye JSON file. Writing to a file every single time someone shortens a URL was gonna break eventually. Switched to PostgreSQL (SQLite fallback for smaller setups). Now it actually handles multiple people using it at once without choking.

No More Sketchy Links

Added URL validation so I don’t accidentally turn this into a phishing playground. Checks if the link is safe before shortening it. Basic but important.

Users Can Actually Own Their Links Now

Built login/signup so people have their own accounts. They can see just their shortened URLs, track clicks on their stuff, delete what they don’t want. No more shared mess.

Spam Protection

Rate limiting by IP because obviously someone would try to abuse it. Can’t shorten 10,000 URLs per minute anymore—keeps the database happy and blocks the dumb attacks.

Tetris animation still lives on the homepage. Some things you don’t touch.

I am currently working on a URL Shortener web application with both CLI and web interfaces in Python/Flask. The web UI features a retro Tetris animation on the left side with falling blocks that stack properly, paired with a clean, modern form interface using an orange color scheme (#ff6b35).

Key features include:

Dual interfaces: Command-line tool (python main.py shorten “url”) and web dashboard
Animated Tetris game: Black blocks falling at random X positions, auto-clearing completed lines
Modern UI design: Press Start 2P retro font for the title, smooth transitions, toast notifications, and animated statistics
Full functionality: URL shortening with base62 codes, click tracking, JSON storage, copy-to-clipboard, and a list view for all URLs
Clean architecture: Separated concerns with shared backend logic, Flask routes, and organized file structure (templates, static/css, static/js)

Hey everyone, just wrapped up the CLI Task Manager and I’m stoked! Started Jan 6th as a basic foundation project and shipped a full production CLI across 6 phases in one week.

Day 1: Modular structure + add/list with tabulate tables. Day 2: complete/delete. Day 3: Refactoring/backups. Day 4: Colorama polish (green success, yellow pending, red errors). Day 5: Pytest suite (92% coverage, 28 tests). Day 6: search, priority, stats, data migration.

Tech stack rocks: Python 3.8+ (full type hints), argparse subparsers, tabulate, colorama (cross-platform), pytest. Full CRUD, filtering, search, stats - all with beautiful colored terminal output.

Modular design FTW - adding search took minutes. Tests caught 3 edge cases. Schema migration was tricky but nailed backward compatibility.

Went from 50-line prototype to 1,200+ lines across 8 files. Portfolio-ready with pro docs, pyproject.toml, VS Code settings.

I have added more features to the already existing CLI Task Manager like complete and delete each tasks. I have also added some polishing to the boring UI in the Command Line by add some colors to make it more vibrant and pleasing for the users

Im Working on a CLI Task Manager and have completed the First Phase of it. The first phase contains how you can add a task and view it. I’m adding more features in the upcoming phases such as Deleting, renaming and Polishing the UI of the CLI interface.