OpenSextant / OpenSextantToolbox

A geotagger and entity extractor
Other
15 stars 7 forks source link

Added ability to deploy OST to cloud foundry #18

Closed haleystorm closed 8 years ago

haleystorm commented 8 years ago
dlutz2 commented 8 years ago

Looks good to me and Travis says OK. Travis and I can't test the CF deployment so if it works for you must be good. In 3.0, I will move all scripts to /bin (unless CF will complain about other stuff there), no reason to have two dirs.

haleystorm commented 8 years ago

CF complains if the other scripts are in /bin. However, CF doesn't care if both the /bin and /scripts exist as long as /bin only contains the one runnable.

Should I remove release-pcf target from the ant build and just create both /bin and /scripts? It seems weird to have both. Thoughts?

haleystorm commented 8 years ago

I didn't test the CF deployment with the full gazetteer. Turns out that the resulting zip file is too large to push. CF has a 1G limit on app package sizes. Will need to explore running with an external solr instance.

dsmiley commented 8 years ago

Couldn't the data be loaded separately somehow? Disclaimer: I know nothing of CF but have been learning Docker.

haleystorm commented 8 years ago

I'm new to CF and haven't found a way to share resources with a application but... I should be able stand up a solr server on cf and load the gazeteer into that and it looks like I can set solr.home in OpenSextant to a url.

dlutz2 commented 8 years ago

Having a separate ant target for the CF build is OK. If CF is picky about other stuff in bin best keep both /bin and /scripts. Haven't tried the separate Solr instance for a while. I know the throughput drops sharply. Let me know how it goes.

haleystorm commented 8 years ago

Yay. I have a working Solr instance and OpenSextant in CF can reach it. Going to open another pull request. I'm hoping the throughput won't be an issue but will keep an eye on it. Thanks.