← Back to My Work
Home›Projects›Project-Tube
Foundation · Local video platform

Project-Tube

● Prototype / Foundation

A Flask-based local video hosting and playback prototype using SQLite for metadata and local file storage.

FlaskPythonSQLiteHTML/CSSJavaScriptsend_file
Project-Tube project visual
01 · OVERVIEW

What is Project-Tube?

What the project does

Project-Tube is a small media-server foundation that explores uploading video files, storing their paths in SQLite and serving them back through a browser player.

How it benefits the user/business

  • Demonstrates the basic architecture of a local video platform.
  • Connects file uploads with metadata persistence.
  • Provides browser playback for supported formats.
  • Makes a useful foundation for later authentication, metadata and streaming improvements.

Platform & environment

Local Flask web application using SQLite and a local uploads directory.

02 · FEATURES

What is included?

01 · Video uploadImplemented as part of the project's current scope.
02 · Local file storageImplemented as part of the project's current scope.
03 · SQLite metadataImplemented as part of the project's current scope.
04 · Supported extension checkingImplemented as part of the project's current scope.
05 · Video listingImplemented as part of the project's current scope.
06 · Browser playbackImplemented as part of the project's current scope.
07 · Dedicated player pageImplemented as part of the project's current scope.
08 · Simple local/LAN usageImplemented as part of the project's current scope.
03 · WORKFLOW

How the project works

Browser
  ↓
Upload Page
  ↓
Validate Extension
  ↓
Save Video File
  ↓
Store Path in SQLite
  ↓
Video Listing
  ↓
Select Video
  ↓
send_file()
  ↓
Browser Playback
04 · BACKEND

What role does the backend play?

The backend/application layer is responsible for connecting the interface to the project's data, business logic and user workflows.

  • Flask routes receive uploads and connect them with SQLite metadata.
  • The database stores the relationship between a video record and its stored file path.
  • The backend serves the selected video back to the browser through Flask's file-serving mechanism.
05 · USAGE

How is it used?

A user opens the local web app, uploads a supported video, sees it in the video interface and opens it in the browser player.

Project maturity: Prototype / Foundation. The purpose of this page is to explain the implementation that exists in the repository, while keeping production-readiness claims separate.
06 · LIMITATIONS

Current boundaries

This is not a YouTube-scale streaming system. Authentication, secure uploads, thumbnails, rich metadata, range-aware streaming, storage abstraction and scalable delivery would be required for production.