https://github.com/archesproject/arches/pull/4801
I've put my small tweak as a PR, if you wanted to check it out Vincent and
test yourself!
Ben
On Wed, 24 Apr 2019 at 10:44, Ben O'Steen wrote:
> Rob G had similar issues running the test suite, but had an extra fail as
> well! Not sure what is g
Rob G had similar issues running the test suite, but had an extra fail as
well! Not sure what is going on but I think some tests need looking at
possibly!
Ben
On Wed, 24 Apr 2019 at 05:13, Vincent Meijer
wrote:
> Nice!
> Sounds like that is a regular assertion error and independent of the
> env
Nice!
Sounds like that is a regular assertion error and independent of the
environment, or does the test succeed locally?
On Tue, Apr 23, 2019 at 6:46 PM Ben O'Steen wrote:
> Good news, Bad news I'm afraid:
>
> Good news? the environment flag seems to have done the trick and the
> Elasticsearch
Good news, Bad news I'm afraid:
Good news? the environment flag seems to have done the trick and the
Elasticsearch container doesn't quit after running its checks.
Bad news? There is a failing test:
FAIL: Test bulk deleting of documents in Elasticsearch
--
That is an odd error, certainly works locally but not when docker hub runs
the test setup.
One thing it could be is that if docker hub are using default EC2
instances, they have the vm.max_map_count set too low for Elasticsearch. It
is high enough that Elasticsearch will boot but not enough to sto
It seems there are problems with our automated docker builds, which is
presumably the cause of the 4.4.1 tag not existing.
Latest build of the master branch failed: the Elasticsearch endpoint cannot
be reached during the unit tests.
Failed to establish a new connection: [Errno -2] Name or service
- As for Docker 4.4.1 not being put onto Docker Hub, I'm not sure why that
is. I've been making my own images of the codebase in lieu of that.
- I don't get the System settings errors you mention, though I am using
Arches based on a much more recent codebase (I created my Arches base image
last we
Thanks Ben,
That was useful, I guess I got confused between DEV mode 8000 and PROD port
80, I got it to work now.
2 followup questions; now that I can see the website and login:
- I see on dockerhub that 4.4.1 has not been published; is that expected
?
- once logged-in I can't seem to access
I should also make it clear that all of what I mentioned above is the
default behaviour and doesn't need you to do anything more to make it work.
--
-- To post, send email to archesproject@googlegroups.com. To unsubscribe, send
email to archesproject+unsubscr...@googlegroups.com. For more inform
How the static files are served depends on a few things. What is the
DJANGO_MODE variable set to in the docker-compose.yml that you are using?
(NB if you also have an .env file in that directory, that may be
overwriting this issue)
If it is PROD, then the command to collect static files should cop
Hello,
I am trying to deploy Arches for our local institution, I'm trying to go
through the instruction [1], on how to run in docker.
Most instruction appear to work so far (a couple of couchdb and
elasticsearch warning which I'm going to assume are for first run,
But when accessing the loca
11 matches
Mail list logo
