Setting up a solr index isn’t that hard, but I found the documentation to be somewhat hard to find. It only took me a few hours from start to finish to go from download to indexing my documents, but I think it could have happened a lot faster if I had some of the below information. I’m assuming you’ve already downloaded solr and you’re now looking at a directory with a bunch of files in it.
- If you do any work with single sign on, you’ll be familiar with the concept of exchanging tokens and validating against the authentication server using that token. One of the issues I’ve just run into which resulted in a huge headache is with urlencoding the result of a curl_exec that had a line ending. It’ easy to miss when it’s a longer string and you aren’t paying very close attention. This is a very simple example, and it still takes a second to realize there’s an extra character at the end.
- Let’s get one thing out in the open. Curl is sweet. It does it’s job very well, and I’m absoutely thrilled it exists. If you’re using curl in your PHP app to make web requests, you’ve probably realized that by doing them one after the other, the total time of your request is the sum of all the requests put together. That’s lame. Unfortunately using the curl_multi_exec is poorly documented in the PHP manual.