We hope very much that you will help us to fix everything that is not perfect yet and troubleshoot all the bugs by the date of official release. Adguard browser menu looks bad as we cannot control menu container size and shape.īut despite all the problems we strongly believe that this is a big step forward.Click "Load extension" button and choose unpacked extension folder.Turn on "Enable extension developer features".This means, that you should be on Insider Preview Windows version. Minimum supported Edge version is 38.14352.1002.0. Hence, in order to install it you should make some changes to your Edge configuration. Make your web surfing fast, safe and ad-free. However, we cannot yet publish it to Windows Store (as we don't see such option in developer dashboard ). AdGuard is the best way to get rid of annoying ads and online tracking and protect your computer from malware. So, we have finally ported Adguard browser extension to Microsoft Edge. Now we need to test it for some time to make sure that nothing is broken for other platforms.Ĭomplete description and a download link are available on GitHub: We have done a massive refactoring in order to port Adguard to Microsoft Edge. We have great news for you today! Finally, we can affirmatively answer the 'Do you have an extension for Edge?' question. # Port, default 8080 port: 8080 # if username and password are defined, basic auth is applied to the sync API username: username password: password # Configure sync features by default all features are enabled.Greetings to all of those who eager about browser extensions! # Configure the sync API server, disabled if api port is 0 api: url: username: username password: password # autoSetup: true # if true, AdGuardHome is automatically initialized. url: username: username password: password # url of the replica instance url: username: username password: password # replicas instances (optional, if more than one) replicas: # url of the origin instance url: # apiPath: define an api path if other than "/control" # insecureSkipVerify: true # disable tls check username: username password: password # replica instance (optional, if only one) replica: (default "" = runs only once) cron: "*/10 * * * * " # runs the synchronisation on startup runOnStart: true origin: 8080:8080 restart: unless-stopped Config file # FEATURES_GENERALSETTINGS: true # FEATURES_QUERYLOGCONFIG: true # FEATURES_STATSCONFIG: true # FEATURES_CLIENTSETTINGS: true # FEATURES_SERVICES: true # FEATURES_FILTERS: true # FEATURES_DHCP_SERVERCONFIG: true # FEATURES_DHCP_STATICLEASES: true # FEATURES_DNS_SERVERCONFIG: true # FEATURES_DNS_ACCESSLISTS: true # FEATURES_DNS_REWRITES: true ports: # REPLICA1_INTERFACENAME: 'ens18' # use custom dhcp interface name CRON: '*/10 * * * * ' # run every 10 minutes RUNONSTART: true # Configure sync features by default all features are enabled. ORIGIN_URL: ' ' ORIGIN_USERNAME: 'username ' ORIGIN_PASSWORD: 'password ' REPLICA_URL: ' ' REPLICA_USERNAME: 'username ' REPLICA_PASSWORD: 'password ' REPLICA1_URL: ' ' REPLICA1_USERNAME: 'username ' REPLICA1_PASSWORD: 'password ' REPLICA1_APIPATH: '/some/path/control ' # REPLICA1_AUTOSETUP: true # if true, AdGuardHome is automatically initialized. Image: ghcr.io/bakito/adguardhome-sync container_name: adguardhome-sync command: run environment:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |