[BUG] feature-policy.conf and permissions-policy.conf don't change #248
Replies: 5 comments
-
Hello @pjorritsma, Can you share the full docker-compose.yml (don't forget to edit sensitive data) please ? |
Beta Was this translation helpful? Give feedback.
-
Hello @fl0ppy-d1sk , Just use the standaard bunkerized docker-compose with autoconf from the wiki site. With the following labels for website:
Did try to add those rules above but don't work or put in the file on dictory |
Beta Was this translation helpful? Give feedback.
-
Hello @pjorritsma, Looks like I can't reproduce your issue. Here is what I did. docker-compose-autoconf.yml : version: '3'
services:
mybunkerized:
image: bunkerity/bunkerized-nginx
restart: always
ports:
- 80:8080
- 443:8443
volumes:
- bunkerized-vol:/etc/nginx
environment:
- SERVER_NAME=
- MULTISITE=yes
labels:
- "bunkerized-nginx.AUTOCONF"
networks:
- services-net
myautoconf:
image: bunkerity/bunkerized-nginx-autoconf
restart: always
volumes_from:
- mybunkerized
volumes:
- /var/run/docker.sock:/var/run/docker.sock:ro
depends_on:
- mybunkerized
volumes:
bunkerized-vol:
networks:
services-net:
name: services-net docker-compose-service.yml : version: "3"
services:
myservice:
image: tutum/hello-world
networks:
services-net:
aliases:
- myservice
labels:
- "bunkerized-nginx.SERVER_NAME=www.example.com"
- "bunkerized-nginx.USE_REVERSE_PROXY=yes"
- "bunkerized-nginx.REVERSE_PROXY_URL=/"
- "bunkerized-nginx.REVERSE_PROXY_HOST=http://myservice"
- "bunkerized-nginx.PERMISSIONS_POLICY=custom value for Permissions-Policy"
- "bunkerized-nginx.FEATURE_POLICY=custom value for Feature-Policy"
networks:
services-net:
external:
name: services-net Run bunkerized-nginx + autoconf and wait until everything is started (e.g. "bunkerized-nginx instances started" in logs) : docker-compose -f docker-compose-autoconf.yml pull
docker-compose -f docker-compose-autoconf.yml up -d
docker-compose -f docker-compose-autoconf.yml logs -f Run the service : docker-compose -f docker-compose-service.yml pull
docker-compose -f docker-compose-service.yml up -d And check the headers : curl http://localhost -H "Host: www.example.com" -H "User-Agent: Legit" -vvv
[...]
< Feature-Policy: custom value for Feature-Policy
< Permissions-Policy: custom value for Permissions-Policy
[...] |
Beta Was this translation helpful? Give feedback.
-
Hello Floppy, Thanks you so much for the response. Can you give me a example how you will define to allow GPS location on the site. This is what is currently blocked:
So do I need to adjust custom vlue with
All the values or is just geolocation '*' anough. The last time a i try the above it don't edit the config files. Thanks in adv. |
Beta Was this translation helpful? Give feedback.
-
Hello Fl0ppy could you help with stil issue? |
Beta Was this translation helpful? Give feedback.
-
Description
trying to allow GPS (Location) on the website
How to reproduce
Add the following code to docker-compose and run:
When looking in the files: feature-policy.conf and permissions-policy.conf notthing is changed
Logs
Can't find any reference in the logs
Beta Was this translation helpful? Give feedback.
All reactions