Skip to content

Conversation

@alexsunday
Copy link

This change add a static method createCustomS3 to S3ObjectMonitor, allowing the creation of S3 clients with custom endpoints. This is useful for development and testing environments, enabling Signal to interact with local or non-standard S3-compatible storage. The method supports endpoint override and path-style access, making it easier to run integration tests without relying on AWS infrastructure.

@stale
Copy link

stale bot commented Nov 3, 2025

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@stale stale bot added the wontfix label Nov 3, 2025
@stale stale bot closed this Nov 11, 2025
@jon-signal
Copy link
Contributor

@alexsunday Apologies for the delay here; let's reopen and review this.

@jon-signal jon-signal reopened this Nov 11, 2025
@jon-signal jon-signal self-requested a review November 11, 2025 15:37
@alexsunday
Copy link
Author

Perhaps the original intention of Signal's open-source release was to enable code review for verifying its security, but in reality, very few people independently follow up and deploy the latest version of the server software?

These changes are critical for self-deployment, while maintaining excessive patches and branches independently becomes overly complex. Therefore, I hope they can be merged. Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants