Closed fostermh closed 4 years ago
I suppose that most people when they run docker-compose expect it to use docker-compose.yml. So defaulting to another file would lead to confusion IMO. I would rather prefer to use docker-compose -f docker-cloud.yml up explicitly... Or create a docker-compose.local.yml file and rename docker-cloud.yml with docker-compose.yml
I suppose that most people when they run docker-compose expect it to use docker-compose.yml. So defaulting to another file would lead to confusion IMO. I would rather prefer to use docker-compose -f docker-cloud.yml up explicitly... Or create a docker-compose.local.yml file and rename docker-cloud.yml with docker-compose.yml
hmm, yes I can see how that could be an issue. Both of your suggestions would work. My thinking is to make it as easy as possible for someone to get an initial system running. To that end, I have a slight preference for renaming the docker-compose files. Do you have a strong preference either way?
No preference. Renaming the compose files sounds good.
To build ckan and other containers:
you will need to reindex datasets and harvester as this will restart solr