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
run_first.sh is performing a docker compose pull but none of the images referenced in the base docker-compose.yml actually exist. This hasn't been an issue for us historically since the images are just built from source as a fallback. The script should be cleaned up to make this process better.
Update the image: references in the base docker-compose file to point to the correct locations in the github package registry
Add a tag to the app and webserver images to allow the above paths to always reference a latest version of a particular image.
Provide an interactive option to allow the user select between pre-built packages (docker compose pull) vs building from source (docker compose build)
Clean up unnecessary steps in the script (build_assets?)
Ideally, a newbie Materia user should be able to use run_first after a fresh clone of the repo with zero problems, regardless of whether they're pulling (faster) or building (better for dev)
The text was updated successfully, but these errors were encountered:
run_first.sh
is performing adocker compose pull
but none of the images referenced in the basedocker-compose.yml
actually exist. This hasn't been an issue for us historically since the images are just built from source as a fallback. The script should be cleaned up to make this process better.image:
references in the base docker-compose file to point to the correct locations in the github package registryapp
andwebserver
images to allow the above paths to always reference a latest version of a particular image.docker compose pull
) vs building from source (docker compose build
)build_assets
?)Ideally, a newbie Materia user should be able to use
run_first
after a fresh clone of the repo with zero problems, regardless of whether they're pulling (faster) or building (better for dev)The text was updated successfully, but these errors were encountered: