Hello Antoine,

I wanted to write to let you know that Arches for Science (and everything 
in that repo) is still in development and an initial release of Arches for 
Science is scheduled for Summer 2021. I realize that the Roadmap and 
Releases <https://www.archesproject.org/roadmap/> page on the Arches 
website had said that it would be released this month (January 2021), but 
after seeing your post, I promptly updated the release date on that page to 
reflect the revised target date. We do our best to maintain the Arches 
website with the latest information, but realize that we could do better in 
making sure that it is as up-to-date as possible. We apologize if the 
outdated information misled you. 

Regarding the rest of your post on installation, I don't have anything to 
add since that's not where my expertise lies, but I do hope that others 
will chime in with some guidance.

All the best,
Annabel


Annabel Lee Enriquez
Associate Project Specialist
Arches Project Team
Getty Conservation Institute

On Tuesday, January 5, 2021 at 4:14:19 AM UTC-8 [email protected] wrote:

> Hi,
>
> For testing purposes on an ongoing project, we'd like to install Arches on 
> a webserver (first, having a running instance on a localhost would be 
> great, it's the last service missing on my stack).
>
> Since my github <https://github.com/archesproject/arches/issues/6973> 
> post, I found the upgrades notes in the 5.1 patch note, the google group, 
> the arches-for-science repo and that the arches docker-install was 
> obsolete. Then I decided to give a go to AFS as I struggled with standard 
> arches).
>
> *To reproduce*
> 1. Clone Arches and AFS Repo
> .
> ├── afs
> │   ├── Dockerfile
> │   ├── README.txt
> │   ├── __init__.py
> │   ├── afs
> │   ├── docker
> │   ├── docker-compose.yml
> │   ├── manage.py
> │   ├── pyproject.toml
> │   └── yarn.lock
> └── arches
>     ├── CONTRIBUTING.md
>     ├── Dockerfile
>     ├── LICENSE.txt
>     ├── MANIFEST.in
>     ├── README.md
>     ├── appspec.yml
>     ├── arches
>     ├── cypress
>     ├── cypress.json
>     ├── docker
>     ├── docker-compose-test.yml
>     ├── docker-compose.yml
>     ├── export_test_fixtures.sh
>     ├── manage.py
>     ├── package.json
>     ├── pyproject.toml
>     ├── releases
>     ├── setup.py
>     ├── tests
>     └── yarn.lock
>
> 2. in /afs ; docker-compose up -d
> 3. reboot the afs container (else : empty response on localhost:8000)
> 4. access localhost:8000
> 5. any interaction with graphs or resources manager takes ages
>
>
> *Discussion*
>
> 1) Is something misplaced ? Or, is something deprecated (like the 
> package.json ?) TBH, having to reboot the container worries me much more.
> 2) Would an installation of a standard version of arches using the 
> Dockerfile and Compose file found in afs would be possible ?
> 3) In which part of the month AFS would be released ? May I hope for a 
> docker-install ? I do have rudiments in django, but they won't be enough 
> for this type of deployment.
>
> Looking forward for any tips to successfully install Arches,
> Best wishes for the new year,
> Regards,
>
> Antoine Gros
>
>

-- 
-- 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].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/archesproject/fb6cc85f-f733-48ac-8729-1753cf640910n%40googlegroups.com.

Reply via email to