尚未偵測到更新。GitHub 發布版本後會顯示在這裡。
依最近已完成的 8 小時觀測回合間的 GitHub 星號增量排序
FloCafe is the free, local-first restaurant POS in the FloPOS ecosystem. Run orders, tables, kitchen display, and local data without a software subscription.
翻譯準備中
個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權，自行管理介紹，無需管理員核准。
登入並產生驗證檔案，在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案，即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入，將前往登入頁面。登入後請回到此處，再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify，即可驗證所有權並自行管理介紹。
一分鐘完成驗證A cyberfunky-themed, highly interactive e-commerce platform for custom gaming rigs. Features a fully integrated CLI, an intelligent AI shopping assistant, a gamified user experience, and a secure admin dashboard. Built with Node.js, Express, and MongoDB.
翻譯準備中
取自儲存庫 README
正在載入完整 README。 以下為已儲存的摘錄。
🦅 Phoenix Codex - Cyberpunk PC Store DEMO
🔗 Live Demo: https://codex-iota-nine.vercel.app
A high-end custom PC retail platform featuring a cyberpunk aesthetic and AI integration.
🚀 Features
• Cyberpunk UI: Built with CSS Grid and Flexbox for a full "Matrix" experience.
• Secure API Communication
• Support Assistant: Guided help menu (Codex Support) covering the most common customer questions.
• Holographic Effects Dynamic product showcase with hover effects.
• Mobile Optimized: Fully responsive layout for smartphones and tablets.檢視完整 README ↗🔗 Live Demo: https://codex-iota-nine.vercel.app A high-end custom PC retail platform featuring a cyberpunk aesthetic and AI integration.
/css: Contains all styling and media queries./js: Store logic and Chatbot functionality./assets: Images, GIFs, and sound effects.This project follows the Git Flow model. All development and testing occur in the main-test branch before merging into main.
Vercel is wired to match: a push to main-test builds a Preview deployment, and merging the
pull request into main is what promotes it to Production. The API lives in the separate
codex-backend repository and follows the same flow,
deployed on Render.
A single feature often touches both repositories, and they deploy independently. Deploy the backend first, wait for Render to report Live, and only then merge the frontend pull request.
An older frontend works fine against a newer API, because backend changes are additive. A frontend that ships first calls routes that do not exist yet and breaks production.