(Oh and worth pointing out that RAM allocated is definitely a
consideration! If you are using docker on your local machine, you may be
surprised by how little RAM and CPU gets allocated to the docker host by
default)
On 8 August 2018 at 09:42, Ben O'Steen wrote:
> I've been hitting someth
I've been hitting something similar. I've noticed that the package.json
file is not created or copied over when you run "arches-project create
...". I'm just learning the project so do not know that this is by design,
and whether this should be done manually. I fixed my dev site by copying
over
those results I think that the
> SQL may be the trickiest to remedy. At any rate, a very good roadmap for an
> initial security update.
>
> Adam
>
> On Mon, Dec 17, 2018 at 5:07 PM Ben O'Steen wrote:
>
>> I ran the project through the Bandit 'security linter' which fl
I ran the project through the Bandit 'security linter' which flagged up a
number of small issues https://pypi.org/project/bandit/ I've attached the
result of this in case it is of interest (run on 4.3.1 so obviously run it
against whatever you plan to deploy).
It is just one tool to use to help
Did this fix it? I'm also interested in adding analytics to Arches!
Ben
On Sun, 25 Nov 2018 at 12:17, Vincent Meijer
wrote:
> Found the potential culprit: I need to add www.google-analytics.com to
> my Content Security Policy ('script-src') directive.
> I'll update here once I am able to test
at something unforeseen has popped up, post bugfix.
>
> Adam
>
> On Tue, Nov 27, 2018 at 10:29 AM Ben O'Steen wrote:
>
>> Did this fix it? I'm also interested in adding analytics to Arches!
>>
>> Ben
>>
>>
>> On Sun, 25 Nov 2018 at 12:17, Vincent Meij
pril 2019 19:12:12 UTC+1, Ben O'Steen wrote:
>
>> I can confirm I hit the same issue and error running 'python manage.py es
>> index_database'. I hadn't filed an issue about it as I too had just
>> upgraded ES in my environment too and wanted to eliminated operator error
&g
root/ENV/local/lib/python2.7/site-packages/elasticsearch/connection/base.py",
line 125, in _raise_error
raise HTTP_EXCEPTIONS.get(status_code, TransportError)(status_code,
error_message, additional_info)
elasticsearch.exceptions.RequestError: RequestError(400,
u'parsing_exception', u'reques
I can confirm I hit the same issue and error running 'python manage.py es
index_database'. I hadn't filed an issue about it as I too had just
upgraded ES in my environment too and wanted to eliminated operator error
first. The command that seems to be the root of the issue was:
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
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
gt; both my deployment working and django to spit out a traceback, otherwise I
> would give up more info)
>
> I'm happy to start this as another thread if this is better suited.
> --
> Matthias
>
>
>
> On Tue, 16 Apr 2019 at 10:12, Ben O'Steen wrote:
>
>> I sho
ith more permissions than me could check the webhook
> settings in the Github repo? :)
>
> Vincent
>
> On Fri, Apr 19, 2019 at 12:40 AM Ben O'Steen wrote:
>
>>
>> - 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
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 sur
hes/builds/88c8a09d-9fa6-44f5-a86a-fc960ba2f327
On Tue, 23 Apr 2019 at 08:23, Ben O'Steen wrote:
> 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
endent 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 container doesn't qui
Sorry to hear that you have had trouble! If you just want to test it out, I
agree with Adam that the demo installation is a good option. The direct
link to that is http://v4demo.archesproject.org/
Ben
On Wed, 10 Apr 2019 at 12:23, Adam Cox wrote:
> Hello, the error you found won't be
Putting aside whether this code should be run or not, the error is a
parsing error concerning the python 2 style of string formatting when run
within python 3 which no longer supports this way of print formating. print
is a function in python 3 and should be in the form print(...) not print
""
Hi,
I think the key error is on line 63 of the gist you posted. For some
reason, it is interpreting file bind mount as a directory and not as a
file. If I run the default docker compose file here, and start up the db
container, this is the log output I get:
$ docker logs db
Add rule to pg_hba:
ms it still has some rough edges. As
> I need to get some development done to make some slides for a conference
> paper, I think I'll go back to the tried and tested method of setting up a
> Vagrant VM!
>
> Cheers
> David
>
> On Wednesday, 4 March 2020 00:33:38 UTC, Ben
20 matches
Mail list logo
