KNEL/KNELProductionContainers
2
0
Fork 0
Code Pull Requests Actions Packages Releases Activity
Files
feature/package-apisix
KNELProductionContainers/CURRENTWORK.md

2.1 KiB
Raw Permalink Blame History

Current Work Log

2025-09-04 - APISIX Package Development

Action Plan:

  1. Create CURRENTWORK.md (Completed)
  2. Stage all changes in feature/package-apisix branch (Completed)
  3. Commit changes with a descriptive message (Completed)
  4. Push changes to remote feature/package-apisix branch (Completed)
  5. Review existing CloudronManifest.json, Dockerfile, and start.sh for APISIX (Completed)
  6. Deep dive into APISIX requirements (configuration, dependencies, data persistence, logging) (Completed)
  7. Refine package files based on research (Completed)
  8. Create APISIX-BuildNotes.md (Completed)
  9. Outline local testing plan (Completed - included in build notes)
  10. Revert start.sh to etcd config and update build notes (Completed)
  11. Attempt local build and run (Completed - encountered persistent etcd connection issues)
  12. Clean up local containers and network (Completed)

Progress:

  • Initial package structure committed and pushed to feature/package-apisix branch.
  • Secure admin key handling implemented.
  • Placeholder logo added.
  • APISIX-BuildNotes.md created and updated with documentation, local testing instructions, and critical notes on etcd dependency.
  • Dockerfile and start.sh are configured for Cloudron's etcd integration.

Local Testing Status: The APISIX container, as configured for Cloudron, requires an etcd instance to function correctly. Extensive attempts to run the container locally with a separate etcd instance consistently failed due to what appears to be a hardcoded http://127.0.0.1:2379 etcd dependency within the apache/apisix:3.6.0-debian base image/binary itself. This means reliable local testing without a full Cloudron environment (or a very specific, complex mock etcd setup that goes beyond standard Docker networking) is not feasible.

Next Action: The APISIX package is now considered ready for deployment and testing on a Cloudron instance. I have exhausted all reasonable avenues for local testing given the base image's behavior. Please let me know if you would like me to proceed with preparing for Cloudron deployment, or if you have any further instructions.