EAWF: Difference between revisions

From EAWF Document Repository
Jump to navigation Jump to search
← Older edit

Admin (talk | contribs)

7 user groups
418 edits
Admin (talk | contribs)
Bureaucrats, customers, eawf, Interface administrators, private, students, Administrators
418 edits
Admin (talk | contribs)
Bureaucrats, customers, eawf, Interface administrators, private, students, Administrators
418 edits
 
(8 intermediate revisions by the same user not shown)
Line 1: Line 1:
<small>[[Main_Page|Return to EAWF Main Page]]</small>
{{Parent|Main Page}}
== '''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
All critical business functions are designed to remain under EAWF control without dependence on SaaS providers or subscription-based business systems.


---
---
Line 59: Line 61:


==== Billing System ====
==== Billing System ====
Customer billing, invoicing, payment tracking, and Bitcoin payment processing.
[[EAWF Billing System]]
[[EAWF Billing System]]
* Customer billing, invoicing, payment tracking, and Bitcoin payment processing.


### Help Desk
==== Help Desk ====
 
Customer support and ticket management.
 
[[EAWF Help Desk]]
[[EAWF Help Desk]]
*Customer support and ticket management.


### Knowledge Base
==== Knowledge Base ====
 
Documentation, procedures, training materials, and internal reference information.
 
[[EAWF Knowledge Base]]
[[EAWF Knowledge Base]]
* Documentation, procedures, training materials, and internal reference information.


### Hosting Management
==== Hosting Management ====
 
Domain, hosting, email, and infrastructure management.
 
[[EAWF Hosting Management]]
[[EAWF Hosting Management]]
* Domain, hosting, email, and infrastructure management.


### Training Management
==== Training Management ====
 
Classes, students, instructors, attendance tracking, and course materials.
 
[[EAWF Training Management]]
[[EAWF Training Management]]
* Classes, students, instructors, attendance tracking, and course materials.


---
---


## EAWF Billing System
=== EAWF Billing System ===
 
### Documentation


==== Documentation ====
* [[EAWF Billing System/Security]]
* [[EAWF Billing System/Security]]
* [[EAWF Billing System/Database]]
* [[EAWF Billing System/Database]]
Line 103: Line 95:
* [[EAWF Billing System/Philosophy]]
* [[EAWF Billing System/Philosophy]]


### Current Design Status
==== Current Design Status ====


Status: Planning
* Status: '''Planning'''
 
Core Components:


==== Core Components: ====
* Users
* Users
* Clients
* Clients
Line 120: Line 111:
---
---


## System Architecture
== System Architecture ==
 
=== Public Infrastructure ===
### Public Infrastructure
'''Server: talon.eawf.com'''
 
Server:
 
* talon
 
Responsibilities:
 
* Customer Portal
* Customer Portal
* Billing
* Billing
Line 137: Line 121:
* Help Desk
* Help Desk


### Private Infrastructure
=== Private Infrastructure ===
'''Device: PC Stick (satoshi)'''
* Bitcoin Node
** Bitcoin Core
** Mining
** Address Monitoring
** Payment Detection
** Confirmation Tracking
''No public Bitcoin Core services are exposed.''<br>
''All communication is outbound from the home node.''


Server:
'''PC: Dell Laptop'''
 
* System Management
* Home Bitcoin Node
* System Programming
 
* Connectivity to & Control of all devices and servers.
Responsibilities:
 
* Bitcoin Core
* Mining
* Address Monitoring
* Payment Detection
* Confirmation Tracking
 
No public Bitcoin Core services are exposed.
 
All communication is outbound from the home node.


'''LaserJet Duplex Printer'''<br>
'''Color LaserJet Printer'''<br>
'''Label Printer'''<br>
'''SANE Scanner'''<br>
---
---


## Security Model
== Security Model ==
 
* Security levels determine page access.
Security levels determine page access.
 
| Level | Description  |
| ----- | ------------- |
| 0    | Guest        |
| 1    | User          |
| 2    | Client        |
| 3    | Student      |
| 4    | Reserved      |
| 5    | Instructor    |
| 6    | Clerk        |
| 7    | Manager      |
| 8    | CFO          |
| 9    | Administrator |


A higher level inherits all lower-level permissions.
{| class="wikitable"
|+ Caption text
|-
! 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
|}


See:
* A higher level inherits all lower-level permissions.


[[EAWF Billing System/Security]]
* See [[EAWF Billing System/Security]]


---
---


## Development Roadmap
== Development Roadmap ==
 
=== Phase 1 - Initial Development ===
### Phase 1
* Basic Page Template(s)
 
** Header
* Users
** Navigation
* Clients
** Body Styles
* Settings
** Footer
* Invoices
* CRUD Database Pages
* Invoice Lines
** Users
* PDF Invoices
** Clients
 
** Inventory
### Phase 2
** Settings
** Invoices
*** Invoice Headers
*** Invoice Lines
** PDF Invoices


=== Phase 2 - Product Development ===
* Payments
* Payments
* Audit Log
* Audit Log
Line 201: Line 202:
* Documents
* Documents


### Phase 3
=== Phase 3 - Bitcoin Implementation ===
 
* Sales Departments
* Bitcoin Drawers
** Wallets & Account Level Extended Public Keys
* Address Derivation
* Address Derivation
* Payment Pages
* Payment Pages
* QR Codes
* QR Codes


### Phase 4
=== Phase 4 - Bitcoin Integration & Automation ===
 
* Home Watcher
* Home Watcher
* Bitcoin Core Integration
* Bitcoin Core Integration
* Automatic Payment Detection
* Automatic Payment Detection


### Phase 5
=== Phase 5 - System Rollout ===
 
* Customer Portal
* Customer Portal
* Email Receipts
* Email Receipts
* Reporting
* Reporting


### Phase 6
=== Phase 6 - Additional Payment Options===
 
* Lightning Support
* Optional Lightning Support


---
---


## Guiding Principle
{{Copyright}}
 
When a choice exists between:
 
* Self-hosted versus SaaS
* Open source versus proprietary
* Owned infrastructure versus rented infrastructure
 
The preferred solution is the one that maximizes EAWF ownership, control, portability, and independence.

Latest revision as of 11:05, 30 May 2026

← Return to Main Page

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

EAWF Billing System

  • Customer billing, invoicing, payment tracking, and Bitcoin payment processing.

Help Desk

EAWF Help Desk

  • Customer support and ticket management.

Knowledge Base

EAWF Knowledge Base

  • Documentation, procedures, training materials, and internal reference information.

Hosting Management

EAWF Hosting Management

  • Domain, hosting, email, and infrastructure management.

Training Management

EAWF Training Management

  • Classes, students, instructors, attendance tracking, and course materials.

---

EAWF Billing System

Documentation

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.
Caption text
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

---

Copyright © 2017-2026 EAWF. All rights reserved.

Retrieved from "https://docs.eawf.com/index.php?title=EAWF&oldid=227"