Edu-Carone-SA builds a staging front door, but it never ships
The fork proposed a protected AWS test environment where the application and login flow could be tried before release.
The setup paired hardened application containers with a separate staging deployment path, using identity-based access instead of stored deployment credentials. It also gave the application controlled access to file storage through its cloud role.
- A load-balanced staging address for reaching the running application.
- A self-hosted sign-in service with tested account creation and token-based login.
- Gateway routing and a data API to support the application's services.
The pull request was closed without being merged, so this remains a useful signal of direction rather than a live capability in the fork.
So what Legal-product teams assessing operational maturity may want to inspect the proposal, but should not assume the staging environment is available.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?