Hosted on Gitlab, mirrored on Github
The 'Scaffold' repo primarily concerns itself with the pg/plsql development environment that builds Dynamic appGoo Databases Pages and Functions for the Web.
The functions are authored through your IDE (such as Sublime, Emacs or Visual Studio Code), saved in the file system and the appGoo Builder is then run to build the functions and procedures within the destination database.
Read more about appGoo capability
Read more about how to develop applications in appGoo
Simply referred to as the 'Builder', this program can build your application code into the database so that it is ready to be called by appGoo. The Builder installs the appGoo capability into the database as well as the application that you develop.
The builder caters for an upgrade to appGoo as enhancements and fixes are released, and also has the ability for you to upgrade the data and objects of your application in addition to new versions of your code.
The Builder consists of the following programs:
- agBuild. This is the core program that builds your application code into the database.
- agNew. Can instantiate a new appGoo project for you by creating a custom folder structure and populating the structure with the appGoo functionality to be installed into the database
- agCreate. Can convert existing text assets into a database function call that allows the text asset to be retrieved by calling the function. For example, a call for a CSS file could be made from the database rather than the filesystem. Also allows minimisation, and caters for both CSS and JavaScript. This will also allow you to modify the output of either function based upon runtime parameters you supply.
- agClean. This removes appGoo and all your code from the database but does not uninstall the objects nor data (apart from the functions and procedures)
Read more about the appGoo Scaffold Builder
appGoo includes procedures and functions that are used to support the appGoo capability and to also accelerate the development of applications.
appGoo instals into a schema titled 'ag_sys' which refers to "appGoo System". You do not develop in this schema. If you do modify the objects within ag_sys you risk your customisation being replaced by an appGoo upgrade which will replace your customisations without notice.
The procedures and functions that you author will be in your application's private schema and it's "search path" can be set to be before ag_sys so that you may use your version of the appGoo helper functions. If you alter the definition of the appGoo helper function then it is likely that it will get replaced and re-built due to a package update, therefore you are better implementing your own version of the function by copying (or creating your own) the appGoo version and altering what is required.
Read more about the appGoo Helper Functions
None of this code is production-ready and is still undergoing development. It is not even ready for you to create a development environment with. We will publish a note when the code has reached a level of maturity and testing that would permit it to be ready for you to install and experiment with.
We anticipate that a release will be made in 2019 that will be usable for you to build upon. As that time approaches we will refine the messaging here concerning this. Our plans at this stage are:
- Initially release for postgresql 10 and 11 with basic Apache capability
- Compatibility with clustered postgresql
- Enhance the Apache capability around configuration and error integration
- Deliver SEO capability along with compatibility for multiple domains served through a single Apache & appGoo installation
- Enhance the capability to deliver all web assets from the database including CSS, JS, fonts and files including graphics
- Release for other databases. Initial candidates currently include Neo4j, Tibero, MariaDB, Mongo DB & SQL Server
There will be many other enhancements that are delivered that are not listed here and will be a reflection of requirements that are desired by contributors or requirements identified by ourselves to strengthen the applications that we build in appGoo.
Contribution is welcome using pull requests within Github. We encourage improvements to existing functionality by improving the quality of the code. If you wish to add additional features, please inquire with us first so that we can agree if the desired feature is in line with the vision for appGoo.