sgallizia commented on issue #128: URL: https://github.com/apache/openserverless/issues/128#issuecomment-2894806521
I think I've solved it. I ran the command on the server: ``` :~$ kubectl get svc -n nuvolaris NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE couchdb ClusterIP 10.43.128.118 <none> 5984/TCP 25h couchdb-np NodePort 10.43.252.24 <none> 5984:30984/TCP 25h redis NodePort 10.43.163.123 <none> 6379:30379/TCP 25h nuvolaris-minio NodePort 10.43.43.80 <none> 9000:32090/TCP,9090:32091/TCP 25h nuvolaris-static-svc ClusterIP 10.43.170.115 <none> 8080/TCP 25h kubegres-controller-manager-metrics-service ClusterIP 10.43.68.82 <none> 8443/TCP 25h nuvolaris-postgres ClusterIP None <none> 5432/TCP 25h nuvolaris-mongodb-svc ClusterIP None <none> 27017/TCP 25h zookeeper ClusterIP None <none> 2181/TCP,2888/TCP,3888/TCP 25h nuvolaris-postgres-replica ClusterIP None <none> 5432/TCP 25h kafka ClusterIP None <none> 9092/TCP,9071/TCP,9888/TCP 25h invoker ClusterIP 10.43.183.238 <none> 8080/TCP 25h controller NodePort 10.43.183.175 <none> 3233:30233/TCP 25h ``` I took the cluster ip of the nuvolaris-minio and I ran: ``` export S3_API_URL=http://10.43.43.80:9000 ops ide deploy /home/user/.ops/tmp/deploy.pid PID 719534 > Scan: >> Action: packages/test/test.go > Deploying: >> Package: test $ $OPS package update test ok: updated package test >>> Action: packages/test/test.go $ $OPS action update test/test packages/test/test.go ok: updated action test/test build process exited with code 0 UPLOAD ASSETS FROM web ERROR: /home/user/path/packages/data/test/web is not a directory URL: http://testuser.192.168.1.171.traefik.me ``` So I created the web directory and then it worked. It's not clear to me why S3_API_URL is missing and why the web directory is mandatory. Now I can finally start using openserverless (I hope :) ) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
