This feature enables Nullstone to build and package source code for users without a Dockerfile.
Intended Outcome
Currently, a user must create a Dockerfile, then build and push the image whenever changes are made.
Instead, a user would push source code and Nullstone would use buildpacks to automatically build and push an image.
How it will work?
Currently, users must perform docker build using a Dockerfile, then nullstone push.
Instead, a user would transmit code similar to Heroku:
git remote add nullstone https://git.nullstone.io/<org-name>/<app-name>/<env-name>
git push nullstone main
Nullstone would perform a build using buildpacks that produces a docker image.
That docker image would automatically be pushed.
Open Questions
Should Nullstone automatically deploy a new image to the first environment in the pipeline?
How does a user promote an image from one environment to the next? (Nullstone currently only promotes infra code)
Summary
This feature enables Nullstone to build and package source code for users without a Dockerfile.
Intended Outcome
Currently, a user must create a Dockerfile, then build and push the image whenever changes are made. Instead, a user would push source code and Nullstone would use buildpacks to automatically build and push an image.
How it will work?
Currently, users must perform
docker buildusing aDockerfile, thennullstone push.Instead, a user would transmit code similar to Heroku:
Nullstone would perform a build using buildpacks that produces a docker image. That docker image would automatically be pushed.
Open Questions