EAWF Document Repository - User contributions [en]

Business

2026-08-04T14:34:40Z

Admin:

{{Parent|Main_Page}}
== Business Documents and Tools ==

[[Mission|Mission Statement]]

[[Articles|Articles of Incorporation]]

[[OrgChart|Organization Chart]]

[[Policies]]

[[Procedures]]

[[BizPlan|Business Plan Builder Docs]]

Business

2026-08-04T14:32:23Z

Admin:

== Business Documents and Tools ==

[[Mission|Mission Statement]]

[[Articles|Articles of Incorporation]]

[[OrgChart|Organization Chart]]

[[Policies]]

[[Procedures]]

[[BizPlan|Business Plan Builder Docs]]

EAWFStandard

2026-08-04T14:30:05Z

Admin: /* EAWF Standards */

{{Parent|Main_Page}}
== EAWF Software Development Standard v1.0 ==

== Purpose ==

The EAWF Software Development Standard defines the minimum quality, documentation, installation, and support requirements for all software released by EAWF.

The objective is simple:

* Deliver software that is useful, professional, predictable, easy to install, easy to maintain, and enjoyable to use.

* Every EAWF project should provide a consistent user interface and experience regardless of language, operating system, or application.

== EAWF Standards ==
* [[StandardsGeneral|General]]
** [[StandardsProjects|Projects]]
** [[StandardsScripts|Scripts]]
** [[StandardsCredits|Credits and Attribution]]
** [[StandardsDocs|Documentation Headers and Footers]]
** [[Business|Business Plan Templates]]

== Programs/Scripts ==
=== BTC ===
* [[StandardsBTC|BTC]]
** [[StandardsBTCStartup|Startup]]
** [[StandardsBTCManagement|Management]]
** [[StandardsBTCProgram|BTC Program]]

=== Connect ===

* [[StandardsScripts|Scripts]]
** [[StandardsScripts|Scripts]]
** [[StandardsScripts|Scripts]]
** [[StandardsScripts|Scripts]]
** [[StandardsScripts|Scripts]]
** [[StandardsScripts|Scripts]]
** [[StandardsScripts|Scripts]]
** [[StandardsScripts|Scripts]]
** [[StandardsScripts|Scripts]]
** [[StandardsScripts|Scripts]]

== Core Philosophy ==

The EAWF Software Development Standard is based on the following principles:

* Follow established Linux conventions whenever practical.
* Keep programs simple.
* One tool should perform one primary task well.
* Do not expose implementation details to the user.
* Auto-detect sensible defaults whenever possible.
* Allow users to customize behavior without modifying program code.
* Never overwrite user configuration without permission.
* Documentation is part of the product.
* Installation and removal should be safe and straightforward.

---

=== Quality Standard ===

A version 1.0 release must satisfy the following requirements.

==== Functional: ====

* Stable operation
* No known functional defects
* Predictable behavior
* Clear error handling
* Professional command output

---

==== User Experience ====

* Clean command syntax
* Consistent help screens
* Quiet operation
* Friendly messages
* No unnecessary technical output
* Consistent formatting throughout the application

---

==== Installation ====

Every project should include:

* `.install.sh`
* `.uninstall.sh`
* README.md
* CHANGELOG.md
* LICENSE
* Man page
* Example configuration files

The installer should:

* Install safely
* Preserve existing user configuration
* Create missing configuration files from examples
* Verify prerequisites
* Report missing dependencies clearly

The uninstaller should remove the application while preserving user data unless explicitly requested otherwise.

== Linux Standards ==

* Programs should follow normal Linux conventions.

* Programs usually run from <code>/usr/local/bin</code>

* User Configuration: <code>~/.config/<project>/</code> e.g., <code>~/.config/connect/</code>

* Documentation Location: <code>/usr/local/share/doc/<project>/</code>

* Manual Pages: <code>/usr/local/share/man/man1/</code> e.g., <code>/usr/local/share/<project>/examples/</code>

* Logs: <code>~/.local/state/<project>/</code>
** Applications should create log directories only when logging is actually needed.

* Cache:
** Applications should '''**not**''' create cache directories unless there is a legitimate performance benefit.

* Avoid creating unnecessary files or directories "just in case."

* Configuration Philosophy: Separate configuration into logical responsibilities.

* Project Configuration: Contains definitions describing the project itself.

Example:
* Servers
* Hosts
* Network links
* Project mappings
* Deployment targets
Example:
connect.conf

* User Settings: Contains user preferences.

Example:

* Preferred editor
* Preferred file manager
* Color preferences
* Future display options

Example:

```
settings.conf
```

---

# Auto First

Every application should attempt to make intelligent default decisions.

Users should only need to customize behavior if they want something different.

Examples:

* Respect `$EDITOR`
* Auto-detect running file manager
* Automatically disable color when output is redirected
* Honor existing SSH configuration

---

# Customization

Power users should always be able to override automatic behavior.

Customization should be achieved through configuration files rather than modifying application code.

---

# Documentation

Every project should provide documentation at three levels.

## README

Project overview

* Purpose
* Installation
* Quick start
* Examples
* Philosophy

---

## Man Page

Reference documentation

* Synopsis
* Commands
* Files
* Environment
* Examples
* Exit codes

---

## Website

The EAWF website serves as the living documentation.

It may contain:

* Tutorials
* Screenshots
* Frequently Asked Questions
* Configuration examples
* Troubleshooting
* Release notes
* Known issues
* Future enhancements

---

# Error Handling

Applications should report problems in language users understand.

Avoid exposing raw command output unless it is genuinely useful.

The user should see results rather than internal implementation details.

---

# Design Philosophy

Good software should:

* Respect the operating system.
* Respect the user's configuration.
* Respect the user's time.
* Stay out of the way.
* Be reliable enough that users stop thinking about it.

---

# EAWF Motto

**Simple. Predictable. Configurable.**

Applications should be approachable for beginners while remaining powerful enough for experienced users.

---

# Release Criteria

A project may be declared Version 1.0 when it:

* Meets all functional requirements.
* Meets the EAWF Software Development Standard.
* Includes complete documentation.
* Includes installation and removal procedures.
* Has been tested through normal daily use.
* Is considered production ready.

Version 1.0 represents the beginning of long-term support, not the end of development.

Main Page

2026-07-16T22:54:39Z

Admin: /* About EAWF: */

= '''EAWF''' ''Empowering People, Solving Problems'' =
=== About Me/Us ===

''EAWF develops practical open-source software, documentation, and educational resources that help individuals and small organizations manage their own technology with confidence. Our projects focus on Linux administration, self-hosted infrastructure, Bitcoin, automation, and system management.'' 
We believe technology should be understandable, maintainable, and under the user's control.

'''Mission:'''
''To empower people by creating practical, reliable, and open tools that simplify technology, encourage self-reliance, and make complex systems easier to understand and manage.''

'''Vision:'''
''A world where individuals, families, educators, and small organizations can confidently build, manage, and own their digital infrastructure without unnecessary complexity or dependence on large vendors.''

'''Motto:''' ''Simple. Reliable. Open.''

'''Tagline:''' ''Empowering People. Solving Problems.''

