changing the configuration to get the database connect to the api when it's running inside the cluster is incompatible with the configuration needed to seed the DB from outside the cluster. Once the seed scripts are able to check that the db has not already been seeded ( #24 ) then it will be safe to always run the db seed container as a preinit job of starting up the API from inside the cluster
changing the configuration to get the database connect to the api when it's running inside the cluster is incompatible with the configuration needed to seed the DB from outside the cluster. Once the seed scripts are able to check that the db has not already been seeded ( #24 ) then it will be safe to always run the db seed container as a preinit job of starting up the API from inside the cluster