Application Development - Revision history

Dominic at 22:19, 18 September 2025

2025-09-18T22:19:26Z

← Older revision		Revision as of 22:19, 18 September 2025
Line 9:		Line 9:
	But rather than putting all these customizations into a server-side configuration file, they would normally be implemented as Python packages which are then imported as '''configuration templates'''. This way, complex custom configurations can be developed, tested and maintained away from the server - and can easily be shared and re-used in other deployments.		But rather than putting all these customizations into a server-side configuration file, they would normally be implemented as Python packages which are then imported as '''configuration templates'''. This way, complex custom configurations can be developed, tested and maintained away from the server - and can easily be shared and re-used in other deployments.

	An '''Eden application''' is therefore understood as a re-usable configuration template (or a combination of templates), and '''Application Development''' is focused on ~~Eden configuration~~ templates.		An '''Eden application''' is therefore understood as a re-usable configuration template (or a combination of templates), and '''Application Development''' is focused on such templates.

	A small selection of configuration templates is included in the Eden code base. However, downstream projects will often develop their own templates, and may publish and/or market them independently - a business model which we encourage and support.		A small selection of configuration templates is included in the Eden code base. However, downstream projects will often develop their own templates, and may publish and/or market them independently - a business model which we encourage and support.

Dominic: Undo revision 124 by Dominic (talk)

2025-09-18T22:17:35Z

Undo revision 124 by Dominic (talk)

← Older revision		Revision as of 22:17, 18 September 2025
Line 9:		Line 9:
	But rather than putting all these customizations into a server-side configuration file, they would normally be implemented as Python packages which are then imported as '''configuration templates'''. This way, complex custom configurations can be developed, tested and maintained away from the server - and can easily be shared and re-used in other deployments.		But rather than putting all these customizations into a server-side configuration file, they would normally be implemented as Python packages which are then imported as '''configuration templates'''. This way, complex custom configurations can be developed, tested and maintained away from the server - and can easily be shared and re-used in other deployments.

	An '''Eden application''' is therefore understood as a re-usable configuration template (or a combination of templates), and '''Application Development''' is focused on ~~re-usable~~ Eden configuration templates.		An '''Eden application''' is therefore understood as a re-usable configuration template (or a combination of templates), and '''Application Development''' is focused on Eden configuration templates.

	A small selection of configuration templates is included in the Eden code base. However, downstream projects will often develop their own templates, and may publish and/or market them independently - a business model which we encourage and support.		A small selection of configuration templates is included in the Eden code base. However, downstream projects will often develop their own templates, and may publish and/or market them independently - a business model which we encourage and support.

Dominic at 22:16, 18 September 2025

2025-09-18T22:16:45Z

← Older revision		Revision as of 22:16, 18 September 2025
Line 9:		Line 9:
	But rather than putting all these customizations into a server-side configuration file, they would normally be implemented as Python packages which are then imported as '''configuration templates'''. This way, complex custom configurations can be developed, tested and maintained away from the server - and can easily be shared and re-used in other deployments.		But rather than putting all these customizations into a server-side configuration file, they would normally be implemented as Python packages which are then imported as '''configuration templates'''. This way, complex custom configurations can be developed, tested and maintained away from the server - and can easily be shared and re-used in other deployments.

	An '''Eden application''' is therefore understood as a re-usable configuration template (or a combination of templates), and '''Application Development''' is focused on Eden configuration templates.		An '''Eden application''' is therefore understood as a re-usable configuration template (or a combination of templates), and '''Application Development''' is focused on re-usable Eden configuration templates.

	A small selection of configuration templates is included in the Eden code base. However, downstream projects will often develop their own templates, and may publish and/or market them independently - a business model which we encourage and support.		A small selection of configuration templates is included in the Eden code base. However, downstream projects will often develop their own templates, and may publish and/or market them independently - a business model which we encourage and support.

Dominic at 22:16, 18 September 2025

