You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using the project without cloning the repo would be significant, something like docker pull inb and then docker run inb ....
The experience nowadays is already better than needing to install Python manually. However, users still have to clone the repo, which adds friction to the usage and popularization of this tool.
We could publish a docker image straight away, and the users would pull it without cloning the repo or needing the source code to run the project.
as MVP: I can clone/build/publish the image directly under the inb name and update the README.md, adding new instructions to use the project without cloning the repo.
This adds great value already, as we'd have the value for the users to pull from Docker straightaway. The issue with this is that it adds manual work.
We should add a GitHub action to publish the image at every push. I wouldn't say we need to run to do this, as we don't have releases/changes often.
The text was updated successfully, but these errors were encountered:
Using the project without cloning the repo would be significant, something like
docker pull inb
and thendocker run inb ...
.The experience nowadays is already better than needing to install Python manually. However, users still have to clone the repo, which adds friction to the usage and popularization of this tool.
We could publish a docker image straight away, and the users would pull it without cloning the repo or needing the source code to run the project.
as MVP: I can clone/build/publish the image directly under the
inb
name and update theREADME.md
, adding new instructions to use the project without cloning the repo.This adds great value already, as we'd have the value for the users to pull from Docker straightaway. The issue with this is that it adds manual work.
We should add a GitHub action to publish the image at every push. I wouldn't say we need to run to do this, as we don't have releases/changes often.
The text was updated successfully, but these errors were encountered: