Yarn seems to be fine. Running* yarn install* generates the following:
> yarn install v1.12.3
> info No lockfile found.
> [1/4] Resolving packages...
> [2/4] Fetching packages...
> [3/4] Linking dependencies...
> [4/4] Building fresh packages...
> success Saved lockfile.
> Done in 0.11s.
>
On Mo
Hi John, it's also possible that yarn did not install all of the node
modules correctly. On the server, can you go into the project and try
running "yarn install"? I'd be curious to know what the outcome is.
On Mon, Dec 17, 2018 at 5:39 AM John Murphy wrote:
> I'm trying to run Arches 4.3 instal
You're right about the 404 errors, there are loads of them. Unfortunately
my settings.py was already set DEBUG = True. There was no MODE flag and
after I tried to add it myself the server refused to run.
On Monday, 17 December 2018 12:29:10 UTC, Vincent Meijer wrote:
>
> This looks like a stati
This looks like a static file issue. Can you see any errors in the console
(in Chrome this is under the menu More Tools -> Developer Tools (or ctrl +
shift + i).
This would happen if in *settings.py *you have the DEBUG setting to False
and/or MODE to PROD (I forgot which one it is).
If you see lot
I'm trying to run Arches 4.3 installed on a DigitalOcean droplet (Ubuntu
16.04.4 x64, 4GB ram, 80GB disk) and I've loaded it with the Arches HIP
sample package. Everything appears to have installed ok and the only change
I needed to make to get things running was to change *settings.py* to
incl
