EAWF: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 1: | Line 1: | ||
<small>[[Main_Page|Return to Main Page]]</small> | <small>[[Main_Page|Return to Main Page]]</small> | ||
== '''EAWF Business Management System''' == | == '''EAWF Business Management System''' == | ||
=== Development Guiding Principles === | |||
* All critical business functions are designed to remain under EAWF control without dependence on SaaS providers or subscription-based business systems. | |||
* Preferred solutions to software issues are the ones that maximizes EAWF ownership, control, portability, and independence. | |||
* '''KISS!''' | |||
=== Purpose === | === Purpose === | ||
| Line 17: | Line 21: | ||
* Training Management | * Training Management | ||
* Reporting and Analytics | * Reporting and Analytics | ||
--- | --- | ||
| Line 79: | Line 81: | ||
--- | --- | ||
=== EAWF Billing System === | === EAWF Billing System === | ||
| Line 209: | Line 209: | ||
* QR Codes | * QR Codes | ||
=== Phase 4 - Bitcoin Integration & Automation === | |||
* Home Watcher | * Home Watcher | ||
* Bitcoin Core Integration | * Bitcoin Core Integration | ||
* Automatic Payment Detection | * Automatic Payment Detection | ||
=== Phase 5 - System Rollout === | |||
* Customer Portal | * Customer Portal | ||
* Email Receipts | * Email Receipts | ||
* Reporting | * Reporting | ||
=== Phase 6 - Additional Payment Options=== | |||
* Lightning Support | |||
* | |||
--- | --- | ||
Revision as of 05:59, 30 May 2026
EAWF Business Management System
Development Guiding Principles
- All critical business functions are designed to remain under EAWF control without dependence on SaaS providers or subscription-based business systems.
- Preferred solutions to software issues are the ones that maximizes EAWF ownership, control, portability, and independence.
- KISS!
Purpose
The EAWF Business Management System (EBMS) is a collection of self-hosted business applications designed to support EAWF operations.
The system is intended to provide:
- Customer Management
- Student Management
- Billing and Invoicing
- Bitcoin Payment Processing
- Knowledge Management
- Help Desk Operations
- Hosting Management
- Training Management
- Reporting and Analytics
---
Design Philosophy
The EBMS shall prioritize:
- Self-hosting
- Open source software
- Data ownership
- Long-term maintainability
- Minimal external dependencies
The EBMS shall avoid:
- SaaS platforms
- Vendor lock-in
- Subscription business software
- Third-party billing systems
- Cloud-hosted management platforms
Preferred technologies:
- Linux
- Apache
- MariaDB
- PHP 8
- Bitcoin Core
- MediaWiki
- osTicket
- Roundcube
- FPDF
All critical business data shall remain under EAWF control.
---
Current Projects
Billing System
- Customer billing, invoicing, payment tracking, and Bitcoin payment processing.
Help Desk
- Customer support and ticket management.
Knowledge Base
- Documentation, procedures, training materials, and internal reference information.
Hosting Management
- Domain, hosting, email, and infrastructure management.
Training Management
- Classes, students, instructors, attendance tracking, and course materials.
---
EAWF Billing System
Documentation
- EAWF Billing System/Security
- EAWF Billing System/Database
- EAWF Billing System/Invoices
- EAWF Billing System/Payments
- EAWF Billing System/Bitcoin
- EAWF Billing System/Watcher
- EAWF Billing System/Reports
- EAWF Billing System/Roadmap
- EAWF Billing System/Philosophy
Current Design Status
- Status: Planning
Core Components:
- Users
- Clients
- Invoices
- Invoice Lines
- PDF Generation
- Bitcoin Integration
- Customer Portal
- Reporting
---
System Architecture
Public Infrastructure
Server: talon.eawf.com
- Customer Portal
- Billing
- Invoices
- Payment Pages
- Documentation
- Help Desk
Private Infrastructure
Device: PC Stick (satoshi)
- Bitcoin Node
- Bitcoin Core
- Mining
- Address Monitoring
- Payment Detection
- Confirmation Tracking
No public Bitcoin Core services are exposed.
All communication is outbound from the home node.
PC: Dell Laptop
- System Management
- System Programming
- Connectivity to & Control of all devices and servers.
LaserJet Duplex Printer
Color LaserJet Printer
Label Printer
SANE Scanner
---
Security Model
- Security levels determine page access.
| Level | Purpose | Description |
|---|---|---|
| 0 | Guest | Example |
| 1 | Registered User | Example |
| 2 | Hosting Client | Example |
| 3 | Bitcoin Student | Example |
| 4 | Reserved | Reserved |
| 5 | Instructor | Contract or Employee Instructor |
| 6 | Clerk | Customer Support or Accounting |
| 7 | Manager | Department Manager |
| 8 | CFO | Chief Financial Officer or Attorney |
| 9 | CEO | Admin/Owner |
- A higher level inherits all lower-level permissions.
---
Development Roadmap
Phase 1 - Initial Development
- Basic Page Template(s)
- Header
- Navigation
- Body Styles
- Footer
- CRUD Database Pages
- Users
- Clients
- Inventory
- Settings
- Invoices
- Invoice Headers
- Invoice Lines
- PDF Invoices
Phase 2 - Product Development
- Payments
- Audit Log
- Invoice Events
- Client Notes
- Documents
Phase 3 - Bitcoin Implementation
- Sales Departments
- Wallets & Account Level Extended Public Keys
- Address Derivation
- Payment Pages
- QR Codes
Phase 4 - Bitcoin Integration & Automation
- Home Watcher
- Bitcoin Core Integration
- Automatic Payment Detection
Phase 5 - System Rollout
- Customer Portal
- Email Receipts
- Reporting
Phase 6 - Additional Payment Options
- Lightning Support
---