Open windcatcher opened 3 months ago
when new a style, clustering permission is 640,how to change to 644?
the docker image version is kartoza/geoserver:2.24.0
the docker run script is docker run --name "cluster-geoserver" --restart=on-failure -p 8081:8080 --privileged=true -e CLUSTERING=true -e CLUSTER_DURABILITY=false -e DB_BACKEND=POSTGRES -e HOST=host -e POSTGRES_PORT=5432 -e POSTGRES_DB=gis1 -e POSTGRES_USER=docker123e -e POSTGRES_PASS=docker1@123e -e SSL_MODE=ALLOW -e BROKER_URL=failover:(tcp://host1:61616,tcp://host2:61616,tcp://host3:61616) -e READONLY=enabled -e TOGGLE_MASTER=false -e TOGGLE_SLAVE=true -e EMBEDDED_BROKER=disabled -e RUN_AS_ROOT=TRUE -e GEOSERVER_ADMIN_USER=admin -e GEOSERVER_ADMIN_PASSWORD=reerwqe -e STABLE_EXTENSIONS= -e COMMUNITY_EXTENSIONS=jms-cluster-plugin -v /tgis/cluster/geoserver_data:/opt/geoserver/data_dir -d -t kartoza/geoserver:2.24.0
the new style [test.sld] permission is 640
style file permission
kartoza/geoserver:2.24.0
@NyakudyaA No response
@windcatcher I will take a look and revert
What is the bug or the crash?
when new a style, clustering permission is 640,how to change to 644?
the docker image version is kartoza/geoserver:2.24.0
the docker run script is docker run --name "cluster-geoserver" --restart=on-failure -p 8081:8080 --privileged=true -e CLUSTERING=true -e CLUSTER_DURABILITY=false -e DB_BACKEND=POSTGRES -e HOST=host -e POSTGRES_PORT=5432 -e POSTGRES_DB=gis1 -e POSTGRES_USER=docker123e -e POSTGRES_PASS=docker1@123e -e SSL_MODE=ALLOW -e BROKER_URL=failover:(tcp://host1:61616,tcp://host2:61616,tcp://host3:61616) -e READONLY=enabled -e TOGGLE_MASTER=false -e TOGGLE_SLAVE=true -e EMBEDDED_BROKER=disabled -e RUN_AS_ROOT=TRUE -e GEOSERVER_ADMIN_USER=admin -e GEOSERVER_ADMIN_PASSWORD=reerwqe -e STABLE_EXTENSIONS= -e COMMUNITY_EXTENSIONS=jms-cluster-plugin -v /tgis/cluster/geoserver_data:/opt/geoserver/data_dir -d -t kartoza/geoserver:2.24.0
the new style [test.sld] permission is 640
Steps to reproduce the issue
style file permission
Versions
kartoza/geoserver:2.24.0
Additional context
@NyakudyaA No response