Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Jakub Vysoký
    @kvbik
    Hey @mikelor happy you've stopped by ;)
    mike lorengo
    @mikelor
    Was using this default "windingtree" wallet... is that the right thing to do?
    H:>type account.json
    {
    "wallet": {"version":3,"id":"7fe84016-4686-4622-97c9-dc7b47f5f5c6","crypto":{"ciphertext":"ef9dcce915eeb0c4f7aa2bb16b9ae6ce5a4444b4ed8be45d94e6b7fe7f4f9b47","cipherparams":{"iv":"31b12ef1d308ea1edacc4ab00de80d55"},"cipher":"aes-128-ctr","kdf":"scrypt","kdfparams":{"dklen":32,"salt":"d06ccd5d9c5d75e1a66a81d2076628f5716a3161ca204d92d04a42c057562541","n":8192,"r":8,"p":1},"mac":"2c30bc373c19c5b41385b85ffde14b9ea9f0f609c7812a10fdcb0a565034d9db"}},
    "uploaders": {
    "root": {
    "swarm": {}
    }
    }
    }
    Jakub Vysoký
    @kvbik
    I believe you are not running an instance of wt-write-api on your machine. You either have to run a docker container, or you can run your curl against our staging instance. The URL is mentioned there in the docs.
    I believe you can use this testing wallet there too. But of course in production you have to create your own.
    mike lorengo
    @mikelor
    I'm pretty sure I have it running. When I go to localhost:8080/ I get the following
    {"docs":"https://playground-write-api.windingtree.com/docs/","info":"https://github.com/windingtree/wt-write-api/blob/master/README.md","version":"0.15.1","config":"playground","ethNetwork":"ropsten","wtIndexAddress":"0xB309875d8b24D522Ea0Ac57903c8A0b0C93C414A","dataFormatVersions":{"hotels":"0.6.6"}}
    Jakub Vysoký
    @kvbik
    Hmmm, maybe the error message curl: (6) Could not resolve host: application got me confused.
    Anyways, if you run your own instance, you have to register
    mike lorengo
    @mikelor
    No problem, that had me confused too. Here's the error. {"status":422,"code":"#validationFailed","short":"Validation did not pass.","long":"Missing required property: wallet"}
    So, I should not use the default windingtree wallet listed in the tutorial?
    Hmm, maybe it's not seeing the application.json file, even though it's in the same directory.
    I mean the "account.json" file
    When I don't specify an account.json, I get a similar error. I'm running this from a windows machine :/
    I'll do some more digging. Thx for helping me take a deeper look at it.
    Ha, just realized I was talking to you Jakub. Have a great day.
    mike lorengo
    @mikelor
    So...that was it, ran it from bash and it worked.
    curl -X POST localhost:8080/accounts -H 'Content-Type: application/json' --data @account.json
    Jakub Vysoký
    @kvbik
    Ulala!!! Sweet!
    Sorry, I was not getting notifications
    Yes, it is me ;) I am taking the night shifts here, hahaha :)))
    Yes, I was actually afraid cmd.exe could cause some problems.
    Good to have you here @mikelor !
    Jiří Chadima
    @JirkaChadima
    Hey @mikelor we totally have some blind spots regarding windows and we hope to fix or at least document them soon! Thanks for trying the tools out!
    Thomas
    @beatelite
    Any update as to when tours/activities model/api will be announced? Is there a way to get involved with it's development?
    Spencer-WindingTree
    @Spencer-WindingTree
    Hey Thomas we have not started on that yet. But we will announce it whne we do.
    Thomas
    @beatelite
    @Spencer-WindingTree Is there any way to get involved with the schema? How open is the discussion around needs for tour operators?
    Thomas
    @beatelite
    @Spencer-WindingTree Also, does anyone on the windingtree team use the opentravel alliance json schemas for determining fields for the winding tree spec? If not, you should. Yes, they're old-school but they offer a well-researched set of datapoints that suppliers all use in transactions and messages to one another.
    Jiří Chadima
    @JirkaChadima
    Hi @beatelite , sorry for the late response... To get involved with the schema - probably the best place to start is the wtips repository. Create an issue with the description of the problem and we might start a discussion about that there.
    When we were researching the data model, I had definitely checked OTA schemas (although not the JSON ones, what I had was some XML stuff) and got a lot of inspiration from there. Also the enumerations are quite exhaustive, so we did a compilation of OTA, HTNG and other existing standards and APIs
    Robin Gottfried
    @czervenka
    You can also register to Winding Tree mainling list where we discuss bigger changes.
    Victor Pereira
    @vpereira
    good morning, I'm evaluating the WT solution, and I was trying to setup the development environment with docker-compose https://github.com/vpereira/wt-development-environment . With that with a simple docker-compose up you have ganache, wt-write-api and wt-read-api up and running
    however I was having some issues to interact with the api-read-api
    BTW I will be next week in lisboa for the hackathron :)
    so back to my problem: After I start everything with docker-compose I can call curl localhost:8081 for example and i see that everything is up and running
    i followed than the README from https://github.com/windingtree/wt-contracts
    Victor Pereira
    @vpereira
    git checkout, contracts compiled and deployed, everything fine. I was able to call it from the truffle console and register a new hotel as described in the README
    however as soon as i call http://localhost:8080/hotels I get some errors
    anyone would like to help me to figure out what I'm missing?
    the backtrace from the error https://gist.github.com/vpereira/a453dddbb7b2092fbef72182df0944b6
    Victor Pereira
    @vpereira
    I followed mostly the readme, the only difference data, I think are the addresses from the proxy instances returned by ./node_modules/.bin/zos create WTHotelIndex --network development --init initialize --args 0x87265a62c60247f862b9149423061b36b460f4bb,0xB6e225194a1C892770c43D4B529841C99b3DA1d7
    Jiří Chadima
    @JirkaChadima
    hi @vpereira I think the problem is that you are running the apis with playground config which tries to communicate with ropsten, but your config is talking to a local network which probably has the contracts deployed on a different address
    Victor Pereira
    @vpereira
    @JirkaChadima ok, thank you. What would be then the required configuration to connect the APIs with the development environment? WT_CONFIG=dev (the default?)
    Jiří Chadima
    @JirkaChadima
    You have two options, I think. Running with the dev config will deploy the smart contracts for you and you will have the environment ready. If you want to play with it a little more, you can use the envvar config and set everything up with environment variables
    Victor Pereira
    @vpereira
    yes, I just couldn't find where the dev WT_CONFIG deploys the contracts. As I see this file https://github.com/windingtree/wt-read-api/blob/master/management/local-network.js deploys the contracts, however its just called to run the specs.. is that right?
    Jiří Chadima
    @JirkaChadima
    I see... the deployment happens in https://github.com/windingtree/wt-read-api/blob/master/src/config/dev.js#L56 and the addresses are spit out on standard output
    Victor Pereira
    @vpereira
    ok, so to get started with the development, its better to run it locally with npm dev and npm run dev ?
    i mean with npm run dev-net
    Jiří Chadima
    @JirkaChadima
    Yeah, it's probably easier. npm run dev-net in one window and npm run dev in another and you should be good to go
    Victor Pereira
    @vpereira
    yes, I would probably make it work on the docker-compose, but i would have to tweak the Dockerfile for the API to run a custom local-network.js, which has localhost hardcoded