=== Core Values ===
'''Simplicity''' 
We remove unnecessary complexity and strive to make every project easy to install, understand, and maintain.

'''Reliability''' 
Software should work consistently and predictably. Stability always comes before unnecessary features.

'''Openness''' 
Whenever practical, our work is open, documented, and available for others to learn from, improve, and build upon.

'''Education''' 
Knowledge should be shared. Every project is an opportunity to teach, document, and help others become more capable.

'''Privacy''' 
People should own their own data and control their own infrastructure whenever possible.

'''Independence''' 
Technology should reduce dependence on centralized services, not increase it.

'''Continuous Improvement''' 
Good software evolves through practical experience, thoughtful design, and feedback from real users.

=== What We Build ===
EAWF projects currently include:
* Linux system administration tools
* MediaWiki management utilities
* Bitcoin node and mining management
* Deployment and synchronization tools
* Server management utilities
* NFC and mobile automation projects
* Documentation and technical knowledge bases
* Educational resources and presentations
* Design Philosophy

'''Every EAWF project follows a common philosophy:'''
* Keep it simple.
* Solve one problem well.
* Automate repetitive work.
* Document everything.
* Prefer standards over cleverness.
* Make installation straightforward.
* Make maintenance predictable.
* Respect the user's data.
* Long-Term Goals
* Build a complete suite of open-source Linux administration tools.
* Simplify self-hosting for individuals and small organizations.
* Promote Bitcoin education and self-custody.
* Create documentation that remains useful for years.
* Build software that people can trust and maintain themselves.

=== The EAWF Promise ===
We build software we use ourselves. If it doesn't make our own work easier, it probably doesn't belong in an EAWF project.

Please read '''[[EAWFStandard|The EAWF Standard]]''' to obtain more understanding about us.

== Private Areas ==
* [[EAWF:Main|EAWF Business]]
* [[Private:Main|Holden Family]]

* [[EAWF:NewPage|New Page Template]]

{{Template:Copyright}}

EAWFStandard

2026-07-11T20:39:31Z

Admin:

{{Parent|Main_Page}}
== EAWF Software Development Standard v1.0 ==

== Purpose ==

The EAWF Software Development Standard defines the minimum quality, documentation, installation, and support requirements for all software released by EAWF.

The objective is simple:

* Deliver software that is useful, professional, predictable, easy to install, easy to maintain, and enjoyable to use.

* Every EAWF project should provide a consistent user interface and experience regardless of language, operating system, or application.

== EAWF Standards ==
* [[StandardsGeneral|General]]
** [[StandardsProjects|Projects]]
** [[StandardsScripts|Scripts]]
** [[StandardsCredits|Credits and Attribution]]
** [[StandardsDocs|Documentation Headers and Footers]]
== Programs/Scripts ==
=== BTC ===
* [[StandardsBTC|BTC]]
** [[StandardsBTCStartup|Startup]]
** [[StandardsBTCManagement|Management]]
** [[StandardsBTCProgram|BTC Program]]

=== Connect ===

* [[StandardsScripts|Scripts]]
** [[StandardsScripts|Scripts]]
** [[StandardsScripts|Scripts]]
** [[StandardsScripts|Scripts]]
** [[StandardsScripts|Scripts]]
** [[StandardsScripts|Scripts]]
** [[StandardsScripts|Scripts]]
** [[StandardsScripts|Scripts]]
** [[StandardsScripts|Scripts]]
** [[StandardsScripts|Scripts]]

== Core Philosophy ==

The EAWF Software Development Standard is based on the following principles:

* Follow established Linux conventions whenever practical.
* Keep programs simple.
* One tool should perform one primary task well.
* Do not expose implementation details to the user.
* Auto-detect sensible defaults whenever possible.
* Allow users to customize behavior without modifying program code.
* Never overwrite user configuration without permission.
* Documentation is part of the product.
* Installation and removal should be safe and straightforward.

---

=== Quality Standard ===

A version 1.0 release must satisfy the following requirements.

==== Functional: ====

* Stable operation
* No known functional defects
* Predictable behavior
* Clear error handling
* Professional command output

---

==== User Experience ====

* Clean command syntax
* Consistent help screens
* Quiet operation
* Friendly messages
* No unnecessary technical output
* Consistent formatting throughout the application

---

==== Installation ====

Every project should include:

* `.install.sh`
* `.uninstall.sh`
* README.md
* CHANGELOG.md
* LICENSE
* Man page
* Example configuration files

The installer should:

* Install safely
* Preserve existing user configuration
* Create missing configuration files from examples
* Verify prerequisites
* Report missing dependencies clearly

The uninstaller should remove the application while preserving user data unless explicitly requested otherwise.

== Linux Standards ==

* Programs should follow normal Linux conventions.

* Programs usually run from <code>/usr/local/bin</code>

* User Configuration: <code>~/.config/<project>/</code> e.g., <code>~/.config/connect/</code>

* Documentation Location: <code>/usr/local/share/doc/<project>/</code>

* Manual Pages: <code>/usr/local/share/man/man1/</code> e.g., <code>/usr/local/share/<project>/examples/</code>

* Logs: <code>~/.local/state/<project>/</code>
** Applications should create log directories only when logging is actually needed.

* Cache:
** Applications should '''**not**''' create cache directories unless there is a legitimate performance benefit.

* Avoid creating unnecessary files or directories "just in case."

* Configuration Philosophy: Separate configuration into logical responsibilities.

* Project Configuration: Contains definitions describing the project itself.

Example:
* Servers
* Hosts
* Network links
* Project mappings
* Deployment targets
Example:
connect.conf

* User Settings: Contains user preferences.

Example:

* Preferred editor
* Preferred file manager
* Color preferences
* Future display options

Example:

```
settings.conf
```

---

# Auto First

Every application should attempt to make intelligent default decisions.

Users should only need to customize behavior if they want something different.

Examples:

* Respect `$EDITOR`
* Auto-detect running file manager
* Automatically disable color when output is redirected
* Honor existing SSH configuration

---

# Customization

Power users should always be able to override automatic behavior.

Customization should be achieved through configuration files rather than modifying application code.

---

# Documentation

Every project should provide documentation at three levels.

## README

Project overview

* Purpose
* Installation
* Quick start
* Examples
* Philosophy

---

## Man Page

Reference documentation

* Synopsis
* Commands
* Files
* Environment
* Examples
* Exit codes

---

## Website

The EAWF website serves as the living documentation.

It may contain:

* Tutorials
* Screenshots
* Frequently Asked Questions
* Configuration examples
* Troubleshooting
* Release notes
* Known issues
* Future enhancements

---

# Error Handling

Applications should report problems in language users understand.

Avoid exposing raw command output unless it is genuinely useful.

The user should see results rather than internal implementation details.

---

# Design Philosophy

Good software should:

* Respect the operating system.
* Respect the user's configuration.
* Respect the user's time.
* Stay out of the way.
* Be reliable enough that users stop thinking about it.

---

# EAWF Motto

**Simple. Predictable. Configurable.**

Applications should be approachable for beginners while remaining powerful enough for experienced users.

---

# Release Criteria

A project may be declared Version 1.0 when it:

