Closed wu-lee closed 4 years ago
I think someone @wu-lee @dtmakm27 said that there was still something to do to make this usable? Something to do with a token? Or was it just that the ReadMe needed to be updated?
need to update documentation *
Shall we create a new issue in the new repository, to redo the documentation for building a database, and close this one? It can wait until March.
Yes, I'll write up something short for now but will make a proper one later We can close this one
I tried to use the open-data
repo and it seems to be missing some things. I don't know if there's a new ticket for that but adding that here. @dtmakm27 perhaps you can make sure this gets copied into the right place?
* it now needs an API key before you can build anything (that should probably go into an encrypted store?)
Why would one need an API key?
Why would one need an API key?
I'm not sure, seems to be something to do with the OpenCage. Running this:
make -f ../../tools/se_open_data/makefiles/generate.mk edition=experimental
Fails with:
tools/se_open_data/lib/se_open_data/csv/open_cage_standard.rb:27:
in `read': No such file or directory @ rb_sysopen - ../APIs/OpenCageKey.txt (Errno::ENOENT)
seems to be something to do with the OpenCage Of course. Essential for generating long/lats for no UK Postcode available. @dtmakm27, it should be an option as not always needed.
Dean's given me the missing files, so I can use this now. However these may need to be committed somewhere suitable (i.e. maybe not here), will look into it.
Note, the OpenCage.txt API key now committed in encrypted form here:
https://github.com/SolidarityEconomyAssociation/password-store/blob/master/OpenCageKey.txt.gpg
I propose the ruby script grab it from there by shelling out to the pass
command as appropriate? This however requires that the pass
command has been set up correctly beforehand and the user has a passphrase to a GPG key with access.
I have put in the required documentation.
There are some files we are passing on from person to person for now. I have put that in the documentation as well but it would be best to include a person to email in this sentence:
"To get these files request them from the current developers or the project manager."
Should we put in your email @ColmMassey
After we decide this we can close this issue
Let's create an alias for the moment lod@solidarityeconomy.coop? Put any further documentation updates you think are required in here
lod@solidarityeconomy.coop now redirects to all of us for the moment.
Actually best to stay within Github and use Issues to communicate. Updated docs here to explain.
This is now in the new repository open-data