I removed all containers. Then I reinstall 1.8.2.
I still have the same error
http://myip/login
Erreur de configuration
La Médiathèque n’est pas accessible à l’écriture
I always make the installation as root.
Could it be the cause of the mistake?
Thank you
=============================================================================
xibo-vm:/opt/xibo/shared# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS
NAMES
1f0fc1b3c21d xibosignage/xibo-cms:release_1.8.2 “/entrypoint.sh” 5 minutes ago Up 5 minutes 0.0.0.0:80->80/tcp
xibo_cms-web_1
6b1c6f85d1d5 xibosignage/xibo-xmr:release_1.8.2 “/entrypoint.sh” 5 minutes ago Up 5 minutes 0.0.0.0:9505->9505/tcp, 50001/tcp
xibo_cms-xmr_1
=============================================================================
xibo-vm:/opt/xibo# ll
total 112
drwxr-xr-x 3 root root 4096 Jun 29 10:31 ./
drwxr-xr-x 5 root root 4096 Jun 27 15:35 …/
-rw-rw-r-- 1 admin-xibo admin-xibo 1137 Jun 26 12:49 cms_custom-ports.yml.template
-rw-rw-r-- 1 admin-xibo admin-xibo 807 Jun 26 12:49 cms_remote-mysql.yml
-rwxrwxrwx 1 root root 1835 Jun 27 16:12 config.env*
-rw-rw-r-- 1 admin-xibo admin-xibo 2331 May 30 08:51 config.env.template
-rw-rw-r-- 1 admin-xibo admin-xibo 1861 Feb 22 16:09 config.env.template-remote-mysql
-rw-rw-r-- 1 admin-xibo admin-xibo 1133 Jun 26 14:04 docker-compose.yml
-rw-rw-r-- 1 admin-xibo admin-xibo 1133 Jun 26 14:04 docker-compose.yml.template
-rw-rw-r-- 1 admin-xibo admin-xibo 34520 Jun 22 2016 LICENSE
-rw-rw-r-- 1 admin-xibo admin-xibo 2088 Feb 22 08:43 README.md
drwxr-xr-x 4 root root 4096 Jun 29 10:31 shared/
Specifically the section about 1/3 the way down the page which starts
Since we’re importing a non-Docker based installation, there’s a couple of additional steps to take which require direct modification of the database. If you’re running with an external database, then please run the SQL commands listed below directly on your remote database instead of running these commands from inside the Docker console.
If you’ve gone for a custom install, then please ensure you setup XTR (essential) and XMR (optional, but advised) otherwise some of the CMS functionality won’t be available to you.
i am joining this thread as i have the same issue.
I made a fresh install under Debian 9.
I configured a custom port.
Everything seems to start without problem.
When i attempt to reach the cms page at localhost, it keeps complaining with the error “Library not writable”
I am not sure where the library path is and how to change it though.
I had a look at the config files where there are some paths that rings a bell but even after changing the permissions on those paths it doesn’t make any difference.
On a fresh install, the library path is set correctly for you to /var/www/cms/library/ which is where the container expects to see it.
Docker then maps that to a location on your servers filesystem defined in the docker-compose file - by default to the current working directory:
./shared/cms/library
So it’s that directory that you’d need to look at. When the container starts, it attempts to fix the permissions on that directory itself, so there shouldn’t be this issue. It implies something else is happening.
Is the server connected to the internet? If so, would I be able to get remote access so I can have a quick look? I can provide an SSH public key.
I don’t really understand the difference between the two paths you mention.
unfortunately my server is behind a firewall only accessible trough a VPN from outside.
i also have setup a custom port (80:80). I also notice that paths are also set in cms_custom_ports.yml so should i modify those if needed or the ones in docker-compose ?
