12-21-2019 03:26 PM
Olá, sou novo na plataforma e não sou programdor... apenas entusiasta do alfresco.
Instalei a versão mais recente do Alfresco, via docker-compose em Windows 10.
A aplicação está rodando bem, inclusive na rede.
Mas, lendo a documentação e post do forum, me deparei com a seguinte situação:
Se eu entendi certo, não é recomendado manter os dados produzidos apenas no container. O ideal é gerar um docker volume para armazenar as informações "fisicamente" na maquina local.
Pesquisei pelo fórum em inglês, mas não achei a solução para win10 de como gerar e fazer funcionar esses volumes.
Alguém teria um passo a passo de como resolver?
Where is the data stored?
When working with containers there are a couple of ways that data can be persisted. You can just store it inside the container or you can use something called Docker Volumes.
Storing it inside a container is a simple approach for demoing, testing, and PoC situations. However, it’s not ideal for a production environment as all content will be inside the container, which will make it very big. This means that there’s no way of having backup containers if something crashes. Also, it would not work if you wanted to cluster ACS. What you would use in production is Docker Volumes, which enable you to store the content outside the container.
To look at the Repository content we have to open a shell into the alf-repo container as follows and step into the alf_data directory (note, the container need to be started for this to work):
"$ docker container exe -it alf-repo /bin/bash
[root@0c3819df8582 tomcat]# ls -l
total 184
-rw-r----- 1 root root 57092 Feb 6 23:12 LICENSE
-rw-r----- 1 root root 1723 Feb 6 23:12 NOTICE
-rw-r----- 1 root root 7138 Feb 6 23:12 RELEASE-NOTES
-rw-r----- 1 root root 16246 Feb 6 23:12 RUNNING.txt
drwxr-x--- 4 root root 4096 Apr 4 15:21 alf_data
drwxr-xr-x 1 root root 4096 Mar 27 13:28 alfresco-mmt
-rw-r----- 1 root root 22382 Apr 5 05:42 alfresco.log
-rw-r----- 1 root root 23311 Apr 4 15:22 alfresco.log.2018-04-04
drwxr-xr-x 1 root root 4096 Mar 27 13:28 amps
drwxr-x--- 2 root root 4096 Mar 26 11:14 bin
drwx------ 1 root root 4096 Apr 4 15:20 conf
drwxr-xr-x 3 root root 4096 Mar 26 11:14 include
drwxr-x--- 1 root root 4096 Mar 27 13:28 lib
drwxr-x--- 1 root root 4096 Apr 5 05:41 logs
drwxr-xr-x 3 root root 4096 Mar 26 11:14 native-jni-lib
drwxr-xr-x 1 root root 4096 Mar 27 13:28 shared
drwxr-x--- 1 root root 4096 Apr 5 05:42 temp
drwxr-x--- 1 root root 4096 Apr 4 15:20 webapps
drwxr-x--- 1 root root 4096 Apr 4 15:20 work
[root@0c3819df8582 tomcat]# cd alf_data/
[root@0c3819df8582 alf_data]# ls -l
total 8
drwxr-x--- 3 root root 4096 Apr 4 15:21 contentstore
drwxr-x--- 2 root root 4096 Apr 4 15:20 contentstore.deleted
[root@0c3819df8582 alf_data]# cd contentstore
[root@0c3819df8582 contentstore]# cd 2018/4/5/5/33/
[root@0c3819df8582 33]# ls -l
total 8
-rw-r----- 1 root root 3732 Apr 5 05:33 1d41a201-ad12-42f9-9f44-3e70597b5fa4.bin
-rw-r----- 1 root root 61 Apr 5 05:33 b1ba1f0f-db04-49fd-9e11-aa57d2ffc6e6.bin
[root@0c3819df8582 33]# exit
Note that when you do this you will have a different directory structure under contentstore as you will have uploaded content after this article was written.
Tags
Find what you came for
We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.