How dbeniteza/pokeapex works
Project type and purpose
• This is a full-stack Progressive Web Application built on Oracle APEX, hosted on Oracle Cloud Infrastructure.
• It consumes the external PokéAPI.co service and surfaces Pokémon data via APEX pages, PL/SQL logic, and static assets.
File structure
• Top-level folders:
• application/ – APEX application definitions (page metadata in YAML, shared components, theme templates, static files)
• src/plsql/ – PL/SQL package bodies/specs (pkmn_data.pkb/pks) providing stored-procedure logic
• Configuration files: code ownership, license.
• The directory layout follows an APEX “export” style: pages, page groups, shared components, theme artifacts, and PL/SQL packages.
README for additional insights
• Stack: Oracle APEX 23.2.3, Oracle Database 19c, Oracle Linux 9.3, NGINX 1.20.1.
• The application runs as a PWA in the browser, served via NGINX/ORDS to the APEX engine, backed by an Oracle DB.
• It integrates with PokéAPI.co at runtime for live data.