* Meets all functional requirements.
* Meets the EAWF Software Development Standard.
* Includes complete documentation.
* Includes installation and removal procedures.
* Has been tested through normal daily use.
* Is considered production ready.

Version 1.0 represents the beginning of long-term support, not the end of development.

EAWFStandard

2026-07-07T07:11:25Z

Admin:

{{Parent|Main_Page}}
== EAWF Software Development Standard v1.0 ==

== Purpose ==

The EAWF Software Development Standard defines the minimum quality, documentation, installation, and support requirements for all software released by EAWF.

The objective is simple:

* Deliver software that is professional, predictable, easy to install, easy to maintain, and enjoyable to use.

* Every EAWF project should provide a consistent experience regardless of language, operating system, or application.

---

== Core Philosophy ==

The EAWF Software Development Standard is based on the following principles:

* Follow established Linux conventions whenever practical.
* Keep programs simple.
* One tool should perform one primary task well.
* Do not expose implementation details to the user.
* Auto-detect sensible defaults whenever possible.
* Allow users to customize behavior without modifying program code.
* Never overwrite user configuration without permission.
* Documentation is part of the product.
* Installation and removal should be safe and straightforward.

---

=== Quality Standard ===

A version 1.0 release must satisfy the following requirements.

==== Functional: ====

* Stable operation
* No known functional defects
* Predictable behavior
* Clear error handling
* Professional command output

---

==== User Experience ====

* Clean command syntax
* Consistent help screens
* Quiet operation
* Friendly messages
* No unnecessary technical output
* Consistent formatting throughout the application

---

==== Installation ====

Every project should include:

* `.install.sh`
* `.uninstall.sh`
* README.md
* CHANGELOG.md
* LICENSE
* Man page
* Example configuration files

The installer should:

* Install safely
* Preserve existing user configuration
* Create missing configuration files from examples
* Verify prerequisites
* Report missing dependencies clearly

The uninstaller should remove the application while preserving user data unless explicitly requested otherwise.

== Linux Standards ==

* Programs should follow normal Linux conventions.

* Programs usually run from <code>/usr/local/bin</code>

* User Configuration: <code>~/.config/<project>/</code> e.g., <code>~/.config/connect/</code>

* Documentation Location: <code>/usr/local/share/doc/<project>/</code>

* Manual Pages: <code>/usr/local/share/man/man1/</code> e.g., <code>/usr/local/share/<project>/examples/</code>

* Logs: <code>~/.local/state/<project>/</code>
** Applications should create log directories only when logging is actually needed.

* Cache:
** Applications should '''**not**''' create cache directories unless there is a legitimate performance benefit.

* Avoid creating unnecessary files or directories "just in case."

* Configuration Philosophy: Separate configuration into logical responsibilities.

* Project Configuration: Contains definitions describing the project itself.

Example:
* Servers
* Hosts
* Network links
* Project mappings
* Deployment targets
Example:
connect.conf

* User Settings: Contains user preferences.

Example:

* Preferred editor
* Preferred file manager
* Color preferences
* Future display options

Example:

```
settings.conf
```

---

# Auto First

Every application should attempt to make intelligent default decisions.

Users should only need to customize behavior if they want something different.

Examples:

* Respect `$EDITOR`
* Auto-detect running file manager
* Automatically disable color when output is redirected
* Honor existing SSH configuration

---

# Customization

Power users should always be able to override automatic behavior.

Customization should be achieved through configuration files rather than modifying application code.

---

# Documentation

Every project should provide documentation at three levels.

## README

Project overview

* Purpose
* Installation
* Quick start
* Examples
* Philosophy

---

## Man Page

Reference documentation

* Synopsis
* Commands
* Files
* Environment
* Examples
* Exit codes

---

## Website

The EAWF website serves as the living documentation.

It may contain:

* Tutorials
* Screenshots
* Frequently Asked Questions
* Configuration examples
* Troubleshooting
* Release notes
* Known issues
* Future enhancements

---

# Error Handling

Applications should report problems in language users understand.

Avoid exposing raw command output unless it is genuinely useful.

The user should see results rather than internal implementation details.

---

# Design Philosophy

Good software should:

* Respect the operating system.
* Respect the user's configuration.
* Respect the user's time.
* Stay out of the way.
* Be reliable enough that users stop thinking about it.

---

# EAWF Motto

**Simple. Predictable. Configurable.**

Applications should be approachable for beginners while remaining powerful enough for experienced users.

---

# Release Criteria

A project may be declared Version 1.0 when it:

* Meets all functional requirements.
* Meets the EAWF Software Development Standard.
* Includes complete documentation.
* Includes installation and removal procedures.
* Has been tested through normal daily use.
* Is considered production ready.

Version 1.0 represents the beginning of long-term support, not the end of development.

Main Page

2026-07-07T06:48:48Z

Admin: /* The EAWF Promise */

= '''EAWF''' ''Empowering People, Solving Problems'' =
=== About EAWF: ===

''EAWF develops practical open-source software, documentation, and educational resources that help individuals and small organizations manage their own technology with confidence. Our projects focus on Linux administration, self-hosted infrastructure, Bitcoin, automation, and system management.'' 
We believe technology should be understandable, maintainable, and under the user's control.

'''Mission:'''
''To empower people by creating practical, reliable, and open tools that simplify technology, encourage self-reliance, and make complex systems easier to understand and manage.''

'''Vision:'''
''A world where individuals, families, educators, and small organizations can confidently build, manage, and own their digital infrastructure without unnecessary complexity or dependence on large vendors.''

'''Motto:''' ''Simple. Reliable. Open.''

'''Tagline:''' ''Empowering People. Solving Problems.''

=== Core Values ===
'''Simplicity''' 
We remove unnecessary complexity and strive to make every project easy to install, understand, and maintain.

'''Reliability''' 
Software should work consistently and predictably. Stability always comes before unnecessary features.

'''Openness''' 
Whenever practical, our work is open, documented, and available for others to learn from, improve, and build upon.

'''Education''' 
Knowledge should be shared. Every project is an opportunity to teach, document, and help others become more capable.

'''Privacy''' 
People should own their own data and control their own infrastructure whenever possible.

'''Independence''' 
Technology should reduce dependence on centralized services, not increase it.

'''Continuous Improvement''' 
Good software evolves through practical experience, thoughtful design, and feedback from real users.

=== What We Build ===
EAWF projects currently include:
* Linux system administration tools
* MediaWiki management utilities
* Bitcoin node and mining management
* Deployment and synchronization tools
* Server management utilities
* NFC and mobile automation projects
* Documentation and technical knowledge bases
* Educational resources and presentations
* Design Philosophy

'''Every EAWF project follows a common philosophy:'''
* Keep it simple.
* Solve one problem well.
* Automate repetitive work.
* Document everything.
* Prefer standards over cleverness.
* Make installation straightforward.
* Make maintenance predictable.
* Respect the user's data.
* Long-Term Goals
* Build a complete suite of open-source Linux administration tools.
* Simplify self-hosting for individuals and small organizations.
* Promote Bitcoin education and self-custody.
* Create documentation that remains useful for years.
* Build software that people can trust and maintain themselves.

