Data Uploads Not Working

[mheadd]

When I create a new CKAN instance under CKAN Multisite and begin to add data I encounter a problem.

The link to the resource points to localhost at the specific internal port the instance is running on. So users won't be able to download it (because its not on their localhost).

In addition, and I think this problem is related to the above, the load into the datastore is failing.

[waldoj]

Interesting! I'm puzzled as to why I didn't encounter this myself. Coincidentally, I'm in the middle of a deployment myself. I'll test this immediately and see if I can reproduce.

[deniszgonjanin]

Oh, this seems to be a problem with the site_url setting in CKAN not being set properly. But I wonder why that is...

[mheadd]

Hmm, if it matters - I changed the HOSTNAME setting in ckan_multisite/config.py after my initial install. I first used an IP address allocated from Amazon, but once it installed and I wanted to create some site I registerd a proper URL and added it there.

Everything seemed to work OK after this change. Possible that this might have caused it?

[mheadd]

@waldoj Interested to see if you can reproduce this.

[JackMc]

Ok, what's going on here is that the site_url setting isn't set.

[waldoj]

Ah-ha—I've only ever tested CKAN Multisite with a domain name, never at an IP address. That might explain things.

[mheadd]

I'm using a domain name now, but during the install process I used an IP. All of the sites that I have created since seem to work fine at the domain name, except for this issue.

[waldoj]

(I'm having permissions problems right now, so I haven't been able to create a site to try uploading data just yet. Damn my accidental sudo.)

[JackMc]

I have this fix ready now - but it seems to have caused some other symptoms. I'll have to look into that before pushing it to master

[mheadd]

Just curious if there was any update on this issue. Thanks!

[JackMc]

Sorry - I had two branches that were one branch but now I will make a PR for review!

[JackMc]

HI @mheadd can you try out #36 and see if it solves your problem? You'll need to recreate the site.

[mheadd]

Apologies - I haven't been able to test this because of this issue #37.