Feat/staging anchr setup

[coodos]

Description of change

Issue Number

closes #251

Type of change

• New (a change which implements a new feature)

How the change has been tested

Change checklist

• I have ensured that the CI Checks pass locally
• I have removed any unnecessary logic
• My code is well documented
• I have signed my commits
• My code follows the pattern of the application
• I have self reviewed my code

Summary by CodeRabbit

• Chores

  • Updated ignore rules to exclude the .env.development file from version control.
  • Removed the .env.development environment configuration file from the repository.

• New Features

  • Added conditional forwarding of webhook requests to an external URL in both Blabsy and Pictique platforms when a specific environment variable is set.

• Refactor

  • Improved code formatting for consistency in webhook controllers.

• Revert

  • Deleted a webhook controller in the Pictique platform that previously handled various entity operations.

• Bug Fixes

  • Expanded the list of allowed hosts for the Pictique development server.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The changes introduce early exit logic in webhook controllers for both Blabsy and Pictique APIs, forwarding webhook payloads to an external URL if a specific environment variable is set. The .env.development file for Blabsy was deleted and added to .gitignore. The Pictique Vite config was updated to allow new hosts. The Pictique web3adapter webhook controller was removed.

Changes

File(s)	Change Summary
.gitignore	Added .env.development to ignored files.
platforms/blabsy/.env.development	Deleted development environment file.
platforms/blabsy-w3ds-auth-api/src/controllers/WebhookController.ts	Added early exit logic to forward webhooks externally if ANCHR_URL is set; minor formatting.
platforms/pictique-api/src/controllers/WebhookController.ts	Added early exit logic to forward webhooks externally if ANCHR_URL is set.
platforms/pictique-api/src/web3adapter/controllers/WebhookController.ts	Deleted the entire WebhookController class and its logic.
platforms/pictique/vite.config.ts	Added new allowed hosts to dev server config.

Sequence Diagram(s)

sequenceDiagram
    participant Client
    participant WebhookController
    participant ExternalService

    Client->>WebhookController: POST /webhook (payload)
    alt ANCHR_URL is set
        WebhookController->>ExternalService: POST payload to ANCHR_URL/PUBLIC_*_BASE_URL
        WebhookController-->>Client: (early return)
    else ANCHR_URL not set
        WebhookController->>WebhookController: Process webhook payload locally
        WebhookController-->>Client: Response
    end

Loading

Assessment against linked issues

Objective	Addressed	Explanation
Health check on the eVault at startup (#251)	❌	No code related to eVault health checks or startup logic was introduced.

Assessment against linked issues: Out-of-scope changes

Code Change	Explanation
Early exit and external forwarding of webhook payloads (platforms/blabsy-w3ds-auth-api/src/controllers/WebhookController.ts, platforms/pictique-api/src/controllers/WebhookController.ts)	Not related to eVault health checks; changes only webhook handling logic.
Deletion of WebhookController class and logic (platforms/pictique-api/src/web3adapter/controllers/WebhookController.ts)	Removal of unrelated webhook processing logic, not tied to eVault health checks.
Deletion and ignoring of .env.development (platforms/blabsy/.env.development, .gitignore)	Environment file management, unrelated to eVault health checks.
Update to allowed hosts in Vite config (platforms/pictique/vite.config.ts)	Dev server configuration, not related to eVault or health checks.

Poem

A webhook hops, then takes a leap,
If ANCHR_URL is set, no secrets to keep!
Env files vanish, configs expand,
Controllers pruned by a careful hand.
Though eVault health is not yet here,
The codebase hops ahead—never fear!
🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between dfd92b5 and a3a7683.

⛔ Files ignored due to path filters (2)

• pglite-debug.log is excluded by !**/*.log
• platforms/blabsy/pglite-debug.log is excluded by !**/*.log

📒 Files selected for processing (6)

• .gitignore (1 hunks)
• platforms/blabsy-w3ds-auth-api/src/controllers/WebhookController.ts (4 hunks)
• platforms/blabsy/.env.development (0 hunks)
• platforms/pictique-api/src/controllers/WebhookController.ts (2 hunks)
• platforms/pictique-api/src/web3adapter/controllers/WebhookController.ts (0 hunks)
• platforms/pictique/vite.config.ts (1 hunks)

✨ Finishing Touches

• 📝 Generate Docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.