=== The EAWF Promise ===
We build software we use ourselves. If it doesn't make our own work easier, it probably doesn't belong in an EAWF project.

Please read '''[[EAWFStandard|The EAWF Standard]]''' to obtain more understanding about us.

== Private Areas ==
* [[EAWF:Main|Business]]
* [[Private:Main|Holden Stuff]]

* [[EAWF:NewPage|New Page]]

{{Template:Copyright}}

Main Page

2026-07-06T21:41:47Z

Admin: /* Private Areas */

= '''EAWF''' ''Empowering People, Solving Problems'' =
=== About EAWF: ===

''EAWF develops practical open-source software, documentation, and educational resources that help individuals and small organizations manage their own technology with confidence. Our projects focus on Linux administration, self-hosted infrastructure, Bitcoin, automation, and system management.'' 
We believe technology should be understandable, maintainable, and under the user's control.

'''Mission:'''
''To empower people by creating practical, reliable, and open tools that simplify technology, encourage self-reliance, and make complex systems easier to understand and manage.''

'''Vision:'''
''A world where individuals, families, educators, and small organizations can confidently build, manage, and own their digital infrastructure without unnecessary complexity or dependence on large vendors.''

'''Motto:''' ''Simple. Reliable. Open.''

'''Tagline:''' ''Empowering People. Solving Problems.''

=== Core Values ===
'''Simplicity''' 
We remove unnecessary complexity and strive to make every project easy to install, understand, and maintain.

'''Reliability''' 
Software should work consistently and predictably. Stability always comes before unnecessary features.

'''Openness''' 
Whenever practical, our work is open, documented, and available for others to learn from, improve, and build upon.

'''Education''' 
Knowledge should be shared. Every project is an opportunity to teach, document, and help others become more capable.

'''Privacy''' 
People should own their own data and control their own infrastructure whenever possible.

'''Independence''' 
Technology should reduce dependence on centralized services, not increase it.

'''Continuous Improvement''' 
Good software evolves through practical experience, thoughtful design, and feedback from real users.

=== What We Build ===
EAWF projects currently include:
* Linux system administration tools
* MediaWiki management utilities
* Bitcoin node and mining management
* Deployment and synchronization tools
* Server management utilities
* NFC and mobile automation projects
* Documentation and technical knowledge bases
* Educational resources and presentations
* Design Philosophy

'''Every EAWF project follows a common philosophy:'''
* Keep it simple.
* Solve one problem well.
* Automate repetitive work.
* Document everything.
* Prefer standards over cleverness.
* Make installation straightforward.
* Make maintenance predictable.
* Respect the user's data.
* Long-Term Goals
* Build a complete suite of open-source Linux administration tools.
* Simplify self-hosting for individuals and small organizations.
* Promote Bitcoin education and self-custody.
* Create documentation that remains useful for years.
* Build software that people can trust and maintain themselves.

=== The EAWF Promise ===
We build software we use ourselves. If it doesn't make our own work easier, it probably doesn't belong in an EAWF project.

'''[[EAWFStandard|The EAWF Standard]]'''
== Private Areas ==
* [[EAWF:Main|Business]]
* [[Private:Main|Holden Stuff]]

* [[EAWF:NewPage|New Page]]

{{Template:Copyright}}

Main Page

2026-07-06T21:40:47Z

Admin:

= '''EAWF''' ''Empowering People, Solving Problems'' =
=== About EAWF: ===

''EAWF develops practical open-source software, documentation, and educational resources that help individuals and small organizations manage their own technology with confidence. Our projects focus on Linux administration, self-hosted infrastructure, Bitcoin, automation, and system management.'' 
We believe technology should be understandable, maintainable, and under the user's control.

'''Mission:'''
''To empower people by creating practical, reliable, and open tools that simplify technology, encourage self-reliance, and make complex systems easier to understand and manage.''

'''Vision:'''
''A world where individuals, families, educators, and small organizations can confidently build, manage, and own their digital infrastructure without unnecessary complexity or dependence on large vendors.''

'''Motto:''' ''Simple. Reliable. Open.''

'''Tagline:''' ''Empowering People. Solving Problems.''

=== Core Values ===
'''Simplicity''' 
We remove unnecessary complexity and strive to make every project easy to install, understand, and maintain.

'''Reliability''' 
Software should work consistently and predictably. Stability always comes before unnecessary features.

'''Openness''' 
Whenever practical, our work is open, documented, and available for others to learn from, improve, and build upon.

'''Education''' 
Knowledge should be shared. Every project is an opportunity to teach, document, and help others become more capable.

'''Privacy''' 
People should own their own data and control their own infrastructure whenever possible.

'''Independence''' 
Technology should reduce dependence on centralized services, not increase it.

'''Continuous Improvement''' 
Good software evolves through practical experience, thoughtful design, and feedback from real users.

=== What We Build ===
EAWF projects currently include:
* Linux system administration tools
* MediaWiki management utilities
* Bitcoin node and mining management
* Deployment and synchronization tools
* Server management utilities
* NFC and mobile automation projects
* Documentation and technical knowledge bases
* Educational resources and presentations
* Design Philosophy

'''Every EAWF project follows a common philosophy:'''
* Keep it simple.
* Solve one problem well.
* Automate repetitive work.
* Document everything.
* Prefer standards over cleverness.
* Make installation straightforward.
* Make maintenance predictable.
* Respect the user's data.
* Long-Term Goals
* Build a complete suite of open-source Linux administration tools.
* Simplify self-hosting for individuals and small organizations.
* Promote Bitcoin education and self-custody.
* Create documentation that remains useful for years.
* Build software that people can trust and maintain themselves.

=== The EAWF Promise ===
We build software we use ourselves. If it doesn't make our own work easier, it probably doesn't belong in an EAWF project.

'''[[EAWFStandard|The EAWF Standard]]'''
== Private Areas ==
* [[EAWF:Main|Business]]
* [[Private:Main|Holden Stuff]]
* EAWF:NewPage

{{Template:Copyright}}

MediaWiki:Sidebar

2026-07-06T21:39:58Z

Admin:

MediaWiki:Sidebar

2026-07-06T21:15:51Z

Admin:

MediaWiki:Sidebar

2026-07-06T21:14:11Z

Admin:

MediaWiki:Sidebar

2026-07-06T21:08:08Z

Main Page

2026-07-06T20:59:38Z

Admin:

= '''EAWF''' ''Empowering People, Solving Problems'' =
=== About EAWF: ===

''EAWF develops practical open-source software, documentation, and educational resources that help individuals and small organizations manage their own technology with confidence. Our projects focus on Linux administration, self-hosted infrastructure, Bitcoin, automation, and system management.'' 
We believe technology should be understandable, maintainable, and under the user's control.

'''Mission:'''
''To empower people by creating practical, reliable, and open tools that simplify technology, encourage self-reliance, and make complex systems easier to understand and manage.''

'''Vision:'''
''A world where individuals, families, educators, and small organizations can confidently build, manage, and own their digital infrastructure without unnecessary complexity or dependence on large vendors.''

'''Motto:''' ''Simple. Reliable. Open.''

'''Tagline:''' ''Empowering People. Solving Problems.''

