by mounting the api first with the frontend-data as a shared volume, docker will copy the contents of the frontend to the shared volume.
this is a wip because i tested it quickly and seemed to work, but traefik was down for some reason and i ran out of time today!
by mounting the api first with the frontend-data as a shared volume, docker will copy the contents of the frontend to the shared volume.
this is a wip because i tested it quickly and seemed to work, but traefik was down for some reason and i ran out of time today!
Oh interesting but I'm not sure you can rely on the ordering of the services in the compose file? I could be wrong. That's a cool trick if it works! It may be possible to use some sort of "depends on" config for this also? Unsure.
Oh interesting but I'm not sure you can rely on the ordering of the services in the compose file? I could be wrong. That's a cool trick if it works! It may be possible to use some sort of "depends on" config for this also? Unsure.
Ah, dependency may work. I'll try it. For what I've seen so far the files were copied, even if the abra output showed a seemingly random order:
INFO creating funkwhale_coopcloud_sutty_local_celerybeat
INFO creating funkwhale_coopcloud_sutty_local_db
INFO creating funkwhale_coopcloud_sutty_local_cache
INFO creating funkwhale_coopcloud_sutty_local_api
INFO creating funkwhale_coopcloud_sutty_local_app
INFO creating funkwhale_coopcloud_sutty_local_celeryworker
Ah, dependency may work. I'll try it. For what I've seen so far the files were copied, even if the abra output showed a seemingly random order:
```
INFO creating funkwhale_coopcloud_sutty_local_celerybeat
INFO creating funkwhale_coopcloud_sutty_local_db
INFO creating funkwhale_coopcloud_sutty_local_cache
INFO creating funkwhale_coopcloud_sutty_local_api
INFO creating funkwhale_coopcloud_sutty_local_app
INFO creating funkwhale_coopcloud_sutty_local_celeryworker
```
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
by mounting the api first with the frontend-data as a shared volume, docker will copy the contents of the frontend to the shared volume.
this is a wip because i tested it quickly and seemed to work, but traefik was down for some reason and i ran out of time today!
Oh interesting but I'm not sure you can rely on the ordering of the services in the compose file? I could be wrong. That's a cool trick if it works! It may be possible to use some sort of "depends on" config for this also? Unsure.
Ah, dependency may work. I'll try it. For what I've seen so far the files were copied, even if the abra output showed a seemingly random order:
25d82584b4toa97746b191This works!
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.