.env
but backend not working
@ihalton
Running command: meteor run --port 4080 --no-lint --no-release-check --raw-logs
[[[[[ /usr/local/src/app ]]]]]
=> Started proxy.
Killed
Error: Command failed: REACTION_METEOR_APP_COMMAND_START_TIME=1597467210450 meteor run --port 4080 --no-lint --no-release-check --raw-logs
at checkExecSyncError (child_process.js:630:11)
at Object.execSync (child_process.js:666:15)
at run (file:///usr/local/src/app/.reaction/scripts/run.mjs:21:18)
at file:///usr/local/src/app/.reaction/scripts/run.mjs:29:1
at ModuleJob.run (internal/modules/esm/module_job.js:110:37)
at async Loader.import (internal/modules/esm/loader.js:164:24) {
status: 137,
signal: null,
output: [ null, null, null ],
pid: 39,
stdout: null,
stderr: null
}
Error: App failed to start
hello, get crashed when running reaction_admin from code. why?
I'd like to take advantage of the canary deployments and GitOps. Rio is a MicroPaaS by Rancher and is designed to work well with k3s. I've done some initial research here for anyone interested who hasn't worked with Rio yet: https://habd.as/post/git-based-continuous-delivery-rio/
ws
to wss
. At first I thought some configurations were wrong on the backend but, storefront successfully connects to the web socket server. I'm not really sure what's going on, this is the error I get failed: Error during WebSocket handshake: Unexpected response code: 400
. Any help would be much appreciated
apiVersion: v1
kind: Service
metadata:
labels:
reaction: admin
name: reaction-admin
annotations:
service.beta.kubernetes.io/aws-load-balancer-backend-protocol: "http"
service.beta.kubernetes.io/aws-load-balancer-ssl-cert: arn:aws:acm:us-east-2:<accountno>:certificate/<cid>
service.beta.kubernetes.io/aws-load-balancer-ssl-ports: "https"
service.beta.kubernetes.io/aws-load-balancer-proxy-protocol: "*"
spec:
ports:
- name: http
port: 80
targetPort: 4080
- name: https
port: 443
targetPort: 4080
selector:
reaction: admin
type: LoadBalancer
status:
loadBalancer: {}