=== Core Values ===
'''Simplicity''' 
We remove unnecessary complexity and strive to make every project easy to install, understand, and maintain.

'''Reliability''' 
Software should work consistently and predictably. Stability always comes before unnecessary features.

'''Openness''' 
Whenever practical, our work is open, documented, and available for others to learn from, improve, and build upon.

'''Education''' 
Knowledge should be shared. Every project is an opportunity to teach, document, and help others become more capable.

'''Privacy''' 
People should own their own data and control their own infrastructure whenever possible.

'''Independence''' 
Technology should reduce dependence on centralized services, not increase it.

'''Continuous Improvement''' 
Good software evolves through practical experience, thoughtful design, and feedback from real users.

=== What We Build ===
EAWF projects currently include:
* Linux system administration tools
* MediaWiki management utilities
* Bitcoin node and mining management
* Deployment and synchronization tools
* Server management utilities
* NFC and mobile automation projects
* Documentation and technical knowledge bases
* Educational resources and presentations
* Design Philosophy

'''Every EAWF project follows a common philosophy:'''
* Keep it simple.
* Solve one problem well.
* Automate repetitive work.
* Document everything.
* Prefer standards over cleverness.
* Make installation straightforward.
* Make maintenance predictable.
* Respect the user's data.
* Long-Term Goals
* Build a complete suite of open-source Linux administration tools.
* Simplify self-hosting for individuals and small organizations.
* Promote Bitcoin education and self-custody.
* Create documentation that remains useful for years.
* Build software that people can trust and maintain themselves.

=== The EAWF Promise ===
We build software we use ourselves. If it doesn't make our own work easier, it probably doesn't belong in an EAWF project.

'''[[EAWFStandard|The EAWF Standard]]'''
== Private Areas ==
* [[EAWF:Main|Business]]
* [[Private:Main|Holden Stuff]]

{{Template:Copyright}}

About

2026-07-06T20:56:41Z

Admin: Replaced content with "{{Parent|Main_Page}}"

About

2026-07-06T20:55:40Z

Admin: Admin moved page EAWF:About to About over redirect

{{Parent|Main_Page}}
= '''EAWF''' ''Empowering People, Solving Problems'' =
=== About EAWF: ===

''EAWF develops practical open-source software, documentation, and educational resources that help individuals and small organizations manage their own technology with confidence. Our projects focus on Linux administration, self-hosted infrastructure, Bitcoin, automation, and system management.'' 
We believe technology should be understandable, maintainable, and under the user's control.

'''Mission:'''
''To empower people by creating practical, reliable, and open tools that simplify technology, encourage self-reliance, and make complex systems easier to understand and manage.''

'''Vision:'''
''A world where individuals, families, educators, and small organizations can confidently build, manage, and own their digital infrastructure without unnecessary complexity or dependence on large vendors.''

'''Motto:''' ''Simple. Reliable. Open.''

'''Tagline:''' ''Empowering People. Solving Problems.''

=== Core Values ===
'''Simplicity''' 
We remove unnecessary complexity and strive to make every project easy to install, understand, and maintain.

'''Reliability''' 
Software should work consistently and predictably. Stability always comes before unnecessary features.

'''Openness''' 
Whenever practical, our work is open, documented, and available for others to learn from, improve, and build upon.

'''Education''' 
Knowledge should be shared. Every project is an opportunity to teach, document, and help others become more capable.

'''Privacy''' 
People should own their own data and control their own infrastructure whenever possible.

'''Independence''' 
Technology should reduce dependence on centralized services, not increase it.

'''Continuous Improvement''' 
Good software evolves through practical experience, thoughtful design, and feedback from real users.

=== What We Build ===
EAWF projects currently include:
* Linux system administration tools
* MediaWiki management utilities
* Bitcoin node and mining management
* Deployment and synchronization tools
* Server management utilities
* NFC and mobile automation projects
* Documentation and technical knowledge bases
* Educational resources and presentations
* Design Philosophy

'''Every EAWF project follows a common philosophy:'''
* Keep it simple.
* Solve one problem well.
* Automate repetitive work.
* Document everything.
* Prefer standards over cleverness.
* Make installation straightforward.
* Make maintenance predictable.
* Respect the user's data.
* Long-Term Goals
* Build a complete suite of open-source Linux administration tools.
* Simplify self-hosting for individuals and small organizations.
* Promote Bitcoin education and self-custody.
* Create documentation that remains useful for years.
* Build software that people can trust and maintain themselves.

=== The EAWF Promise ===
We build software we use ourselves. If it doesn't make our own work easier, it probably doesn't belong in an EAWF project.

Main Page

2026-07-06T20:55:26Z

Admin:

= '''EAWF Document Repository''' ''Empowering People, Solving Problems'' =
'''[[EAWFStandard|The EAWF Standard]]'''
== EAWF Documentation Project ==
[[EAWF:About|About EAWF]]

== Private Areas ==
* [[EAWF:Main|Business]]
* [[Private:Main|Holden Stuff]]

{{Template:Copyright}}

Main Page

2026-07-06T20:54:08Z

Admin:

Main Page

2026-07-06T20:52:33Z

Admin: /* Drafts */

= '''EAWF Document Repository''' ''Empowering People, Solving Problems'' =
'''[[EAWFStandard|The EAWF Standard]]'''

== Private Areas ==
* [[EAWF:Main|Business]]
* [[Private:Main|Holden Stuff]]
== Drafts ==
* [[EAWF:Unsorted Notes]] - Stuff that is more important than a scratchpad.
* [[EAWF:Scratchpad]] - Just what it says. Just a place to jot stuff down before it gets categorized into a Page.

== Wiki Utils ==
*[[NewPage]] - Create a new page...don't forget Namespace
*[[Backup]]
*[[Sandbox]]

{{Template:Copyright}}

NewPage

2026-07-06T20:51:22Z

Admin: Admin moved page NewPage to EAWF:NewPage

#REDIRECT [[EAWF:NewPage]]

Unsorted Notes

2026-07-06T20:51:02Z

Admin: Admin moved page Unsorted Notes to EAWF:Unsorted Notes

#REDIRECT [[EAWF:Unsorted Notes]]

Scratchpad

2026-07-06T20:50:40Z

Admin: Admin moved page Scratchpad to EAWF:Scratchpad

#REDIRECT [[EAWF:Scratchpad]]

Main Page

2026-07-06T19:48:48Z

Admin:

= '''EAWF Document Repository''' ''Empowering People, Solving Problems'' =
'''[[EAWFStandard|The EAWF Standard]]'''

== Private Areas ==
* [[EAWF:Main|Business]]
* [[Private:Main|Holden Stuff]]
== Drafts ==
* [[Scratchpad]] - Just what it says. Just a place to jot stuff down before it gets categorized into a Page.
* [[Unsorted Notes]] - Stuff that is more important than a scratchpad.

== Wiki Utils ==
*[[NewPage]] - Create a new page...don't forget Namespace
*[[Backup]]
*[[Sandbox]]

{{Template:Copyright}}

EAWFStandard

2026-07-06T19:29:19Z

Admin: Admin moved page EAWF:EAWFStandard to EAWFStandard over redirect

