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
{{ message }}
This repository has been archived by the owner on Oct 6, 2021. It is now read-only.
We need an easy way to develop Airship inside Docker. Currently I need three steps per change:
docker-compose rm -vf
docker-compose build airship
docker-compose up
I already have docker-compose aliased to dc, but it's not the commands that's annoying, but a build time. The time is low if composer dependencies are already installed on the host, but it's still quite long.
This is especially important if you're developing Motifs, because you often check whether things are right. Also the above process involves setting it up every time.
We should probably have Docker volumes for all persistent files and not delete the containers + their volumes. If these are persistent, we also don't have to delete the database volume.
The text was updated successfully, but these errors were encountered:
We need an easy way to develop Airship inside Docker. Currently I need three steps per change:
docker-compose rm -vf
docker-compose build airship
docker-compose up
I already have
docker-compose
aliased todc
, but it's not the commands that's annoying, but a build time. The time is low if composer dependencies are already installed on the host, but it's still quite long.This is especially important if you're developing Motifs, because you often check whether things are right. Also the above process involves setting it up every time.
We should probably have Docker volumes for all persistent files and not delete the containers + their volumes. If these are persistent, we also don't have to delete the database volume.
The text was updated successfully, but these errors were encountered: