[Loris-dev] LORIS - v21.0.3 (Ubuntu Base 16.04.6) - CRU

[Dave MacFarlane]

The Makefile uses git to generate the VERSION file based on what's checked
out. Since it looks like you didn't get the code via git, you can trick it
into skipping that step by manually creating a file named "VERSION" in the
root of the LORIS directory so that it thinks it's already up to date.

Regarding your follow up email: you should run `make` with no arguments in
the root of your LORIS directory. If you get the "No targets specified"
error when in the correct directory try "make all" (most versions of make
that I'm aware of use the first target from the Makefile if no argument is
specified, but "make all" is explicit.)

(You should also make sure that you have: 1. composer and 2. npm installed
with a recent enough version according to the README, or the make step will
likely fail.)

- Dave

On Thu, Nov 14, 2019 at 2:30 PM Matthew Sparks, Mr <matthew.sparks at mcgill.ca>
wrote:

> Well obviously there was no file; lol sorry. How to proceed with this?
>
>
>
> root at ubuntu-s-1vcpu-2gb-tor1-01:/var/www/loris# make
>
> git describe --tags --always > VERSION
>
> fatal: not a git repository (or any of the parent directories): .git
>
> Makefile:8: recipe for target 'VERSION' failed
>
> make: *** [VERSION] Error 128
>
>
>
> Matthew
>
>
>
> *From:* Matthew Sparks, Mr
> *Sent:* Thursday, November 14, 2019 2:27 PM
> *To:* Dave MacFarlane <dave.macfarlane at mcin.ca>
> *Cc:* loris-dev at bic.mni.mcgill.ca
> *Subject:* RE: [Loris-dev] LORIS - v21.0.3 (Ubuntu Base 16.04.6) - CRU
>
>
>
> Great, thanks. Everytime I run this command I receive the following;
>
> -          make: *** No targets specified and no makefile found
>
>
>
> Dependency related no doubt?
>
>
>
> Best,
>
> Matthew
>
>
>
> *From:* Dave MacFarlane <dave.macfarlane at mcin.ca>
> *Sent:* Thursday, November 14, 2019 2:17 PM
> *To:* Matthew Sparks, Mr <matthew.sparks at mcgill.ca>
> *Cc:* loris-dev at bic.mni.mcgill.ca
> *Subject:* Re: [Loris-dev] LORIS - v21.0.3 (Ubuntu Base 16.04.6) - CRU
>
>
>
> In that case. you're missing the equivalent step of the install process
> (run `make` for production or `make dev` for a sandbox which invokes
> composer.)
>
>
>
> There was a bug in the initial 21.0.0 release where that step wasn't
> properly documented, so it's easy to have missed but it should be listed as
> step 4 in the README as of v21.0.3.
>
>
>
> On Thu, Nov 14, 2019 at 1:59 PM Matthew Sparks, Mr <
> matthew.sparks at mcgill.ca> wrote:
>
> Sorry if I was unclear. I’m not upgrading. I have more than one instance
> of Loris running. The v17 version will be made dormant once the latest v21
> clean install works. I would like to port a few modules from the working
> v17 to the latest. Otherwise, I have 10+ point-release iterations to
> updates to make.
>
>
>
> -Matthew
>
>
>
>
>
> *From:* Dave MacFarlane <dave.macfarlane at mcin.ca>
> *Sent:* Thursday, November 14, 2019 1:56 PM
> *To:* Matthew Sparks, Mr <matthew.sparks at mcgill.ca>
> *Cc:* loris-dev at bic.mni.mcgill.ca
> *Subject:* Re: [Loris-dev] LORIS - v21.0.3 (Ubuntu Base 16.04.6) - CRU
>
>
>
> When upgrading, it's required to be on the latest minor release and to go
> one release at a time. If you go to https://github.com/aces/Loris/releases
> there should be an "Upgrade process" section for each release that you
> should follow in order from 17. The error (that it can't find the autoload
> file generated by composer) seems to suggest you missed step 2 of the
> upgrade process to LORIS v21.
>
>
>
> - Dave
>
>
>
> On Thu, Nov 14, 2019 at 1:39 PM Matthew Sparks, Mr <
> matthew.sparks at mcgill.ca> wrote:
>
> Hi Dave,
>
>
>
> Certainly, my apologies for not attaching them initially.
>
>
>
> Best,
>
> Matthew
>
>
>
> *From:* Dave MacFarlane <dave.macfarlane at mcin.ca>
> *Sent:* Thursday, November 14, 2019 1:34 PM
> *To:* Matthew Sparks, Mr <matthew.sparks at mcgill.ca>
> *Cc:* loris-dev at bic.mni.mcgill.ca
> *Subject:* Re: [Loris-dev] LORIS - v21.0.3 (Ubuntu Base 16.04.6) - CRU
>
>
>
> Hi Matthew,
>
>
>
> Do you have access to the web server's error log on Digital Ocean? It's
> difficult to guess why it's generating a 500 error without seeing the error
> log.
>
>
>
> - Dave
>
>
>
> On Thu, Nov 14, 2019 at 1:30 PM Matthew Sparks, Mr <
> matthew.sparks at mcgill.ca> wrote:
>
> Hello Loris Devs,
>
>
>
> I have just installed a new loris instance on the DigitalOcean platform
> and post-install I receive a HTTP 500 Error.
>
>
>
> Please advise and see the screenshot attached;
>
> -          To troubleshoot; From the dev instance you can see that I’ve
> granted excessive permissions beyond what is needed, and the *issue
> persists*.
>
>
>
> Currently;
>
> -          Functional Loris *v17* instance running on DO.
>
> -          Non-functional Loris *v21.0.3 (.1-3)* instance running on DO.
>
>
>
> Nice to have;
>
> -          DigitalOcean application for rapid reployment.
>
> -          Up-to-date Loris install guide (e.g., deprecation of
> python-properties-common etc)
>
>
>
> I can re-initialize the DO base and provide you with root credentials for
> a quick install to loris v21.0.3?
>
> -          Ultimately, we need to be able to use the *DQT*.
>
>
>
> Any suggestions to resolve the issue would be appreciated
>
>
>
> Kindest regards,
>
> Matthew
>
> _______________________________________________
> Loris-dev mailing list
> Loris-dev at bic.mni.mcgill.ca
> https://mailman.bic.mni.mcgill.ca/mailman/listinfo/loris-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.bic.mni.mcgill.ca/pipermail/loris-dev/attachments/20191114/615f1e13/attachment-0001.html>