{{Parent|Main_Page}}
== EAWF Software Development Standard v1.0 ==

== Purpose ==

The EAWF Software Development Standard defines the minimum quality, documentation, installation, and support requirements for all software released by EAWF.

The objective is simple:

* Deliver software that is professional, predictable, easy to install, easy to maintain, and enjoyable to use.

* Every EAWF project should provide a consistent experience regardless of language, operating system, or application.

---

== Core Philosophy ==

The EAWF Software Development Standard is based on the following principles:

* Follow established Linux conventions whenever practical.
* Keep programs simple.
* One tool should perform one primary task well.
* Do not expose implementation details to the user.
* Auto-detect sensible defaults whenever possible.
* Allow users to customize behavior without modifying program code.
* Never overwrite user configuration without permission.
* Documentation is part of the product.
* Installation and removal should be safe and straightforward.

---

=== Quality Standard ===

A version 1.0 release must satisfy the following requirements.

==== Functional: ====

* Stable operation
* No known functional defects
* Predictable behavior
* Clear error handling
* Professional command output

---

==== User Experience ====

* Clean command syntax
* Consistent help screens
* Quiet operation
* Friendly messages
* No unnecessary technical output
* Consistent formatting throughout the application

---

==== Installation ====

Every project should include:

* `.install.sh`
* `.uninstall.sh`
* README.md
* CHANGELOG.md
* LICENSE
* Man page
* Example configuration files

The installer should:

* Install safely
* Preserve existing user configuration
* Create missing configuration files from examples
* Verify prerequisites
* Report missing dependencies clearly

The uninstaller should remove the application while preserving user data unless explicitly requested otherwise.

---

# Linux Standards

Programs should follow normal Linux conventions.

## Program

```
/usr/local/bin
```

## User Configuration

```
~/.config/<project>/
```

Example:

```
~/.config/connect/
```

---

## Documentation

```
/usr/local/share/doc/<project>/
```

---

## Manual Pages

```
/usr/local/share/man/man1/
```

---

## Examples

```
/usr/local/share/<project>/examples/
```

---

## Logs

When required:

```
~/.local/state/<project>/
```

Applications should create log directories only when logging is actually needed.

---

## Cache

Applications should **not** create cache directories unless there is a legitimate performance benefit.

Avoid creating unnecessary files or directories "just in case."

---

# Configuration Philosophy

Separate configuration into logical responsibilities.

## Project Configuration

Contains definitions describing the project itself.

Example:

* Servers
* Hosts
* Network links
* Project mappings
* Deployment targets

Example:

```
connect.conf
```

---

## User Settings

Contains user preferences.

Example:

* Preferred editor
* Preferred file manager
* Color preferences
* Future display options

Example:

```
settings.conf
```

---

# Auto First

Every application should attempt to make intelligent default decisions.

Users should only need to customize behavior if they want something different.

Examples:

* Respect `$EDITOR`
* Auto-detect running file manager
* Automatically disable color when output is redirected
* Honor existing SSH configuration

---

# Customization

Power users should always be able to override automatic behavior.

Customization should be achieved through configuration files rather than modifying application code.

---

# Documentation

Every project should provide documentation at three levels.

## README

Project overview

* Purpose
* Installation
* Quick start
* Examples
* Philosophy

---

## Man Page

Reference documentation

* Synopsis
* Commands
* Files
* Environment
* Examples
* Exit codes

---

## Website

The EAWF website serves as the living documentation.

It may contain:

* Tutorials
* Screenshots
* Frequently Asked Questions
* Configuration examples
* Troubleshooting
* Release notes
* Known issues
* Future enhancements

---

# Error Handling

Applications should report problems in language users understand.

Avoid exposing raw command output unless it is genuinely useful.

The user should see results rather than internal implementation details.

---

# Design Philosophy

Good software should:

* Respect the operating system.
* Respect the user's configuration.
* Respect the user's time.
* Stay out of the way.
* Be reliable enough that users stop thinking about it.

---

# EAWF Motto

**Simple. Predictable. Configurable.**

Applications should be approachable for beginners while remaining powerful enough for experienced users.

---

# Release Criteria

A project may be declared Version 1.0 when it:

* Meets all functional requirements.
* Meets the EAWF Software Development Standard.
* Includes complete documentation.
* Includes installation and removal procedures.
* Has been tested through normal daily use.
* Is considered production ready.

Version 1.0 represents the beginning of long-term support, not the end of development.

Main Page

2026-07-06T19:28:44Z

Admin: /* EAWFEmpowering People, Solving Problems */

= '''EAWF''' ''Empowering People, Solving Problems'' =
'''[[EAWFStandard|The EAWF Standard]]'''
== Private Areas ==
* [[EAWF:Main|EAWF Workspace]]
* [[Private:Main|Private Workspace]]

== Projects In Progress ==
* [[EAWF:Btc|BTC Operations Manager]] - Bitcoin Node w/Mining Services
* [[EAWF:Mmgr|Mail Manager]] Postfix Mail Management System
* [[EAWF:Mwmgr|MediaWiki Manager]] - MediaWiki Management Tool
* [[EAWF:Wgmgr|Wireguard Manager]] - Manage Wireguard Connections
* [[EAWF:Audit|Audit]] - Rocky9 Server Auditor
* [[EAWF:ServerBox|Server In A Box]] - Web, eMail, Wiki Server System for the masses

'''[[Private:Personal|Personal Projects]]'''

== EAWF Documentation Project ==
[[EAWF:About|About EAWF]]

[[Squirrel|Squirrel Habitat]] - ''Ideas worth keeping, but not necessarily worth chasing today.''

[[Code Library]] - Code Snippets for all situations

[[EAWF|EAWF Business Management System]]

[[KBDocs|Knowledge Base]] - The EAWF Web Site Knowledge Base/Repository of Important EAWF Things

[[Bitcoin|Bitcoin Tips & Tricks]]

[[Git|GitHub Repositories]] - Making MY stuff MINE!

[[BizPlan|Business Plan Templates]] - {{Book
|title=Business Plan Builder
|author=Jian
}}

=== Web Site Administration ===
*Policies & Procedures for the web sites.
[[Apache2|Hosting]]

[[php8|PHP Programming]]

[[wiki|MediaWiki]]

[[RoundCube|Web Mail]]

[[osTicket|Work Tickets]]

=== Misc Stuff ===
* [[OfficeStuff|Stuff I need for the Office]]
* [[Private:Side Hustles|Side Hustles]] - Stuff we want to look into insofar as making some extra money
* [[Private:376|376 Spreading Oak Lane]]

== Drafts ==
* [[Scratchpad]] - Just what it says. Just a place to jot stuff down before it gets categorized into a Page.
* [[Unsorted Notes]] - Stuff that is more important than a scratchpad.

== Wiki Utils ==
*[[NewPage]] - Create a new page...don't forget Namespace
*[[Backup]]
*[[Sandbox]]

{{Template:Copyright}}

Main Page

2026-07-06T19:25:00Z

Admin:

= '''EAWF''' ''Empowering People, Solving Problems'' =
'''[[EAWF:EAWFStandard|The EAWF Standard]]'''
== Private Areas ==
* [[EAWF:Main|EAWF Workspace]]
* [[Private:Main|Private Workspace]]

== Projects In Progress ==
* [[EAWF:Btc|BTC Operations Manager]] - Bitcoin Node w/Mining Services
* [[EAWF:Mmgr|Mail Manager]] Postfix Mail Management System
* [[EAWF:Mwmgr|MediaWiki Manager]] - MediaWiki Management Tool
* [[EAWF:Wgmgr|Wireguard Manager]] - Manage Wireguard Connections
* [[EAWF:Audit|Audit]] - Rocky9 Server Auditor
* [[EAWF:ServerBox|Server In A Box]] - Web, eMail, Wiki Server System for the masses

'''[[Private:Personal|Personal Projects]]'''

== EAWF Documentation Project ==
[[EAWF:About|About EAWF]]

[[Squirrel|Squirrel Habitat]] - ''Ideas worth keeping, but not necessarily worth chasing today.''

[[Code Library]] - Code Snippets for all situations

[[EAWF|EAWF Business Management System]]

[[KBDocs|Knowledge Base]] - The EAWF Web Site Knowledge Base/Repository of Important EAWF Things

[[Bitcoin|Bitcoin Tips & Tricks]]

[[Git|GitHub Repositories]] - Making MY stuff MINE!

[[BizPlan|Business Plan Templates]] - {{Book
|title=Business Plan Builder
|author=Jian
}}

=== Web Site Administration ===
*Policies & Procedures for the web sites.
[[Apache2|Hosting]]

[[php8|PHP Programming]]

[[wiki|MediaWiki]]

[[RoundCube|Web Mail]]

[[osTicket|Work Tickets]]

=== Misc Stuff ===
* [[OfficeStuff|Stuff I need for the Office]]
* [[Private:Side Hustles|Side Hustles]] - Stuff we want to look into insofar as making some extra money
* [[Private:376|376 Spreading Oak Lane]]

== Drafts ==
* [[Scratchpad]] - Just what it says. Just a place to jot stuff down before it gets categorized into a Page.
* [[Unsorted Notes]] - Stuff that is more important than a scratchpad.

== Wiki Utils ==
*[[NewPage]] - Create a new page...don't forget Namespace
*[[Backup]]
*[[Sandbox]]

{{Template:Copyright}}

Main Page

2026-07-06T17:57:59Z

Admin: /* Projects In Progress */

= '''EAWF''' ''Empowering People, Solving Problems'' =
'''[[EAWF:EAWFStandard|The EAWF Standard]]'''
== Projects In Progress ==
* [[EAWF:Btc|BTC Operations Manager]] - Bitcoin Node w/Mining Services
* [[EAWF:Mmgr|Mail Manager]] Postfix Mail Management System
* [[EAWF:Mwmgr|MediaWiki Manager]] - MediaWiki Management Tool
* [[EAWF:Wgmgr|Wireguard Manager]] - Manage Wireguard Connections
* [[EAWF:Audit|Audit]] - Rocky9 Server Auditor
* [[EAWF:ServerBox|Server In A Box]] - Web, eMail, Wiki Server System for the masses

'''[[Private:Personal|Personal Projects]]'''

== EAWF Documentation Project ==
[[EAWF:About|About EAWF]]

[[Squirrel|Squirrel Habitat]] - ''Ideas worth keeping, but not necessarily worth chasing today.''

[[Code Library]] - Code Snippets for all situations

[[EAWF|EAWF Business Management System]]

[[KBDocs|Knowledge Base]] - The EAWF Web Site Knowledge Base/Repository of Important EAWF Things

[[Bitcoin|Bitcoin Tips & Tricks]]

[[Git|GitHub Repositories]] - Making MY stuff MINE!

[[BizPlan|Business Plan Templates]] - {{Book
|title=Business Plan Builder
|author=Jian
}}

=== Web Site Administration ===
*Policies & Procedures for the web sites.
[[Apache2|Hosting]]

[[php8|PHP Programming]]

[[wiki|MediaWiki]]

[[RoundCube|Web Mail]]

[[osTicket|Work Tickets]]

=== Misc Stuff ===
* [[OfficeStuff|Stuff I need for the Office]]
* [[Private:Side Hustles|Side Hustles]] - Stuff we want to look into insofar as making some extra money
* [[Private:376|376 Spreading Oak Lane]]

== Drafts ==
* [[Scratchpad]] - Just what it says. Just a place to jot stuff down before it gets categorized into a Page.
* [[Unsorted Notes]] - Stuff that is more important than a scratchpad.

== Wiki Utils ==
*[[NewPage]] - Create a new page...don't forget Namespace
*[[Backup]]
*[[Sandbox]]

{{Template:Copyright}}

Main Page

2026-07-06T17:56:47Z

Admin: /* Projects In Progress */

= '''EAWF''' ''Empowering People, Solving Problems'' =
'''[[EAWF:EAWFStandard|The EAWF Standard]]'''
== Projects In Progress ==
* [[EAWF:Btc|BTC Operations Manager]] - Bitcoin Node w/Mining Services
* [[EAWF:Mmgr|Mail Manager]] Postfix Mail Management System
* [[EAWF:Mwmgr|MediaWiki Manager]] - MediaWiki Management Tool
* [[EAWF:Wgmgr|Wireguard Manager]] - Manage Wireguard Connections
* [[EAWF:Audit|Audit]] - Rocky9 Server Auditor
* [[Server|Server In A Box]] - Web, eMail, Wiki Server System for the masses

'''[[Private:Personal|Personal Projects]]'''

== EAWF Documentation Project ==
[[EAWF:About|About EAWF]]

[[Squirrel|Squirrel Habitat]] - ''Ideas worth keeping, but not necessarily worth chasing today.''

[[Code Library]] - Code Snippets for all situations

[[EAWF|EAWF Business Management System]]

[[KBDocs|Knowledge Base]] - The EAWF Web Site Knowledge Base/Repository of Important EAWF Things

[[Bitcoin|Bitcoin Tips & Tricks]]

[[Git|GitHub Repositories]] - Making MY stuff MINE!

[[BizPlan|Business Plan Templates]] - {{Book
|title=Business Plan Builder
|author=Jian
}}

=== Web Site Administration ===
*Policies & Procedures for the web sites.
[[Apache2|Hosting]]

[[php8|PHP Programming]]

[[wiki|MediaWiki]]

[[RoundCube|Web Mail]]

[[osTicket|Work Tickets]]

=== Misc Stuff ===
* [[OfficeStuff|Stuff I need for the Office]]
* [[Private:Side Hustles|Side Hustles]] - Stuff we want to look into insofar as making some extra money
* [[Private:376|376 Spreading Oak Lane]]

== Drafts ==
* [[Scratchpad]] - Just what it says. Just a place to jot stuff down before it gets categorized into a Page.
* [[Unsorted Notes]] - Stuff that is more important than a scratchpad.

== Wiki Utils ==
*[[NewPage]] - Create a new page...don't forget Namespace
*[[Backup]]
*[[Sandbox]]

{{Template:Copyright}}

Main Page

2026-07-06T17:55:25Z

Admin: /* EAWFEmpowering People, Solving Problems */

