Closed DrSeussFreak closed 7 years ago
This isn't a bug. It is your configuration. Which guide did you follow?
I followed https://github.com/nZEDb/nZEDb/wiki/Install-Guide:-Windows-using-XAMPP, which I have been updating
From a brief look at that guide, it has a number of problems. However I haven't used Windows in a few years and XAMPP never, so I wouldn't want to edit it myself.
Can you let me know what the issues are, and I can update it as I get it working? That is what I've been doing thus far.
1) It only deals with 32 bit versions. Nature of usenet indexing requires 64 bit integers, and files can go over 2GB (limit of 32 bit). 2) The vhost is way out of date, see the Ubuntu guide for one more upto date. 3) 'Create a file here: "d:\www\nZEDb\nzedb-update.bat"' This is a bad Idea as we have a command built in to do this (./zed update nzedb). Also, in a previous step it checked for git being in path, so hard-coding it isn't needed. 4) Adding the alias to apache vhost would not be needed if it was in the initial file at the top like in the Ubuntu guide
Ok, doing what I was trying to avoid, creating a new Windows Install without XAMPP or WAMP and just installing all of the components manually.
Setting it up manually is always the best option. If you are on Windows 10, you can use the BASH shell integration (from the anniversary update) to do it almost identically to Ubuntu. I haven't tried this as I do not have a machine with Windows installed as primary OS, but as I understand the BASH integration for Win10, it provides you with apt-get so you can follow the Ubuntu 16.04 guide. Alternatively create an Ubuntu VM. Honestly, the Linux setup is by far the best solution, (as that is how it is designed to work) so use it where/how ever you can.
I tried 1 last time with WAMP (which unlike XAMPP, does have a 64-bit flavor), and was able to get it working without issue (thus far). I created yet another new page to document it, it is https://github.com/nZEDb/nZEDb/wiki/Install-Guide:-Windows-using-WAMP. Fingers crossed it remains functional.
Expected behaviour
Script updates binaries as expected
Actual behaviour
The error then repeats a lot, and finally fails with
Steps to reproduce the behaviour
run php update_binaries.php