rewrite build scripts to accommodate current releases

[vasyugan]

I think the build script needs to be completely rewritten. The release versions of Uwazi don't require you do build uwazi, they are ready to run. See the description of the install/upgrade procedure here.

Meanwhile I have transitioned to using Uwazi natively rather than dockerized, because this is just way easier. I am not quite sure, that there is a substantial benefit to using docker with the release versions. I'll be archiving my own repository because I haven't been maintaining it it a long while.

[fititnt]

I think the build script needs to be completely rewritten. The release versions of Uwazi don't require you do build uwazi, they are ready to run. See the description of the install/upgrade procedure here.

HUMMM... you're right. I haven't tested this method, but it would at the very least reduce the container creation time.

Meanwhile I have transitioned to using Uwazi natively rather than dockerized, because this is just way easier. I am not quite sure, that there is a substantial benefit to using docker with the release versions. I'll be archiving my own repository because I haven't been maintaining it it a long while.

Fun fact: I actually know very well Ansible, so could do directly on VMs or Bare Metal. Done a few times with other projects here in GitHub. So what you propose is viable to automate, but I'm not sure if would have others using Ansible than manually

[fititnt]

I've already started rewriting the init script. However, one thing I noticed is that, at least for booting with example data, downloading the .tgz files from https://github.com/huridocs/uwazi/releases/ instead of cloning the git repository would not work.

This is why at this moment it was not already using the .tgz, and maybe will not (or at least not unless user just want the blank state.