Migrating from Banana.dev

Hello. I'm trying to migrate a project over. My previous flow was, whenever I wanted to deploy a change, I would run banana deploy, and that would send off the project to be built into an image and deployed. I was unable to really utilize the local image build option as I have limited resources. I've read the migration blog post, but the only option there is for building the image and pushing to a repo. Is there anything similar to banana deploy, where I only need to tweak the Dockerfile a bit and update the handler? Alternatively, I could go the dockerless route, but I'm not seeing any way in that post to specify non-Python requirements. I need access to ffmpeg and a project on GitHub; how would I setup these? And what would be the preferred way to provide API tokens/keys?
Solution:
A few things - there is a tutorial with a little more details than the blog here: https://docs.runpod.io/tutorials/migrations/banana/overview Secondly, if you can't build your docker image (resources limited) use the CLI tool for projects: https://docs.runpod.io/cli/projects/get-started This will "build" your image on our GPU....
Jump to solution
1 Reply
Solution
PatrickR
PatrickR5mo ago
A few things - there is a tutorial with a little more details than the blog here: https://docs.runpod.io/tutorials/migrations/banana/overview Secondly, if you can't build your docker image (resources limited) use the CLI tool for projects: https://docs.runpod.io/cli/projects/get-started This will "build" your image on our GPU. You can replace the docker image inside the config.toml file with any extra requirements you need. Then, to deploy changes to your project, run:
runpodctl project deploy
runpodctl project deploy
Instead of banana deploy and it will start to deploy on your serverless Endpoint. From then on - if you make a change, just rerun that command.