= '''EAWF''' ''Empowering People, Solving Problems'' =
'''[[EAWF:EAWFStandard|The EAWF Standard]]'''
== Projects In Progress ==
* [[EAWF:Btc|BTC Operations Manager]] - Bitcoin Node w/Mining Services
* [[EAWF:Mmgr|Mail Manager]] Postfix Mail Management System
* [[EAWF:Mwmgr|MediaWiki Manager]] - MediaWiki Management Tool
* [[EAWF:Wgmgr|Wireguard Manager]] - Manage Wireguard Connections
* [[EAWF:Audit|Audit]] - Rocky9 Server Auditor
* [[EAWF:Server|Server In A Box]] - Web, eMail, Wiki Server System for the masses

'''[[Private:Personal|Personal Projects]]'''

== EAWF Documentation Project ==
[[EAWF:About|About EAWF]]

[[Squirrel|Squirrel Habitat]] - ''Ideas worth keeping, but not necessarily worth chasing today.''

[[Code Library]] - Code Snippets for all situations

[[EAWF|EAWF Business Management System]]

[[KBDocs|Knowledge Base]] - The EAWF Web Site Knowledge Base/Repository of Important EAWF Things

[[Bitcoin|Bitcoin Tips & Tricks]]

[[Git|GitHub Repositories]] - Making MY stuff MINE!

[[BizPlan|Business Plan Templates]] - {{Book
|title=Business Plan Builder
|author=Jian
}}

=== Web Site Administration ===
*Policies & Procedures for the web sites.
[[Apache2|Hosting]]

[[php8|PHP Programming]]

[[wiki|MediaWiki]]

[[RoundCube|Web Mail]]

[[osTicket|Work Tickets]]

=== Misc Stuff ===
* [[OfficeStuff|Stuff I need for the Office]]
* [[Private:Side Hustles|Side Hustles]] - Stuff we want to look into insofar as making some extra money
* [[Private:376|376 Spreading Oak Lane]]

== Drafts ==
* [[Scratchpad]] - Just what it says. Just a place to jot stuff down before it gets categorized into a Page.
* [[Unsorted Notes]] - Stuff that is more important than a scratchpad.

== Wiki Utils ==
*[[NewPage]] - Create a new page...don't forget Namespace
*[[Backup]]
*[[Sandbox]]

{{Template:Copyright}}

Main Page

2026-07-06T17:43:20Z

Admin: /* EAWF Documentation Project */

= '''EAWF''' ''Empowering People, Solving Problems'' =
'''[[EAWF:EAWFStandard|The EAWF Standard]]'''
== Projects In Progress ==
* [[EAWF:Btc|BTC Operations Manager]] - Bitcoin Node w/Mining Services
* [[EAWF:Mmgr|Mail Manager]] Postfix Mail Management System
* [[EAWF:Mwmgr|MediaWiki Manager]] - MediaWiki Management Tool
* [[EAWF:Wgmgr|Wireguard Manager]] - Manage Wireguard Connections
* [[EAWF:Audit]] - Rocky9 Server Auditor
* [[EAWF:Server|Server In A Box]] - Web, eMail, Wiki Server System for the masses

'''[[Private:Personal|Personal Projects]]'''

== EAWF Documentation Project ==
[[EAWF:About|About EAWF]]

[[Squirrel|Squirrel Habitat]] - ''Ideas worth keeping, but not necessarily worth chasing today.''

[[Code Library]] - Code Snippets for all situations

[[EAWF|EAWF Business Management System]]

[[KBDocs|Knowledge Base]] - The EAWF Web Site Knowledge Base/Repository of Important EAWF Things

[[Bitcoin|Bitcoin Tips & Tricks]]

[[Git|GitHub Repositories]] - Making MY stuff MINE!

[[BizPlan|Business Plan Templates]] - {{Book
|title=Business Plan Builder
|author=Jian
}}

=== Web Site Administration ===
*Policies & Procedures for the web sites.
[[Apache2|Hosting]]

[[php8|PHP Programming]]

[[wiki|MediaWiki]]

[[RoundCube|Web Mail]]

[[osTicket|Work Tickets]]

=== Misc Stuff ===
* [[OfficeStuff|Stuff I need for the Office]]
* [[Private:Side Hustles|Side Hustles]] - Stuff we want to look into insofar as making some extra money
* [[Private:376|376 Spreading Oak Lane]]

== Drafts ==
* [[Scratchpad]] - Just what it says. Just a place to jot stuff down before it gets categorized into a Page.
* [[Unsorted Notes]] - Stuff that is more important than a scratchpad.

== Wiki Utils ==
*[[NewPage]] - Create a new page...don't forget Namespace
*[[Backup]]
*[[Sandbox]]

{{Template:Copyright}}

About

2026-07-06T17:42:51Z

Admin: Admin moved page About to EAWF:About

Main Page

2026-07-06T17:40:34Z

Admin: /* Projects In Progress */

= '''EAWF''' ''Empowering People, Solving Problems'' =
'''[[EAWF:EAWFStandard|The EAWF Standard]]'''
== Projects In Progress ==
* [[EAWF:Btc|BTC Operations Manager]] - Bitcoin Node w/Mining Services
* [[EAWF:Mmgr|Mail Manager]] Postfix Mail Management System
* [[EAWF:Mwmgr|MediaWiki Manager]] - MediaWiki Management Tool
* [[EAWF:Wgmgr|Wireguard Manager]] - Manage Wireguard Connections
* [[EAWF:Audit]] - Rocky9 Server Auditor
* [[EAWF:Server|Server In A Box]] - Web, eMail, Wiki Server System for the masses

'''[[Private:Personal|Personal Projects]]'''

== EAWF Documentation Project ==
[[About|About EAWF]]

[[Squirrel|Squirrel Habitat]] - ''Ideas worth keeping, but not necessarily worth chasing today.''

[[Code Library]] - Code Snippets for all situations

[[EAWF|EAWF Business Management System]]

[[KBDocs|Knowledge Base]] - The EAWF Web Site Knowledge Base/Repository of Important EAWF Things

[[Bitcoin|Bitcoin Tips & Tricks]]

[[Git|GitHub Repositories]] - Making MY stuff MINE!

[[BizPlan|Business Plan Templates]] - {{Book
|title=Business Plan Builder
|author=Jian
}}

=== Web Site Administration ===
*Policies & Procedures for the web sites.
[[Apache2|Hosting]]

[[php8|PHP Programming]]

[[wiki|MediaWiki]]

[[RoundCube|Web Mail]]

[[osTicket|Work Tickets]]

=== Misc Stuff ===
* [[OfficeStuff|Stuff I need for the Office]]
* [[Private:Side Hustles|Side Hustles]] - Stuff we want to look into insofar as making some extra money
* [[Private:376|376 Spreading Oak Lane]]

== Drafts ==
* [[Scratchpad]] - Just what it says. Just a place to jot stuff down before it gets categorized into a Page.
* [[Unsorted Notes]] - Stuff that is more important than a scratchpad.

== Wiki Utils ==
*[[NewPage]] - Create a new page...don't forget Namespace
*[[Backup]]
*[[Sandbox]]

{{Template:Copyright}}