How to set Pipi configuration

Mike's Notes

Here are my notes from today's work on the Website Engine (wbs).

Resources

How to set Pipi configuration

By: Mike Peters
01/02/2025

Mike is the inventor and architect of Pipi and the founder of Ajabbi.

I'm manually migrating my first customer's website to Pipi's hosting. This is an excellent product test of the Website Engine (wbs), which sets up website hosting.

The next problem is enabling simple bullet-proof configurations for future customers to set up websites using no-code.

In the future, each of the hundreds of modules will have many configuration options, so a standardised system-wide process is needed.

This morning, I sketched some ideas on how the Admin User Interface (UI) might look.

This afternoon, I figured out that the Namespace Engine (nsp) already has a way to register the interfaces of every engine that is automatically built by the Factory Engine (fac).

I added another Interface Class Type, "Config", and solved the problem.

This allowed the fast addition of these examples of global properties that a website might have as options for the admin.

  • Meta Title
  • Meta Keywords
  • Meta Description
  • Domain Name
  • Default Language, e.g. eng
  • Plugins
  • Default Theme
  • Use References
  • Use See Also
  • Use Keywords
  • etc

Doing this also automatically generates config variable names used in internal messaging.

This would also enable configuration storage in XML or other open formats for interchange purposes and documentation.

This configuration system will also work for all the other engines.

No comments:

Post a Comment