Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upload system services on ipfs node #907

Merged
merged 4 commits into from
Apr 23, 2019
Merged

Conversation

krhubert
Copy link
Contributor

close #840

Copy link
Member

@antho1404 antho1404 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think there is some issue of compatibility between osx and linux

➜  core git:(feature/upload-systemservices) ✗ ./scripts/build-core.sh
./scripts/build-core.sh: line 12: ${name^}: bad substitution

@NicolasMahe
Copy link
Member

NicolasMahe commented Apr 23, 2019

I think there is some issue of compatibility between osx and linux

➜  core git:(feature/upload-systemservices) ✗ ./scripts/build-core.sh
./scripts/build-core.sh: line 12: ${name^}: bad substitution

It should be run inside a Docker container...
Try to run docker build .

@antho1404
Copy link
Member

It doesn't work in docker too

/bin/sh: 1: ./scripts/build-core.sh: not found

@antho1404
Copy link
Member

finally built by removing the script directory in the .dockerignore but still some error when running it.

time="2019-04-23T05:10:21Z" level=info msg="Deploying service \"ethwallet\" from \"\""
time="2019-04-23T05:10:21Z" level=fatal msg="Get : unsupported protocol scheme \"\""
time="2019-04-23T05:10:26Z" level=info msg="Deploying service \"ethwallet\" from \"\""
time="2019-04-23T05:10:26Z" level=fatal msg="Get : unsupported protocol scheme \"\""

@krhubert please test correctly and/or give a description on the pull request on how to test it.

@NicolasMahe
Copy link
Member

NicolasMahe commented Apr 23, 2019

I cannot run it also.
I runned (like the CI):

docker build -t mesg/core:dev --build-arg version="dev build test" .

@krhubert krhubert force-pushed the feature/upload-systemservices branch from 31e58c8 to 4322b20 Compare April 23, 2019 08:35
@krhubert
Copy link
Contributor Author

krhubert commented Apr 23, 2019

@antho1404 @NicolasMahe fixed

➜  core git:(feature/upload-systemservices) ✗ ./bin/cli logs      
time="2019-04-23T08:33:34Z" level=info msg="Deploying service \"ethwallet\" from \"http://ipfs.app.mesg.com:8080/ipfs/Qmcvqsd5kSTeB2bbzh4N4JqfUn1kJ4YyCQEzuCVf3fLPbj\""
time="2019-04-23T08:35:29Z" level=info msg="Service \"ethwallet\" deployed with hash \"9bAzHe2RyoYwAZLA2JUzDsgNnz3NtTYLADKCWf1E8VDf\""
time="2019-04-23T08:35:30Z" level=info msg="Deploying service \"marketplace\" from \"http://ipfs.app.mesg.com:8080/ipfs/QmbegmPwNnPGuYaMtoiFhGaTKYF2B6Jb1sk3UYVeywJuLr\""

To test locally you can

$ docker build -t mesg/core:local .
$ ./bin/cli start
$ ./bin/cli logs

scripts/build-core.sh Show resolved Hide resolved
@antho1404
Copy link
Member

I cannot test it, I keep having the same error

go: gopkg.in/src-d/go-git-fixtures.v3@v3.3.0: git fetch -f origin refs/heads/*:refs/heads/* refs/tags/*:refs/tags/* in /go/pkg/mod/cache/vcs/67698a57fcf1e2e2f3930542ab0263846a1ad71c488399c086e4929ccb6a539b: exit status 128:
        error: RPC failed; curl 56 GnuTLS recv error (-9): A TLS packet with unexpected length was received.
        fatal: The remote end hung up unexpectedly
        fatal: early EOF
        fatal: index-pack failed

any recommendation?

@ilgooz
Copy link
Contributor

ilgooz commented Apr 23, 2019

I cannot test it, I keep having the same error

go: gopkg.in/src-d/go-git-fixtures.v3@v3.3.0: git fetch -f origin refs/heads/*:refs/heads/* refs/tags/*:refs/tags/* in /go/pkg/mod/cache/vcs/67698a57fcf1e2e2f3930542ab0263846a1ad71c488399c086e4929ccb6a539b: exit status 128:
        error: RPC failed; curl 56 GnuTLS recv error (-9): A TLS packet with unexpected length was received.
        fatal: The remote end hung up unexpectedly
        fatal: early EOF
        fatal: index-pack failed

any recommendation?

we need to setup a module proxy for our automated builds. it'll fasten things a lot because there'll be no git clones, every download will use pre created zips for each package and we'll avoid missing packages or connection problems to third party servers like this. i can setup a proxy just in minutes maybe on http://goproxy.dev.mesg.com.

@NicolasMahe can you create a DNS record for *.dev.mesg.com to point DO, it can be useful.

@NicolasMahe
Copy link
Member

NicolasMahe commented Apr 23, 2019

@NicolasMahe can you create a DNS record for *.dev.mesg.com to point DO, it can be useful.

Done

@NicolasMahe
Copy link
Member

I cannot test it, I keep having the same error

go: gopkg.in/src-d/go-git-fixtures.v3@v3.3.0: git fetch -f origin refs/heads/*:refs/heads/* refs/tags/*:refs/tags/* in /go/pkg/mod/cache/vcs/67698a57fcf1e2e2f3930542ab0263846a1ad71c488399c086e4929ccb6a539b: exit status 128:
        error: RPC failed; curl 56 GnuTLS recv error (-9): A TLS packet with unexpected length was received.
        fatal: The remote end hung up unexpectedly
        fatal: early EOF
        fatal: index-pack failed

any recommendation?

Setup Athens: https://docs.gomods.io/install/shared-team-instance/
And inject the env variable in Dockerfile: ENV GOPROXY=http://host.docker.internal:3000

@ilgooz
Copy link
Contributor

ilgooz commented Apr 23, 2019

i enabled the proxy at http://goproxy.dev.mesg.com and cached gopkg.in/src-d/go-git-fixtures.v3@v3.3.0 for you. please use this one as a proxy, you shouldn't face with any problems.

if you don't even want to go to outside network, you can spin up an http static file server at your $GOPATH/pkg/mod/cache/vcs and it'll be your local goproxy.

@antho1404
Copy link
Member

the proxy did the job thanks.

@krhubert krhubert merged commit ca5a07e into dev Apr 23, 2019
@antho1404 antho1404 deleted the feature/upload-systemservices branch April 23, 2019 16:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Manage deployment of services for the build
4 participants