-
Notifications
You must be signed in to change notification settings - Fork 108
Support pulling code.json from an agency's organization github.io page #238
Comments
Another item to think about. Even if it was easy to post something to https://www.iad.gov, it uses an SSL certificate issued by a DoD CA. Can the retrieval mechanism handle that? This issue doesn't exist for https://www.nsa.gov since it uses a commercial SSL certificate. |
We are hosting GSA's code.json at a different website by using a HTTP redirect. This way, the main agency website only needs to be updated once to implement the redirect. Code.gov honors the redirect and pulls code.json from the appropriate site. This approach might be useful for scenarios like yours. |
If establishing legitimacy is part of the problem, then you can see that https://github.com/iadgov is linked from the upper right corner of https://www.iad.gov/iad/index.cfm |
@jfredrickson5 I guess I don't see the point of additional hoop jumping like that even if it technically works. I also can't assume the people running the web site will do that for us either. |
+1 on the redirect suggestion. That facilitates automated updates of the machine-readable content that shouldn't require website administrators to review and approve, anyway. A similar approach is already used for data.json files. |
Hello everybody. Code.gov dev here. As @jfredrickson5 stated some months ago, the code.gov harvester follows proper redirects (HTTP 301 and 302). If you are doing the "redirect" via javascript by using |
@iadgovuser1 , is this still an issue? |
@DanielJDufour Let me check with some folks who visited there recently. I know this topic was brought up. |
There's a comment in #183 that I think deserves its own issue. Getting files updated on official agency web sites is a herculean effort especially if it is updated often. It would be great if official agency GitHub organizations could host the code.json file under their main github.io page. For example:
The text was updated successfully, but these errors were encountered: