Update: Successful Deployment of My Local Service on Choreo

[Visal Vitharana (Intern)]

Hi all,

I’m pleased to inform you that we have successfully deployed the my local service on Choreo. You can access the service at the following URL:
https://mylocal.datafoundation.lk/mylocal/

During the deployment process, we explored several methods to optimize the backend deployment. Initially, it took approximately 3 hours for the service to complete the warm-up process in Choreo. However, with @Ramith Jayasinghe's data file embedding method, we successfully reduced the startup time to around 1.5 minutes, and sometimes even under 1 minute.

Please note that scale-to-zero is enabled in Choreo, so the front end may take a little time to load initially.

If you have any questions or need further details, please feel free to reach out.

Best regards,

Visal.

--

Visal Vitharana | Intern Software Engineer | WSO2

(m)  +94 76 712 3972      |      (e)  vi...@wso2.com

[Malith Jayasinghe]

Great!

I just tried it as well, and the site loaded instantly for me.

[Sanjiva Weerawarana]

This is great! Tried it and its awesome :). Thanks Visal!

--

Sanjiva Weerawarana

[Sanjiva Weerawarana]

Where is the code? We need to organize the repos too.

--

Sanjiva Weerawarana

[Ramith Jayasinghe]

Hi Sanjiva,

 Code for the server side is in : https://github.com/LDFLK/mylocal_service/tree/choreo

regards

Ramith

--

Ramith Jayasinghe | Director Engineering | WSO2 Inc.

(w) +94777542851 | Email: ram...@wso2.com

[Visal Vitharana (Intern)]

Hi Sanjiva,

All the code repositories are organized under the LDF GitHub organization. For the deployments on Choreo, we created Choreo branches in the relevant repositories. These branches were necessary to accommodate the following changes required by Choreo:

1. Update Dockerfiles to use non-root users, as Choreo mandates non-root execution.
2. Add endpoint details to the .choreo directory for proper configuration.
3. Update deprecated modules, as some of them were outdated and incompatible.
4. Adjust authentication to OAuth2, to align with Choreo’s requirements.

And we performed a few additional adjustments during deployment in some repos, including environment-specific tweaks to ensure everything runs smoothly.

Regards,

Visal.