Hi Vincent,

Been digging further into the postgres libs.  It seems the dsn and kwargs
in them are getting values from the <project_name>'s settings.py which
contains the default db credentials (postgres; postgis).  Normally, I
assumed it will get it from the arches' settings.py file.

In case I am confusing :) When you browse the container, you would be
landed into \web_root\arches.  Back down, it would be ENV, arches,
<project_name> folders.

Probably I might need a new pull from arches again and work from there.  I
am unsure if my own is corrupted.

Thanks.

Regards,
Lawrence


On Thu, Oct 25, 2018 at 5:30 AM Vincent Meijer <[email protected]>
wrote:

> Ah I can see the image now (in email). Looks like a regular firewall
> misconfiguration.
> Can you show us your current settings?
>
> There is also the option 'Enforce SSL Connection' under 'SSL Settings' in
> your Azure DB. Is this set to Disabled?
>
> And can you connect to it from your local machine if you whitelist your ip
> in that same screen?
>
>
> On Tuesday, 23 October 2018 23:45:06 UTC+2, Lawrence Goh wrote:
>>
>> Hi Vincent,
>>
>> Apologies for another set up question.  Been going everywhere and sadly
>> to nowhere.  We have set up a Azure Database for Postgresql.  We could get
>> the docker compose to create the DB.  But the arches container failed due
>> to some weird network restriction.
>>
>> [image: image.png]
>>
>> I have added IPs to the firewall.  Even having it being from 0.0.0.0 to
>> 255.255.255.255.  The "Allow access to Azure services" is on.
>>
>> Any ideas?
>>
>> Thanks.
>>
>> Regards,
>> Lawrence
>>
>> On Fri, Oct 19, 2018 at 10:32 PM Vincent Meijer <[email protected]>
>> wrote:
>>
>>> Yeah it's a weird choice from Microsoft to do things differently and
>>> arches wasn't prepared for that @...
>>>
>>>
>>>
>>> On Fri, 19 Oct 2018, 11:23 larrygoh84, <[email protected]> wrote:
>>>
>>>> using 4.3.1.  does this mean its a known issue? it doesn't handle the @
>>>> well? :)
>>>>
>>>> -------- Original message --------
>>>> From: Vincent Meijer <[email protected]>
>>>> Date: 10/19/18 10:02 PM (GMT+12:00)
>>>> To: Arches Project <[email protected]>
>>>> Subject: Re: [Arches] Re: Hosting Arches on Azure as a Web App for
>>>> Containers
>>>>
>>>> Which version of Arches are you using?
>>>> I created a PR (for #4099) for this earlier, but it was after 4.3.1 was
>>>> released.
>>>>
>>>> Until the next release you could use the master branch (there are
>>>> docker images built for that in Docker Hub for every new push:
>>>> https://hub.docker.com/r/archesproject/arches/tags/ )
>>>>
>>>> However, if you want something more stable, you are also free to use my
>>>> own arches base images:
>>>> https://hub.docker.com/r/globaldigitalheritage/arches/tags/
>>>> The current tags in there are all based on Arches 4.3.1 and I push a
>>>> new version every time I created some additional functionality / fixes for
>>>> a PR, such as the one with '@' in Azure database names.
>>>>
>>>> Currently the latest I got is globaldigitalheritage/arches:4.3.1.11
>>>>
>>>>
>>>> I use these images as a base in my own Dockerfile
>>>> (as described in step 7 of 'Setting up your own Arches project':
>>>> https://github.com/archesproject/arches/blob/master/docker/Readme.md#setting-up-your-own-arches-project
>>>> )
>>>>
>>>> I recommend to follow these steps to create your own Arches project,
>>>> rather than editing the core Arches app.
>>>>
>>>> Hope this helps!
>>>> Vincent
>>>>
>>>>
>>>> On Friday, 19 October 2018 05:14:57 UTC+2, Lawrence Goh wrote:
>>>>>
>>>>> Hi Vincent,
>>>>>
>>>>> Had you faced this issue before?  We are now trying to connect to
>>>>> Azure DB for Postgresql.  The container log just freezes at Testing if
>>>>> database server is up.. Is it senstive to the @?  thanks.
>>>>>
>>>>> On Friday, October 19, 2018 at 3:03:47 PM UTC+13, Lawrence Goh wrote:
>>>>>>
>>>>>> Hi Vincent,
>>>>>>
>>>>>> Yups.  Was poking around the codes yesterday and had a go with
>>>>>> removing the staticfiles_storage and all went well :)
>>>>>>
>>>>>> Thanks.
>>>>>>
>>>>>> Regards,
>>>>>> Lawrence
>>>>>>
>>>>>> On Thu, Oct 18, 2018 at 9:00 PM Vincent Meijer <[email protected]>
>>>>>> wrote:
>>>>>>
>>>>>>> If I'm understanding you correctly, you want to serve static files
>>>>>>> the 'standard' way (directly from the Arches app using Whitenoise) and
>>>>>>> serve uploaded files from Azure Blob Storage?
>>>>>>> I do the same at the moment. For that, use:
>>>>>>> DEFAULT_FILE_STORAGE='storages.backends.azure_storage.AzureStorage'
>>>>>>> and
>>>>>>> STATICFILES_STORAGE =
>>>>>>> 'whitenoise.storage.CompressedStaticFilesStorage'
>>>>>>>
>>>>>>> (together with the other appropriate settings for Azure and
>>>>>>> Whitenoise, that you probably already have).
>>>>>>>
>>>>>>> Does that make sense?
>>>>>>>
>>>>>>>
>>>>>>> On Wednesday, 17 October 2018 23:04:35 UTC+2, Lawrence Goh wrote:
>>>>>>>>
>>>>>>>> Hi Vincent,
>>>>>>>>
>>>>>>>> Thanks for that link.  Will need to figure to adapt it for Azure
>>>>>>>> use.
>>>>>>>>
>>>>>>>> Besides that, I noticed it loads all the static files into the
>>>>>>>> blob.  Was thinking to have the static files be in the container.  Only
>>>>>>>> push the uploaded 'media files' into the blob.  I guess it doesn't do 
>>>>>>>> that
>>>>>>>> right? :)
>>>>>>>>
>>>>>>>> Thanks.
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>> Lawrence
>>>>>>>>
>>>>>>>> On Thu, Oct 18, 2018 at 2:12 AM Vincent Meijer <
>>>>>>>> [email protected]> wrote:
>>>>>>>>
>>>>>>>>> The collectfast package looks promising:
>>>>>>>>> https://stackoverflow.com/questions/16805232/faster-alternative-to-manage-py-collectstatic-w-s3boto-storage-backend-to-syn
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> -- To post, send email to [email protected]. To
>>>>>>>>> unsubscribe, send email to [email protected]. For
>>>>>>>>> more information, visit
>>>>>>>>> https://groups.google.com/d/forum/archesproject?hl=en
>>>>>>>>> ---
>>>>>>>>> You received this message because you are subscribed to the Google
>>>>>>>>> Groups "Arches Project" group.
>>>>>>>>> To unsubscribe from this group and stop receiving emails from it,
>>>>>>>>> send an email to [email protected].
>>>>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>>>>
>>>>>>>> --
>>>>>>> -- To post, send email to [email protected]. To
>>>>>>> unsubscribe, send email to [email protected]. For
>>>>>>> more information, visit
>>>>>>> https://groups.google.com/d/forum/archesproject?hl=en
>>>>>>> ---
>>>>>>> You received this message because you are subscribed to the Google
>>>>>>> Groups "Arches Project" group.
>>>>>>> To unsubscribe from this group and stop receiving emails from it,
>>>>>>> send an email to [email protected].
>>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>>
>>>>>> --
>>>> -- To post, send email to [email protected]. To unsubscribe,
>>>> send email to [email protected]. For more information,
>>>> visit https://groups.google.com/d/forum/archesproject?hl=en
>>>> ---
>>>> You received this message because you are subscribed to the Google
>>>> Groups "Arches Project" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>> an email to [email protected].
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>> --
> -- To post, send email to [email protected]. To unsubscribe,
> send email to [email protected]. For more
> information, visit https://groups.google.com/d/forum/archesproject?hl=en
> ---
> You received this message because you are subscribed to the Google Groups
> "Arches Project" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- To post, send email to [email protected]. To unsubscribe, send 
email to [email protected]. For more information, 
visit https://groups.google.com/d/forum/archesproject?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Arches Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to