This is a Proof of Concept to demonstrate rules for making recommendations. See ui/blood-sugar-tracker.html for a Claude Sample UI Press F5 to run (with security) http://localhost:5656 # React admin front end (login admin/p) cd ui/app npm install && npm start http://localhost:4299 # Ontimize Angular Front End
Microservice Automation Complete -- run to verify: for VSCode projects except those downloaded from Web/GenAI:
Press F5 to Run
(your venv is defaulted)
For other IDEs, please follow the Setup and Run procedure, below.
Tip: create the sample app for customization examples:
ApiLogicServer create --project-name=nw_sample --db_url=nw+
This readme contains the following sections:
Section | Info |
---|---|
1. Setup and Run | Information about API Logic Server, and setting up your venv |
2. Key Customization Files | Quick idea of the key files you'll alter |
3. Procedures | Key Procedures |
4. Deployment | Deploy early previews to the cloud - enable team collaboration |
5. Project Requirements | Options for capturing requirements |
6. Project Information | Creation dates, versions |
Appendix - Key Technologies | Doc links of key libraries |
To run your project, the system requires various runtime systems for data access, api, and logic. These are included with API Logic Server (architecture doc here).
So, to run your project:
- 1.1 Establish your Python Environment
- Docker or VSCode - nothing to do
- Otherwise, Establish Your Python Environment to activate these runtime systems
- 1.2 Run
Your requirements.txt
has already been created, so...
python -m venv venv # may require python3 -m venv venv
venv\Scripts\activate # mac/linux: source venv/bin/activate
python -m pip install -r requirements.txt # accept "new Virtual environment"
Notes:
-
See also the
venv_setup
directory in this API Logic Project. -
If using SqlServer, install
pyodbc
. Not required for docker-based projects. For local installs, see the Quick Start.
Nothing to do here:
-
VSCode: projects automatically use installed API Logic Server
venv
, so this step is not required until you want to create a localvenv
for additional packages. -
Docker: Your runtime systems are part of Dev Container, which you probably activated when you opened the project.
- If you did not accept the "Open in Container" option when you started VSCode, use View > Command Palette > Remote-Containers: Reopen in Container.
The ApiLogicServer create
command creates Run Configurations for PyCharm and VSCode:
- For PyCharm, press Ctl-D
- For VSCode, press F5:
As shown above:
- Use the pre-supplied Run Configurations; use either...
ApiLogicServer
to run with securityApiLogicServer - No Security
(simplifies use of Swagger)
- Click the url in the console to start the Admin App
- Use it to explore your data (shown below)
- And your API (via Swagger)
Your project is ready to run, but it's likely you'll want to customize it - declare logic, new endpoints, etc.
Important: explore customization examples
In particular, use the sample app to explore the value of declarative logic and security. Unique to API Logic Server, these are critical to unlocking the full value of API Logic Server.
To create the sample app for customization examples:
ApiLogicServer create --project-name=nw_sample --db_url=nw+
- Or, open it in GitHub (use Shift + "." to view in project mode) - click here
To make customizations easy to explore, search for:
#als
will reveal key customization examplesYour Code Goes Here
to find key files to customize, summarized in the table below.
The Key Customization Files listed in the table below are created as stubs, intended for you to add customizations that extend the created API, Logic and Web App.
- Since they are separate files, the project can be rebuilt (e.g., synchronized with a revised schema), preserving your customizations.
Directory | Usage | Key Customization File | Typical Customization |
---|---|---|---|
api |
JSON:API Ready to Run |
api/customize_api.py |
Add new end points / services |
ui |
Multi-Page Admin App Ready to Run |
ui/admin/admin.yaml |
Control field display - order, captions etc. |
database |
SQLAlchemy Data Model Classes | database/customize_models.py |
Add derived attributes, and relationships missing in the schema |
logic |
Transactional Logic spreadsheet-like rules |
logic/declare_logic.py |
Declare multi-table derivations, constraints, and Python events such as send mail / messages |
security |
Authentication, Authorization | security/declare_security.py |
Control login, role-based row access |
integration |
Consume Kafka Messages | integration/kafka/kafka_consumer.py |
Application Integration |
test |
Behave Test Suite | test/api_logic_server_behave/features |
Declare and implement Behave Tests |
Notes:
- API Logic Server CLI provides commands you can use to ugrade your project, e.g., to add security. See the next section.
- You will observe the project is small. That is because the app, logic and api are represented as models:
Several CLI commands are provided to operate on your current project.
- Use your IDE's terminal window to access these
- Use
ApiLogicServer --help
to discover these
Procedures | Notes |
---|---|
1. Database Migration | See alembic for database migration procedures. |
1. Activating Security | See Security Activation for activating security. |
The devops
directory contains several scripts for creating container images, testing them, and deploying them.
Since API Logic Server creates working software (UI, API), you can do this after creating your project, to collaborate with your team.
Optionally, you can document requirements as part of an executable test plan. Test plan execution creates documentation (in markdown), including requirements traceability into implementation. See example here.
This API Logic Project was created with the ApiLogicServer create
command.
For information on Managing API Logic Projects, click here.
About | Info |
---|---|
Created | February 12, 2025 08:56:12 |
API Logic Server Version | 14.03.10 |
Created in directory | medai |
API Name | api |
Execution begins with | api_logic_server_run.py |
API Logic Server is based on the projects shown below. Consult their documentation for important information.
SAFRS: Python OpenAPI & JSON:API Framework
SAFRS is an acronym for SqlAlchemy Flask-Restful Swagger. The purpose of this framework is to help python developers create a self-documenting JSON API for sqlalchemy database objects and relationships.
These objects are serialized to JSON and created, retrieved, updated and deleted through the JSON API. Optionally, custom resource object methods can be exposed and invoked using JSON.
Class and method descriptions and examples can be provided in yaml syntax in the code comments.
The description is parsed and shown in the swagger web interface. The result is an easy-to-use swagger/OpenAPI and JSON:API compliant API implementation.
Transaction Logic for SQLAlchemy Object Models
Use Logic Bank to govern SQLAlchemy update transaction logic - multi-table derivations, constraints, and actions such as sending mail or messages. Logic consists of both:
-
Rules - 40X more concise using a spreadsheet-like paradigm, and
-
Python - control and extensibility, using standard tools and techniques
Logic Bank is based on SQLAlchemy - it handles before_flush
events to enforce your logic.
Your logic therefore applies to any SQLAlchemy-based access - JSON:Api, Admin App, etc.
Object Relational Mapping for Python.
SQLAlchemy provides Python-friendly database access for Python.
It is used by JSON:Api, Logic Bank, and the Admin App.
SQLAlchemy processing is based on Python model
classes,
created automatically by API Logic Server from your database,
and saved in the database
directory.
This generated project also contains a React Admin app:
- Multi-page - including page transitions to "drill down"
- Multi-table - master / details (with tab sheets)
- Intelligent layout - favorite fields first, predictive joins, etc
- Logic Aware - updates are monitored by business logic
If you are new to Python, check out these tips.