2025-09-18T22:16:01Z

← Older revision		Revision as of 22:16, 18 September 2025
Line 7:		Line 7:
	Such adjustments can be minimal, or (more commonly) be extensive customization involving menus, forms, user roles, workflows, data models and even processing logic - so that Eden can be repurposed and adapted for many different use-cases and scenarios.		Such adjustments can be minimal, or (more commonly) be extensive customization involving menus, forms, user roles, workflows, data models and even processing logic - so that Eden can be repurposed and adapted for many different use-cases and scenarios.

	But rather than putting all these customizations into a server-side configuration file, they would normally be implemented as Python packages which are then imported as '''configuration templates'''. This way, complex custom configurations can be developed, tested and maintained away from the server - and easily be shared and re-used in other deployments.		But rather than putting all these customizations into a server-side configuration file, they would normally be implemented as Python packages which are then imported as '''configuration templates'''. This way, complex custom configurations can be developed, tested and maintained away from the server - and can easily be shared and re-used in other deployments.

	An '''Eden application''' is therefore understood as a re-usable configuration template (or a combination of templates), and '''Application Development''' is focused on Eden configuration templates.		An '''Eden application''' is therefore understood as a re-usable configuration template (or a combination of templates), and '''Application Development''' is focused on Eden configuration templates.

	A small selection of configuration templates is included in the Eden code base. However, downstream projects will often develop their own templates, and may publish and/or market them independently - a business model which we encourage and support.		A small selection of configuration templates is included in the Eden code base. However, downstream projects will often develop their own templates, and may publish and/or market them independently - a business model which we encourage and support.

Dominic at 22:15, 18 September 2025

2025-09-18T22:15:08Z

← Older revision		Revision as of 22:15, 18 September 2025
Line 5:		Line 5:
	The appearance and business logic of this application can be adjusted to the needs of a particular deployment by altering settings in the <code>models/000_config.py</code> configuration file on the server.		The appearance and business logic of this application can be adjusted to the needs of a particular deployment by altering settings in the <code>models/000_config.py</code> configuration file on the server.

	Such adjustments can be minimal, or (more commonly) extensive customization involving menus, forms, user roles, workflows, data models and even processing logic - so that Eden can be repurposed and adapted for many different use-cases and scenarios.		Such adjustments can be minimal, or (more commonly) be extensive customization involving menus, forms, user roles, workflows, data models and even processing logic - so that Eden can be repurposed and adapted for many different use-cases and scenarios.

	But rather than putting all these customizations into a server-side configuration file, they would normally be implemented as Python packages which are then imported as '''configuration templates'''. This way, complex custom configurations can be developed, tested and maintained away from the server - and easily be shared and re-used in other deployments.		But rather than putting all these customizations into a server-side configuration file, they would normally be implemented as Python packages which are then imported as '''configuration templates'''. This way, complex custom configurations can be developed, tested and maintained away from the server - and easily be shared and re-used in other deployments.

Dominic at 22:14, 18 September 2025

2025-09-18T22:14:09Z

← Older revision		Revision as of 22:14, 18 September 2025
Line 9:		Line 9:
	But rather than putting all these customizations into a server-side configuration file, they would normally be implemented as Python packages which are then imported as '''configuration templates'''. This way, complex custom configurations can be developed, tested and maintained away from the server - and easily be shared and re-used in other deployments.		But rather than putting all these customizations into a server-side configuration file, they would normally be implemented as Python packages which are then imported as '''configuration templates'''. This way, complex custom configurations can be developed, tested and maintained away from the server - and easily be shared and re-used in other deployments.

	An '''Eden application''' is therefore understood as a re-usable configuration template (or a combination of templates), and '''Application Development''' is focused on Eden configuration templates. A small selection of configuration templates is included in the Eden code base. However, downstream projects will often develop their own templates, and may publish and/or market them independently - a business model which we encourage and support.		An '''Eden application''' is therefore understood as a re-usable configuration template (or a combination of templates), and '''Application Development''' is focused on Eden configuration templates.

			A small selection of configuration templates is included in the Eden code base. However, downstream projects will often develop their own templates, and may publish and/or market them independently - a business model which we encourage and support.

