Move the tessdata files to AWS S3
- Dominant language
- Java
- Stars
- 1
- Forks
- 1
- Avg merge
- 2m
- Merged PRs (30d)
- 1
Description
### Objective
To avoid the large time of download files (in first pull or clone) and wait for a smaller docker image, it's a good idea integrate the **AWS SDK** to push the `tessdata` files to **S3** service
### Checklist
- [ ] Implement the AWS SDK for java in the spring-boot API
- [ ] Retrieve the `tessdata `files `"eng.traineddata"` and `"spa.traineddata" `from s3
- [ ] Remove the files of` /resources/tessdata/*`
Contributor guide
Research direction
Start in the Spring Boot API and trace how the tessdata resources are currently loaded; inspect /resources/tessdata/* and the references to eng.traineddata and spa.traineddata. Confirm the AWS SDK and S3 retrieval requirements, then verify that both files are fetched successfully and the bundled resource files can be removed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, java, spring-boot
- Domain
- api, backend, cloud
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100