Oh I see that now, good point. I guess I just got excited about more
incentives to use the ORM.
On Mon, Dec 17, 2018 at 5:38 PM Ben O'Steen wrote:
> It is flagging that the string formatting method is being used to
> construct a SQL query, rather than a method that might escape or encode
> param
It is flagging that the string formatting method is being used to construct
a SQL query, rather than a method that might escape or encode parameters
that may have SQL side-effects.
Ben
On Mon, 17 Dec 2018 at 15:35, Adam Cox wrote:
> Thanks for sharing those results Ben. A number of the issues r
Thanks for sharing those results Ben. A number of the issues raised there
are also a matter of best practices not being followed (like using
non-typed try/except/pass blocks, or calling os.system) so it's good to see
them flagged. Also, though it would be really nice to get away from raw SQL
and re
Hi Enzo, no, I believe you need 9.5. The main reason is that Arches uses
the JSONB postgres datatype.
Adam
On Mon, Dec 17, 2018 at 3:30 PM enzo cocca wrote:
> hi people!
> an fast question:
> is it possible work with postgres 9.3 on arches?
>
> --
> -- To post, send email to archesproject@goog
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 ga
Hi John, I have not had a security audit either, and would be very
interested in the results. I do have a pending deployment for the Bureau of
Land Management which will most likely require an audit, so I'm expecting
to do some prep work on Arches for that at some point.
On Mon, Dec 17, 2018 at 5:
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
hi people!
an fast question:
is it possible work with postgres 9.3 on arches?
--
-- To post, send email to archesproject@googlegroups.com. To unsubscribe, send
email to archesproject+unsubscr...@googlegroups.com. For more information,
visit https://groups.google.com/d/forum/archesproject?hl=en
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
Hi John,
I haven't heard of anyone doing a security audit for Arches, but if so I
would also be quite interested in hearing about it.
Best,
Vincent
On Monday, 17 December 2018 10:49:03 UTC+1, John Murphy wrote:
>
> Good morning everyone!
>
> I was wondering if has anyone has had to commission a
Good morning everyone!
I was wondering if has anyone has had to commission a security audit of
Arches yet and, if so, what have your experiences been? Our corporate IT
are going to require one before they allow me to set this loose on our
network and it would be good to know what I need to look
13 matches
Mail list logo
