make deploy exit error 1 - caddy is missing
See original GitHub issueAs far as I can see the PR https://github.com/WalletConnect/walletconnect-monorepo/pull/697 has wiped all caddy related configuration. Was it deprecated? Is there a replacement?
Latest release when running make deploy
exists with error:
~/walletconnect-monorepo$ sudo make deploy
sed: can't read setup: No such file or directory
Relay URL domain [localhost]:
Email for SSL certificate (default noreply@gmail.com):
Paste your cloudflare API token:
MAKE: Done with setup
mkdir -p build
mkdir -p .makeFlags
docker pull redis:6-alpine
6-alpine: Pulling from library/redis
Digest: sha256:4bed291aa5efb9f0d77b76ff7d4ab71eee410962965d052552db1fb80576431d
Status: Image is up to date for redis:6-alpine
docker.io/library/redis:6-alpine
docker pull nixos/nix
Using default tag: latest
latest: Pulling from nixos/nix
Digest: sha256:f0c68f870c655d8d96658ca762a0704a30704de22d16b4956e762a2ddfbccb09
Status: Image is up to date for nixos/nix:latest
docker.io/nixos/nix:latest
touch .makeFlags/pull
MAKE: Done with pull
MAKE: Done with nix-volume
docker run --name builder --rm -v nix-store:/nix -v /home/ubuntu/walletconnect-monorepo:/src -w /src nixos/nix nix-shell -p bash --run "nix-build --attr relay.docker --argstr githash ad1670bf && cp -r -f -L result build/build-img-relay && rm -rf result"
/nix/store/xc0ydzg1kasi940k4l54544020gyan6z-relay-server.tar.gz
docker load -i build/build-img-relay | awk '{print $NF}' | tee build/build-img-relay-img
walletconnect/relay-server:v1.0.2
MAKE: Done with build-img-relay
docker run --name builder --rm -v nix-store:/nix -v /home/ubuntu/walletconnect-monorepo:/src -w /src nixos/nix nix-shell -p bash --run "nix-build ./ops/waku-docker.nix --argstr wakuVersionTag v0.5.1 --argstr nixNimRepoSha256 0k55hw1wqcyrpf9cxchhxdb92p75mmskkpvfn1paivl1r38pyb4a && cp -r -f -L result build/build-img-waku && rm -rf result"
/nix/store/jckw0kx1ha032bywyc1rld6z19ap6373-wakunode.tar.gz
docker load -i build/build-img-waku | awk '{print $NF}' | tee build/build-img-waku-img
wakunode:9b5lmv4gdvi28y37riqjyg7a6xygsa32
MAKE: Done with build-img-waku
touch .makeFlags/predeploy
bash ops/deploy.sh
cat: ./build/build-img-caddy-img: No such file or directory
Deploy command: docker stack deploy walletconnect -c ops/docker-compose.yml -c ops/docker-compose.prod.yml -c ops/docker-compose.monitor.yml
Creating network walletconnect_default
open /home/ubuntu/walletconnect-monorepo/ops/stats.html: no such file or directory
make: *** [Makefile:148: deploy] Error 1
Issue Analytics
- State:
- Created 2 years ago
- Comments:8 (2 by maintainers)
Top Results From Across the Web
Caddy - exit status 1
How I run Caddy: caddy run. error after the command run: adapting config using caddyfile: subject does not qualify for certificate: '}'.
Read more >Troubleshooting 'terminated with exit code 1' error - ContainIQ
The application will have crashed, causing the container's foreground process to stop and emit the exit code. This signals to Kubernetes that an...
Read more >Troubleshooting - Dokku Documentation
This command deamonizes the process and exists. The container thinks it's done so it closes itself. The error you get is the one...
Read more >Troubleshooting Grafana Agent | Grafana Cloud documentation
Stop the agent from running by pressing Ctrl-C in the terminal window and then repeat the Generate config file step, followed by Run...
Read more >How To Host a Website with Caddy on Ubuntu 16.04
Step 1 — Building Caddy. In this step, you'll fetch Caddy's source code and make sure that you're able to compile it. Caddy...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thanks, I will work on fixing this.
@sbc64 thank you for a response! I’m going to close the issue. Running the service itself is more than enough. Most engineers know how to add a LB and/or Reverse Proxy layer.