Feature type

Quality of life

Describe the feature

I would like to be able to use relative paths in the launcher settings file to point to x32dbg.exe and x64dbg.exe respectively. I've already tried editing the file manually and assuming my implementation (.\/\//) isn't wrong, the launcher seemingly refuses the use of relative paths.

How to test

Caddyfile

http://{$BASE_URL} {
    log

    handle {
        root * /usr/share/caddy/html
        try_files {path} /index.html
        file_server
    }
}

test1.env

BASE_URL="test.com"

test2.env

BASE_URL=test.com

Run command

caddy run --config /etc/caddy/Caddyfile --adapter caddyfile --envfile /etc/caddy/.env

Possib

OS/Environment

None yet, but I'm working on OS X v10.11.6 'El Capitan' client-side. (See 'The way of deployment (cloud or local)' below for details on considered server infrastructure.)

Ansible version

None yet, as I haven't yet gotten that far into setting up Algo.

Version of components from requirements.txt

Not applicable (see above.)

Summary of the pro

🧐 Motivation
The current flash loans implementation suggests to burn the fee of the flash loan with no easy way for implementers to override this default behavior. e.g. If the token is capped, this leads to shrink the total supply over time [considering the fee is higher than 0].

This behavior is not well documented and the Wizard doesn't consider this.

📝 Details
I would suggest to

We have cd,pwd already, those two can be useful for scripts

Sorry for not following the template. It's a straightforward question.

By enabling "WordPress-specific rules", the following codes will be added to the wordpress.conf:

# WordPress: deny general stuff
location ~* ^/(?:xmlrpc\.php|wp-links-opml\.php|wp-config\.php|wp-config-sample\.php|readme\.html|license\.txt)$ {
    deny all;
}

However, this disables xmlrpc feature, which disa

We need a flag (compose-svc-start-wait ) to control how long docker-slim should wait before starting each service when there's a compose file (build, profile, run commands though the run command doesn't have support for compose yet).

Asking about this since the NSA recently published guidance advising the public and private sectors to transition to cryptographic algorithms that are no less than sha384 & ec384 (elliptic curves).

While Edwards' Curves are different, its worth noting that prior to this update sha256 & secp256k1 were both on the list of acceptable cryptographic algorithms. My deduction was that 128-bit securit

Hi,

it would be nice, if pod annotations would be configurable via values file. E.g:

values.yaml:

.
.
.
podAnnotations: {}
.
.
.

statefulset.yaml:

  template:
    metadata:
      {{- with .Values.podAnnotations }}
      annotations:
        {{- . | toYaml | nindent 8 }}
      {{- end }}