Putting it under MarkLogic server (#12) was an interesting exercise, but it is no good. The MarkLogic server on AWS is too expensive! Plus, I think, it makes it too difficult for someone else who wants to deploy it locally, so they can work on development, to run it.
So I am re-porting it to exist-db. I just figured out all the server configuration needed, and now it is just a matter of porting all the MarkLogic dependencies.
The other reason is, of course, #13: nightmare problem that I'm completely stumped by.
Putting it under MarkLogic server (#12) was an interesting exercise, but it is no good. The MarkLogic server on AWS is too expensive! Plus, I think, it makes it too difficult for someone else who wants to deploy it locally, so they can work on development, to run it.
So I am re-porting it to exist-db. I just figured out all the server configuration needed, and now it is just a matter of porting all the MarkLogic dependencies.
The other reason is, of course, #13: nightmare problem that I'm completely stumped by.