Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ResourceRegistry: Require a method to read an existing RR datasets #81

Open
3 tasks
birdage opened this issue Jul 7, 2014 · 0 comments
Open
3 tasks

Comments

@birdage
Copy link
Contributor

birdage commented Jul 7, 2014

at present we are presuming that the system will be brought up along side the EOI services, this might not be the case. we could do with a method of bringing up the coi-service separate from the eoi services then sync the dataset resources after the fact.

i think this might be done via a resources registry pass for datasets, then following the model of table loader to generate the resources in postgres and geoserver.

My guess is that this would be request driven, maybe started by importerservice?
This would also be important to run if the data services get out of sync for any reason.

we would test this on the deployed infrastructure (vms) by:

  • preloading a coi-services vm (eoi-dev1) with alpha or beta
  • bring up all eoi services on second instance (test-pg-03)
  • run method to sync the services
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant