Gitiles
Code Review Sign In
gerrit.avm99963.com / gomodules / zenithplanner / c3b00d68e54c6abc2ffd1a9ce32da87c59649386
commitc3b00d68e54c6abc2ffd1a9ce32da87c59649386[log] [tgz]
authorAdrià Vilanova Martínez <me@avm99963.com>Thu May 15 16:07:01 2025 +0200
committerAdrià Vilanova Martínez <me@avm99963.com>Fri May 16 11:08:40 2025 +0200
tree6d2a42c5656194fed3c18c055e0a57df1fad88ee
parent6e72f027db2d300d438b399c738c0bbc64b37f70 [diff]
chore: create compose file example

Change-Id: I6a6a6964867dedcccb7772ec595b20ab1d4a5a6e
2 files changed
tree: 6d2a42c5656194fed3c18c055e0a57df1fad88ee
  1. cmd/
  2. database/
  3. docs/
  4. examples/
  5. internal/
  6. tools/
  7. .bazelrc
  8. .gitignore
  9. BUILD.bazel
  10. compose.dev.yml
  11. go.mod
  12. go.sum
  13. LICENSE
  14. MODULE.bazel
  15. MODULE.bazel.lock
  16. NOTICE
  17. README.md
README.md

ZenithPlanner

Under development

If you want to gain some context about this project, you may read the initial project plan at //docs/project_plan.

In the future, when I can dedicate more time to this project, I will update this README file to be much more friendly.

To do

  • Write this README file.
  • Set up CI/CD.
  • Fix known bugs:
    • Recurring events sometimes are not processed well, and they are sometimes deleted.
    • When starting the backend, it will send a watch request to Google Calendar even if a webhook is already active, so we will end up receiving duplicate requests
  • Refactor code.

Release

bazel run //cmd/backend:push_all --config=release