GitHub Actions publish about fastapi-nano HOT 6 CLOSED

I think you've convinced me. So, what I'll do is to push the container to GitHub registry and then see if anyone finds that useful. Thank you.

from fastapi-nano.

After battling with the CI, this is now ready. Checkout the release for details. Thank you.

from fastapi-nano.

This is a great idea but I'm not sure how it'd be helpful when you'll need access to the code.

from fastapi-nano.

@rednafi Access to the code how? Could you elaborate?

from fastapi-nano.

@ayr-ton This application is pretty basic at what it does. However, it's extensible. So, if I push this as a container, what purpose that'd serve? I mean in the end, you'll need access to the code in the container and if you docker-pull the container, you won't have access to the source code.

I mean, it's easy enough to push the container but I was wondering what purpose that'd serve.

from fastapi-nano.

@rednafi Got it!
I think in 2 advantages:

• Testing the container build itself (we could actually test it with testinfra for validating aspects of the container creation)
• Have a reference pipeline on how to push the container to a registry (either GitHub or https://ttl.sh/)

Also, we could publish it to dockerhub if we want so anyone could pull the image for validating the working architecture.

If someone chooses to use some container scheduler in the future, this someone would just need to track the container registry for having updates (Ex.: ArgoCD).

from fastapi-nano.