As it currently stands we use the upstream all-in-one image, which contains caddy, postgres, celery and redis. These can all be externalized, and there's seperate images for the celery, frontend and app containers also packaged by upstream. We could reroll the recipe if required with the various layers separated and our own redis and postgres image choices, and it'd probably be lighter weight.
As it currently stands we use the upstream all-in-one image, which contains caddy, postgres, celery and redis. These can all be externalized, and there's seperate images for the celery, frontend and app containers also packaged by upstream. We could reroll the recipe if required with the various layers separated and our own redis and postgres image choices, and it'd probably be lighter weight.
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.
As it currently stands we use the upstream all-in-one image, which contains caddy, postgres, celery and redis. These can all be externalized, and there's seperate images for the celery, frontend and app containers also packaged by upstream. We could reroll the recipe if required with the various layers separated and our own redis and postgres image choices, and it'd probably be lighter weight.
#2