Recipes

recipes are the most critical component of bytes bakery, they determine how and what your image get's baked with; from the name all the way down to shell scripts you will want to run image name non unique user friendly name that is used to generate this name carries through to the baked image and is appended with the utc timestamp at the time of baking when viewing baked images in your project look for example image 07 17 2019 12 42 12 145069 gcp project id the project id https //support google com/googleapi/answer/7014113?hl=en of your gcp (google cloud platform) project pushing baked images to your project requires iam permissions https //cloud google com/iam/docs/overview to be configured ( see required permissions https //docs bytesbakery com/pushing images directly to your project ) this field is disabled for the free tier and defaults to bytes bakery public if left blank recipe description brief description of the contents of your recipe ssh compiance monitoring an open source script https //github com/bigcosmallco/cloud compliance by bigco smallco that will automatically label your vm instances upon ssh login shell script upload shell script to be ran during the image building process here is where you will find additional instruction on our default entrypoint base image bases images are pulled directly from gcp at the time of creation we pull the images into our system to maintain a proper versioning of your recipes with exact base image versions anytime you update your recipe currently we only support ubuntu family images, you can refer to the full list of images here https //cloud google com/compute/docs/images which we aim to support in the near future packages list the packages you'd like to install here seperated by a comma, they will be installed in order before the your uploaded script is ran alternatively you can include your package installations in your shell script