| Predicate | Sourcegraph | Sourcebot | Notes |
|---|---|---|---|
repo:has.path(...) |
✅ | ❌ | Repos containing matching file paths |
repo:has.meta(...) |
✅ | ❌ | Filter by repo metadata (key-value) |
repo:has.topic(...) |
✅ | ❌ | Filter by GitHub/GitLab topic |
repo:has.commit.after(...) |
✅ | ❌ | Exclude stale repos |
| "use strict"; | |
| Object.defineProperty(exports, "__esModule", { | |
| value: true | |
| }); | |
| exports.default = void 0; | |
| var _default = process = { | |
| env: { | |
| NODE_ENV: "dev" |
| __pycache__ |
| /.vscode | |
| __pycache__ | |
| .pytest_cache | |
| log.txt |
| <html> | |
| <head> | |
| <script type="text/javascript" src="https://www.gstatic.com/charts/loader.js"></script> | |
| <script type="text/javascript"> | |
| /////////////////////////////////////////////////////////////////////////////////////////// | |
| // | |
| // Scrollez vers le bas, jusqu'à la définition de la fonction "drawChart()" | |
| // | |
| /////////////////////////////////////////////////////////////////////////////////////////// |
Here's a setup using a reverse proxy so that you can use relative url (instead of messing with domain names in your webpages) and which also has the advantage of taking care of CORS issues you would have while making ajax calls to your backend.
If you are not familiar with reverse proxies, just know that all http requests should first hit the reverse proxy, and the reverse proxy will take care of forwarding those http requests to the correct http server following a set of rules.
In the docker world, a very convenient reverse proxy is Traefik.
| image: dockergit:latest | |
| before_script: | |
| - docker version | |
| - docker login -u "$CI_REGISTRY_USER" -p "$CI_REGISTRY_PASSWORD" $CI_REGISTRY | |
| stages: | |
| - build | |
| #- test | |
| - publish |
| { | |
| "config": "https://via.placeholder.com/150" | |
| } |
Because I had a hard time finding the cause of a memory leak, I ended up making this bookmarlet to help find evidence of a memory leak caused by event listener not being removed on a webpage.
Once this bookmarklet is activated on your webpage, you will be able to call the getEventListenersStats()
from the Chrome DevTools Console. This function will give you stats about all events listeners and handlers.
| healthcheck: | |
| test: ["CMD", "wget", "--retry-connrefused", "--tries=10", "--spider", "--server-response", "http://localhost"] | |
| # wget --retry-connrefused --tries=10 --spider --server-response http://localhost:8080/ | |
| healthcheck: | |
| test: ["CMD", "curl", "--silent", "--show-error", "--fail", "--retry", "10", "--retry-connrefused", "--retry-delay", "5", "--retry-max-time", "30", "--head", "http://localhost:3000/login"] | |
| # curl --silent --show-error --fail --retry 10 --retry-connrefused --retry-delay 5 --retry-max-time 30 --head http://localhost:3000/login |