USE 111 - Initial app setup

[ghukill]

Purpose and background context

This PR is the initial application setup, including:

• renaming my_app to embeddings
• beginning with a very minimal README
• updating the uv entrypoint script to be called embeddings

This app is built from the uv branch in python-cli-template. That branch had a recent update which this new repository inherits.

As discussed internally, we had decided that new CLI applications would likely use uv. Additionally, this application will have fairly significant library and technical requirements, making uv a good choice.

This application also includes a .aws-architecture file with the value linux/arm64, which will build an arm64 image/container once we get to deployment. This file is utilized in the Makefile to build the appropriate image type for the convenience command make docker-build.

How can a reviewer manually see the effects of these changes?

Clone the repo and then run make install.

Then, confirm make test and make lint pass.

Additionally, you can build a docker image and launch a container to test that side of things:

make docker-build
make docker-run

Output:

docker run timdex-embeddings:latest
2025-10-21 20:42:52,252 INFO embeddings.cli.main(): Logger 'root' configured with level=INFO
2025-10-21 20:42:52,252 INFO embeddings.cli.main(): No Sentry DSN found, exceptions will not be sent to Sentry
2025-10-21 20:42:52,252 INFO embeddings.cli.main(): Running process
2025-10-21 20:42:52,252 INFO embeddings.cli.main(): Total time to complete process: 0:00:00.000212

Includes new or updated dependencies?

NO

Changes expectations for external applications?

NO

What are the relevant tickets?

• https://mitlibraries.atlassian.net/browse/USE-111

Code review

• Code review best practices are documented here and you are encouraged to have a constructive dialogue with your reviewers about their preferences and expectations.

[jonavellecuerdo]

It's looking good to me, however, one thing I noticed is that the Docker file uses Python 3.13. I'm assuming this is because that's what's in the template, but .python-version still reads 3.12. Can you verify which version of Python will be used?

[ghukill]

It's looking good to me, however, one thing I noticed is that the Docker file uses Python 3.13. I'm assuming this is because that's what's in the template, but .python-version still reads 3.12. Can you verify which version of Python will be used?

Nice catch!! Thank you. Should be 3.12 all around. Dockerfile is updated.