MobileRead Forums - View Single Post

MontyJ · 02-03-2017, 01:03 PM

Well, I am losing hair and grinding down the teeth over this QNAP/COPS/Apache thing.

I have had to completely reset the QNAP system 3 times in the last month, simply because I don't know the ramifications of editing various COPS files, Apache conf files, etc. I am a learn-by-doing advocate, but enough is enough!

Much of the problem is me wanting to install cops v1.0.1 over an existing v1.0.0 install. The posts in this thread clearly indicate all you need to do is unzip v1.0.1 and copy the contents into the existing COPS install folder.

For whatever reason, that simply does not work. So my first question is:

What is the benefit of using v1.0.1?

The changelog shows 6 'fixes', none of which seem to be more than cosmetic. So is it a big deal to stick with v1.0.0?

My second question is:

v1.0.0 has a (to me, a real noob) convoluted install in the QNAP in:

Code:

/share/CACHEDEV1_DATA/.qpkg/COPS/COPS

The contents of the first COPS folder is:

Code:

[/share/Web/COPS] # ls -la /share/CACHEDEV1_DATA/.qpkg/COPS
drwxr-xr-x    3 admin    administ      4096 Feb  2 14:53 ./
drwxrwxrwx   12 admin    administ      4096 Feb  3 10:24 ../
-rw-r--r--    1 admin    administ      4505 Feb  2 13:38 .list
-rw-r--r--    1 admin    administ      3861 Jan 11  2015 .qpkg_icon.gif
-rw-r--r--    1 admin    administ      3861 Jan 11  2015 .qpkg_icon_80.gif
-rw-r--r--    1 admin    administ      2401 Jan 11  2015 .qpkg_icon_gray.gif
-rwxr-xr-x    1 admin    administ       762 Feb  2 13:38 .uninstall.sh*
drwxr-xr-x    8 admin    administ      4096 Feb  2 20:18 COPS/
-rwxr-xr-x    1 admin    administ      1697 Jan 11  2015 COPS.sh*
-rw-r--r--    1 admin    administ      1400 Feb  3 10:10 accesCops.htpasswd
-rw-r--r--    1 admin    administ        43 Jan 11  2015 accesCops.htpasswd.org
[/share/Web/COPS] #

The second COPS folder contains all the normal COPS files and sub-folders, and appears to be "simlinked" to /share/Web/COPS.

So, if I do copy v1.0.1 files/folders into /share/Web/COPS, how about the "index.php" file that comes with v1.0.1? Should I copy it into the /share/Web folder over the original v1.0.0 version?

I really am trying to make this work. I gave up on QApache, which supposedly had better logging options, and am trying to make this work with plain old Apache and .htaccess.

I am frustrated that to me, this is so obtuse. It is as if it was all aimed at web designers, CNE's or php/json coders. By that I mean if a .qpkg is made for v1.0.0, why isn't v1.0.1 updated with a .qpkg. I realize the developer has larger fish to fry, but if it is supported and new versions released, why force noobs like me to lose more hair trying to dig into the install minutia to make the dang thing work? I really don't have that much hair to lose...

Sorry for venting, but there it is. The actual questions above are few, but any tips/hints at all might point me to a solution.

Thanks!

02-03-2017, 01:03 PM	#1444
MontyJ Addict Posts: 224 Karma: 10 Join Date: Jul 2012 Device: Kindle	Well, I am losing hair and grinding down the teeth over this QNAP/COPS/Apache thing. I have had to completely reset the QNAP system 3 times in the last month, simply because I don't know the ramifications of editing various COPS files, Apache conf files, etc. I am a learn-by-doing advocate, but enough is enough! Much of the problem is me wanting to install cops v1.0.1 over an existing v1.0.0 install. The posts in this thread clearly indicate all you need to do is unzip v1.0.1 and copy the contents into the existing COPS install folder. For whatever reason, that simply does not work. So my first question is: What is the benefit of using v1.0.1? The changelog shows 6 'fixes', none of which seem to be more than cosmetic. So is it a big deal to stick with v1.0.0? My second question is: v1.0.0 has a (to me, a real noob) convoluted install in the QNAP in: Code: /share/CACHEDEV1_DATA/.qpkg/COPS/COPS The contents of the first COPS folder is: Code: [/share/Web/COPS] # ls -la /share/CACHEDEV1_DATA/.qpkg/COPS drwxr-xr-x 3 admin administ 4096 Feb 2 14:53 ./ drwxrwxrwx 12 admin administ 4096 Feb 3 10:24 ../ -rw-r--r-- 1 admin administ 4505 Feb 2 13:38 .list -rw-r--r-- 1 admin administ 3861 Jan 11 2015 .qpkg_icon.gif -rw-r--r-- 1 admin administ 3861 Jan 11 2015 .qpkg_icon_80.gif -rw-r--r-- 1 admin administ 2401 Jan 11 2015 .qpkg_icon_gray.gif -rwxr-xr-x 1 admin administ 762 Feb 2 13:38 .uninstall.sh* drwxr-xr-x 8 admin administ 4096 Feb 2 20:18 COPS/ -rwxr-xr-x 1 admin administ 1697 Jan 11 2015 COPS.sh* -rw-r--r-- 1 admin administ 1400 Feb 3 10:10 accesCops.htpasswd -rw-r--r-- 1 admin administ 43 Jan 11 2015 accesCops.htpasswd.org [/share/Web/COPS] # The second COPS folder contains all the normal COPS files and sub-folders, and appears to be "simlinked" to /share/Web/COPS. So, if I do copy v1.0.1 files/folders into /share/Web/COPS, how about the "index.php" file that comes with v1.0.1? Should I copy it into the /share/Web folder over the original v1.0.0 version? I really am trying to make this work. I gave up on QApache, which supposedly had better logging options, and am trying to make this work with plain old Apache and .htaccess. I am frustrated that to me, this is so obtuse. It is as if it was all aimed at web designers, CNE's or php/json coders. By that I mean if a .qpkg is made for v1.0.0, why isn't v1.0.1 updated with a .qpkg. I realize the developer has larger fish to fry, but if it is supported and new versions released, why force noobs like me to lose more hair trying to dig into the install minutia to make the dang thing work? I really don't have that much hair to lose... Sorry for venting, but there it is. The actual questions above are few, but any tips/hints at all might point me to a solution. Thanks!