dineshrepostry/post-chat

Purpose and Entry Points

POST-chat is a PHP/MySQL chat site for global room chat and one-to-one private chat. Apache serves the static/PHP pages; MySQL is initialized from postdb.sql. The public landing page is index.html; authentication begins at loginpage/loginpage.php, and account registration at createaccount/createaccount.html.

Authentication and Account Lifecycle

Account creation and login are handled by PHP endpoints under php/, backed by the shared database configuration in php/config.php. Core flows are registration through php/createacc.php, credential processing through php/login.php, and account/database validation through php/tablevalidate.php.

Global Chat Room

The primary global-chat UI is chat/chat.php, styled by chat/chat3.css. Its server-side chat data boundary is the root PHP API layer: message submission/storage uses php/insert.php and php/store.php, while retrieval uses php/get.php. This separates the rendered chat page from persistence operations.

Private Messaging

Private conversation functionality is served from privatechat/privatechat.php with presentation in privatechat/privatechat.css. It shares the application’s PHP/MySQL backend model but remains a distinct UI/control boundary from the global room in chat/chat.php.

Rooms and User-Managed State

Room assignment/creation is represented by roomassign/roomassign.php and php/createroom.php; deletion is handled by php/delete.php. User preferences include theme persistence via php/settheme.php. These endpoints form the mutable user/room state layer around the chat experience.

Feedback and Supporting Content

Feedback is collected through feedback/feedback.html, written via php/writefeed.php, and retrieved through php/getfeed.php. Documentation, policies, and static informational pages are independent content surfaces: documentation/documentation.html, policies/Policies.html, and post-documentation.pdf.

Separate End-Semester Scheduling Module

The repository also contains an instructor slot-management subsystem, separate from chat: endsem/instructor-slot.html, endsem/php/instructor-slot.php, and endsem/php/slot.php. It has its own connection configuration and schema artifacts in endsem/php/config.php and endsem/it5211.sql, indicating an independent scheduling database/domain boundary.

Runtime and Infrastructure

The application requires an Apache-compatible PHP runtime and MySQL. Main chat schema/data is imported from postdb.sql; the scheduling module provides endsem/it5211.sql. No client-side framework, build system, or external hosted service is represented; interaction is page/PHP-endpoint driven, with local assets including images/ and songs/.