Dominic at 22:12, 18 September 2025

2025-09-18T22:12:47Z

← Older revision		Revision as of 22:12, 18 September 2025
Line 1:		Line 1:
	== Eden applications ==		== Eden applications ==

	Sahana Eden is a ''web application'' written for the [https://web2py.com web2py] framework.		Sahana Eden is a multi-purpose ''web application'' written for the [https://web2py.com web2py] framework.

	The appearance and business logic of this application can be adjusted to the needs of a particular deployment by altering settings in the <code>models/000_config.py</code> configuration file on the server.		The appearance and business logic of this application can be adjusted to the needs of a particular deployment by altering settings in the <code>models/000_config.py</code> configuration file on the server.

Dominic at 22:09, 18 September 2025

2025-09-18T22:09:38Z

← Older revision		Revision as of 22:09, 18 September 2025
Line 9:		Line 9:
	But rather than putting all these customizations into a server-side configuration file, they would normally be implemented as Python packages which are then imported as '''configuration templates'''. This way, complex custom configurations can be developed, tested and maintained away from the server - and easily be shared and re-used in other deployments.		But rather than putting all these customizations into a server-side configuration file, they would normally be implemented as Python packages which are then imported as '''configuration templates'''. This way, complex custom configurations can be developed, tested and maintained away from the server - and easily be shared and re-used in other deployments.

	An '''Eden application''' is therefore understood as a re-usable configuration template (or a combination of templates).		An '''Eden application''' is therefore understood as a re-usable configuration template (or a combination of templates), and '''Application Development''' is focused on Eden configuration templates. A small selection of configuration templates is included in the Eden code base. However, downstream projects will often develop their own templates, and may publish and/or market them independently - a business model which we encourage and support.

	A small selection of configuration templates is included in the code base, ~~but~~ downstream projects will often develop their own templates, and ~~potentially~~ publish and market them independently - a business model which we encourage and support.

Dominic: Created page with "== Eden applications == Sahana Eden is a ''web application'' written for the [https://web2py.com web2py] framework. The appearance and business logic of this application can be adjusted to the needs of a particular deployment by altering settings in the `models/000_config.py` configuration file on the server. Such adjustments can be minimal, or (more commonly) extensive customization involving menus, forms, user roles, workflows, data models and even proce..."

2025-09-18T22:06:04Z

Created page with "== Eden applications == Sahana Eden is a ''web application'' written for the [https://web2py.com web2py] framework. The appearance and business logic of this application can be adjusted to the needs of a particular deployment by altering settings in the <code>models/000_config.py</code> configuration file on the server. Such adjustments can be minimal, or (more commonly) extensive customization involving menus, forms, user roles, workflows, data models and even proce..."

New page

== Eden applications ==

Sahana Eden is a ''web application'' written for the [https://web2py.com web2py] framework.

The appearance and business logic of this application can be adjusted to the needs of a particular deployment by altering settings in the <code>models/000_config.py</code> configuration file on the server.

Such adjustments can be minimal, or (more commonly) extensive customization involving menus, forms, user roles, workflows, data models and even processing logic - so that Eden can be repurposed and adapted for many different use-cases and scenarios.

But rather than putting all these customizations into a server-side configuration file, they would normally be implemented as Python packages which are then imported as '''configuration templates'''. This way, complex custom configurations can be developed, tested and maintained away from the server - and easily be shared and re-used in other deployments.

An '''Eden application''' is therefore understood as a re-usable configuration template (or a combination of templates).

A small selection of configuration templates is included in the code base, but downstream projects will often develop their own templates, and potentially publish and market them independently - a business model which we encourage and support.