Skip to content
Permalink
Branch: dev-master
Commits on Apr 15, 2019
  1. Update ChangeLog for release-v0.0.1

    Yi Wang
    Yi Wang committed Apr 15, 2019
    Signed-off-by: Yi Wang <wangyi@storswift.com>
  2. fix uid verifing bug. (#16)

    yeewang authored and coder-lb committed Apr 15, 2019
    Signed-off-by: Yi Wang <wangyi@storswift.com>
Commits on Mar 20, 2019
  1. Fix user login and cp (#15)

    yeewang authored and coder-lb committed Mar 20, 2019
    * fix files/cp bug.
    
    Signed-off-by: Yi Wang <wangyi@storswift.com>
    
    * add uid/login API.
    
    Signed-off-by: Yi Wang <wangyi@storswift.com>
Commits on Mar 7, 2019
  1. use filepath to join path string. (#14)

    yeewang committed Mar 7, 2019
    Signed-off-by: Yi Wang <wangyi@storswift.com>
Commits on Feb 1, 2019
  1. fix bugs in uid synchronization; sync uid/renew action to all of clus…

    yeewang committed Feb 1, 2019
    …ter members.
    
    * fix bugs in  key synchronization
    
    Signed-off-by: Yi Wang <wangyi@storswift.com>
    
    * sync the uid/renew actions in all of actions.
    
    Signed-off-by: Yi Wang <wangyi@storswift.com>
Commits on Jan 31, 2019
  1. enable user keys discovery and synchronising in cluster. (#12)

    yeewang authored and coder-lb committed Jan 31, 2019
    * rename uid/login to uid/renew;
    fix typo error.
    
    Signed-off-by: Yi Wang <wangyi@storswift.com>
    
    * enable user keys discovery and synchronising in cluster.
    
    Signed-off-by: Yi Wang <wangyi@storswift.com>
Commits on Jan 27, 2019
  1. add more settings in deb package (#11)

    yeewang authored and coder-lb committed Jan 27, 2019
    * add configurable feature for to install Debian package
    
    Signed-off-by: Yi Wang <wangyi@storswift.com>
    
    * add more comments displaying while installing deb package.
    
    Signed-off-by: Yi Wang <wangyi@storswift.com>
Commits on Jan 24, 2019
  1. update deb package facility (#10)

    yeewang authored and coder-lb committed Jan 24, 2019
    * optimize Makefile
    
    * fix typo issue
    
    * update deb package facility
    
    Signed-off-by: Yi Wang <wangyi@storswift.com>
Commits on Jan 23, 2019
  1. Feat dist linux deb (#9)

    yeewang authored and coder-lb committed Jan 23, 2019
    * add a distribution target for Linux Debian system.
    
    Signed-off-by: Yi Wang <wangyi@storswift.com>
    
    * update README.md
    
    Signed-off-by: Yi Wang <wangyi@storswift.com>
Commits on Jan 21, 2019
  1. update file/get API; (#8)

    yeewang authored and stiartsly committed Jan 21, 2019
    add file/cat API.
    Signed-off-by: Yi Wang <wangyi@storswift.com>
  2. merge with ipfs cluster master (#5)

    yeewang authored and coder-lb committed Jan 21, 2019
    * Add the build tools download gateway.
    
    Signed-off-by: Yi Wang <wangyi8848@gmail.com>
    
    * add hive.cluster mark.
    due to this change, hive.cluster will be isolated from typical ipfs.cluster.
    
    Signed-off-by: Yi Wang <wangyi@storswift.com>
    
    * Fix HTTPs with DNS multiaddresses
    
    Before we resolved all /dns*/ multiaddresses before we used them.
    
    When using HTTPs, the Go HTTP Client only sees the resolved IP address
    and it is unable to negotiate TLS with a cerficate because the request
    is not going to the hostname the certificate is signed for, but to
    the IP. This leverages a recent feature in go-multiaddr-net
    and uses directly the user-provided hostname.
    
    License: MIT
    Signed-off-by: Hector Sanjuan <code@hector.link>
    
    * Fix interpreting Host parameter correctly.
    
    We should deprecate passing in Host/Port in the config,
    but in the meantime, it hardcoded /dns4/, meaning that if
    someone placed an ipv6 address in there things would break badly
    and weirdly.
    
    License: MIT
    Signed-off-by: Hector Sanjuan <code@hector.link>
    
    * Added tests for /monitor/metrics/{metrics_type}
    
    Added API and client tests for GET /monitor/metrics/{metrics_type}
    
    Fixes ipfs#587
    
    License: MIT
    Signed-off-by: Kishan Mohanbhai Sagathiya <kishansagathiya@gmail.com>
    
    * We are using https://github.com/chriscool/sharness
    
    We aren't using https://github.com/mlafeldt/sharness, code reference
    below
    https://github.com/ipfs/ipfs-cluster/blob/fdfe8def9467893d451e1fcb8ea3fb980c8c1389/Makefile#L67
    
    License: MIT
    Signed-off-by: Kishan Mohanbhai Sagathiya <kishansagathiya@gmail.com>
    
    * Sharness tests for ipfs-cluster-ctl health metrics
    
    Added sharness tests for `ipfs-cluster-ctl health metrics <metricname>`
    
    Fixes ipfs#587
    
    License: MIT
    Signed-off-by: Kishan Mohanbhai Sagathiya <kishansagathiya@gmail.com>
    
    * Added tests for /monitor/metrics/{metrics_type}
    
    Move ctl-health sharness tests to apprpriate file
    
    Since the API is using the RPC mock to request metrics and it always
    returns a mocked test metric we might just do c.Metrics("somemetricstype")
    and check that there is no error. Here we just want to check that the
    client is hitting an API endpoint (and understands the response).
    
    Fixes ipfs#587
    
    License: MIT
    Signed-off-by: Kishan Mohanbhai Sagathiya <kishansagathiya@gmail.com>
    
    * Fix ipfs#632: Handle "stream-channels" in /add endpoints
    
    License: MIT
    Signed-off-by: Hector Sanjuan <code@hector.link>
    
    * Fix $632: Test stream-channels=false in /add endpoint
    
    License: MIT
    Signed-off-by: Hector Sanjuan <code@hector.link>
    
    * Fix ipfs#632: Apply -Q option to --enc=json when adding.
    
    This will only print the latest JSON update when adding
    with -Q.
    
    License: MIT
    Signed-off-by: Hector Sanjuan <code@hector.link>
    
    * Fix ipfs#445: Implemented status filter for ipfs-cluster-ctl
    
    License: MIT
    Signed-off-by: Paul Jewell <sona1111@zoho.com>
    
    * Fix ipfs#445: Reduced length of filter help string
    
    License: MIT
    Signed-off-by: Paul Jewell <sona1111@zoho.com>
    
    * Fix ipfs#445:
    
    -Fixed logic issue in match condition of 'filterStatus' function
    -Added and verified success of test provided by @lanzafame
    -Attempted to condense code and apply other cleanup provided by @lanzafame
    
    License: MIT
    Signed-off-by: Paul Jewell <sona1111@zoho.com>
    
    * Fix ipfs#445:
    
    -Changed some 'snake case' to 'camel case' in accordance with code climate
    
    License: MIT
    Signed-off-by: Paul Jewell <sona1111@zoho.com>
    
    * Status filters for `ipfs-cluster-ctl status`
    
    Added filter option to `ipfs-cluster-ctl status`
    
    When the --filter is passed, it will only fetch the peer information
    where status of the pin matches with the filter value.
    Valid filter values are tracker status types(i.e., "pinned",
    "pin_error", "unpinning" etc), an alias of tracker status type (i.e.,
    "queued" or "error"), comma separated list of tracker status type
    and/or it aliases(i.e., "error,pinning")
    
    On passing invalid filter value no status information will be shown
    
    In particular, the filter would remove elements from []GlobalPinInfo
    when none of the peers in GlobalPinInfo match the filter. If one peer
    in the GlobalPinInfo matches the filter, the whole object is returned,
    including the information for the other peers which may or not match it.
    
    filter option works on statusAll("GET /pins"). For fetching pin status
    for a CID("GET /pins/<cid>"), filter option would have no effect
    
    Fixes ipfs#445
    
    License: MIT
    Signed-off-by: Kishan Mohanbhai Sagathiya <kishansagathiya@gmail.com>
    
    * Status filters for `ipfs-cluster-ctl status`
    
    Added clients tests
    
    Fixes ipfs#445
    
    License: MIT
    Signed-off-by: Kishan Mohanbhai Sagathiya <kishansagathiya@gmail.com>
    
    * Status filters for `ipfs-cluster-ctl status`
    
    Added a fail case where an invalid filter is passed in.
    Update `api.rpcClient.Call` to `api.rpcClient.CallContext` and pass
    in the Request context r.Context() so that context can be cancelled
    when the request is cancelled by caller
    
    Fixes ipfs#445
    
    License: MIT
    Signed-off-by: Kishan Mohanbhai Sagathiya <kishansagathiya@gmail.com>
    
    * Status filters for `ipfs-cluster-ctl status`
    
    Passing `make check`
    
    Fixes ipfs#445
    
    License: MIT
    Signed-off-by: Kishan Mohanbhai Sagathiya <kishansagathiya@gmail.com>
    
    * Status filters for `ipfs-cluster-ctl status`
    
    Improved matching of filters and tracker status
    
    Fixes ipfs#445
    
    License: MIT
    Signed-off-by: Kishan Mohanbhai Sagathiya <kishansagathiya@gmail.com>
    
    * Wrap help message for less than 120 characters
    
    License: MIT
    Signed-off-by: Kishan Mohanbhai Sagathiya <kishansagathiya@gmail.com>
    
    * Status filters for `ipfs-cluster-ctl status`
    
    Optimized filter to tracker status matching by using bitwise
    comparisions
    
    License: MIT
    Signed-off-by: Kishan Mohanbhai Sagathiya <kishansagathiya@gmail.com>
    
    * Fix ipfs#632: Make sure StreamChannels is enabled in rest/client.
    
    License: MIT
    Signed-off-by: Hector Sanjuan <code@hector.link>
    
    * Feat ipfs#632: Keep default /add behaviour outside of conditional block
    
    Per review comment.
    
    License: MIT
    Signed-off-by: Hector Sanjuan <code@hector.link>
    
    * Feat ipfs#445: Use TrackerStatus as filter. Simplify and small misc.
    
    License: MIT
    Signed-off-by: Hector Sanjuan <code@hector.link>
    
    * Feat ipfs#445: Clarify about 0 filter value.
    
    License: MIT
    Signed-off-by: Hector Sanjuan <code@hector.link>
    
    * add uid register and uid name changing API.
    
    Signed-off-by: Yi Wang <wangyi@storswift.com>
    
    * add hive api: UidNew, UidLogIn, FilesCp, FilesFlush, FilesLs
    
    Signed-off-by: Yi Wang <wangyi@storswift.com>
    
    * Feat ipfs#445: Catch invalid filter strings in ipfs-cluster-ctl.
    
    License: MIT
    Signed-off-by: Hector Sanjuan <code@hector.link>
    
    * Issue ipfs#445: Fix test
    
    License: MIT
    Signed-off-by: Hector Sanjuan <code@hector.link>
    
    * Feat ipfs#445: Fix string test with TrackerStatus == 0
    
    License: MIT
    Signed-off-by: Hector Sanjuan <code@hector.link>
    
    * add FilesMkdir, FilesMv, and FilesRm API.
    
    Signed-off-by: Yi Wang <wangyi@storswift.com>
    
    * Fix ipfs#632: Add --no-stream to ipfs-cluster-ctl
    
    tl;dr: this solves the user's immediate need and, even if not tne strictest
    solution, it is the simplest one.
    
    I think we should not have the server buffer output when we can do it rather
    easily client side and have the clients use their own memory for the task even
    if `stream-channels=false` would do this.
    
    We can always change the approach, but this is the minimal solution to
    json array with all the AddedOutput things.
    
    We might not buffer at all and hack a `[`, `,` separating elements and `]`
    at the end, when json encoding is enabled, etc. But that would not be clean,
    specially if we mean to support more output formats at some point.
    
    Enabling supporting stream-channels=false in the api/rest/client means adding
    new methods, with tests, modifying the interface etc etc. for what is
    essentially a presentation issue in "ctl" in the end. Similarly we could
    buffer inside the client, but it is so trivial that I don't see advatange.
    We should also start thinking about moving to streaming API endpoints and
    when that moment arrives we shall revisit this discussion.
    
    I have removed the hacky manual output parts by declaring a custom
    addedOutputQuiet type which wraps added output and is understood by
    the formatters.go helpers.
    
    License: MIT
    Signed-off-by: Hector Sanjuan <code@hector.link>
    
    * add FilesRead, FilesStat, FilesWrite.
    
    Known bug: FilesWrite may occur writing interrupt.
    
    Signed-off-by: Yi Wang <wangyi@storswift.com>
    
    * Issue ipfs#632: Fix wrong name for flag. Address review comments
    
    License: MIT
    Signed-off-by: Hector Sanjuan <code@hector.link>
    
    * Fix ipfs#382 (again): A better strategy for handling proxy headers
    
    This changes the current strategy to extract headers from the IPFS daemon to
    use them for hijacked endpoints in the proxy. The ipfs daemon is a bit of a
    mess and what we were doing is not really reliable, specially when it comes to
    setting CORS headers right (which we were not doing).
    
    The new approach is:
    
    * For every hijacked request, make an OPTIONS request to the same path, with
    the given Origin, to the IPFS daemon and extract some CORS headers from
    that. Use those in the hijacked response
    
    * Avoid hijacking OPTIONS request, they should always go through so the IPFS
    daemon controls all the CORS-preflight things as it wants.
    
    * Similar to before, have a only-once-triggered request to extract other
    interesting or custom headers from a fixed IPFS endpoint.  This allows us to
    have the proxy forward other custom headers and to catch
    `Access-Control-Expose-Methods`. The difference is that the endpoint use for
    this and the additional headers are configurable by the user (but with hidden
    configuration options because this is quite exotic from regular usage).
    
    Now the implementation:
    
    * Replaced the standard Muxer with gorilla/mux (I have also taken the change
    to update the gxed version to the latest tag). This gives us much better
    matching control over routes and allows us to not handle OPTIONS requests.
    
    * This allows also to remove the extractArgument code and have proper handlers
    for the endpoints passing command arguments as the last segment of the URL. A
    very simple handler that wraps the default ones can be used to extract the
    argument from the url and put it in the query.  Overall much cleaner this way.
    
    * No longer capture interesting headers from any random proxied request.  This
    made things complicated with a wrapping handler. We will just trigger the one
    request to do it when we need it.
    
    * When preparing the headers for the hijacked responses:
      * Trigger the OPTIONS request and figure out which CORS things we should set
      * Set the additional headers (perhaps triggering a POST request to fetch them)
      * Set our own headers.
    
    * Moved all the headers stuff to a new headers.go file.
    
    * Added configuration options (hidden by default) to:
      * Customize the extract headers endpoint
      * Customize what additional headers are extracted
      * Use HTTPs when talking to the IPFS API
        * I haven't tested this, but I did not want to have hardcoded 'http://' urls
          around, as before.
    
    * Added extra testing for this, and tested manually a lot comparing the
    daemon original output with our hijacked endpoint outputs while looking
    at the API traffic with ngrep and making sure the requets happen as expected.
    Also tested with IPFS companion in FF and Chrome.
    
    License: MIT
    Signed-off-by: Hector Sanjuan <code@hector.link>
    
    * ipfsproxy: add ExtractHeaderTTL option to config
    
    License: MIT
    Signed-off-by: Hector Sanjuan <code@hector.link>
    
    * Fix ipfs#382: Add TTL for cached headers
    
    License: MIT
    Signed-off-by: Hector Sanjuan <code@hector.link>
    
    * Fix typos in comments
    
    License: MIT
    Signed-off-by: Hector Sanjuan <code@hector.link>
    
    * Fix ipfs#639: Import rs/cors with Gx
    
    License: MIT
    Signed-off-by: Hector Sanjuan <code@hector.link>
    
    * Fix ipfs#639: Add CORS options to restapi
    
    License: MIT
    Signed-off-by: Hector Sanjuan <code@hector.link>
    
    * Fix ipfs#639: restapi: Handle CORS preflight requests (OPTIONS)
    
    This adds support for handling preflight requests in the REST API
    and fixes currently mostly broken CORS.
    
    Before we just let the user add custom response headers to the
    configuration "headers" key but this is not the best way because
    CORs headers and requests need special handling and doing it wrong
    has security implications.
    
    Therefore, I have added specific CORS-related configuration options
    which control CORS behavour. We are forced to change the "headers"
    defaults and will notify the users about this in the changelog.
    
    License: MIT
    Signed-off-by: Hector Sanjuan <code@hector.link>
    
    * ipfsproxy: fix tests for new configuration keys
    
    License: MIT
    Signed-off-by: Hector Sanjuan <code@hector.link>
    
    * ipfsproxy: fix typos in comments
    
    License: MIT
    Signed-off-by: Hector Sanjuan <code@hector.link>
    
    * restapi: minor codeclimate issue
    
    License: MIT
    Signed-off-by: Hector Sanjuan <code@hector.link>
    
    * Fix ipfs#639: Do not break start by complaining of unset CORSMaxAge
    
    License: MIT
    Signed-off-by: Hector Sanjuan <code@hector.link>
    
    * Fix ipfs#639: Enforce basic auth for all requests when enabled
    
    License: MIT
    Signed-off-by: Hector Sanjuan <code@hector.link>
    
    * Sharness: update configuration files used in sharness
    
    Maintenance
    
    License: MIT
    Signed-off-by: Hector Sanjuan <code@hector.link>
    
    * config: Fix confusing errors
    
    The JSON parsing of the config could error, but we skipped error checking and
    use Validate() at the end. This caused that maybe some JSON parsing errors
    where logged but the final error when validating the configuration came from
    somewhere different, creating very confusing error messages for the user.
    
    This changes this, along with removing hardcoded section lists. This also
    removes a Sharder component section because, AFAIK, it was a left over
    from the sharding branch and in the end there is no separate sharding
    component that needs a config.
    
    License: MIT
    Signed-off-by: Hector Sanjuan <code@hector.link>
    
    * sharness: Fix test typo causing an empty grep
    
    License: MIT
    Signed-off-by: Hector Sanjuan <code@hector.link>
    
    * Config: Interpret empty duration strings as duration = 0.
    
    In practice, we allowed this already, because parsing failed
    but Validate() succeeded.
    
    License: MIT
    Signed-off-by: Hector Sanjuan <code@hector.link>
    
    * config: do not handle "" durations (and do not error)
    
    They should not be interpreted as 0, since that may overwrite
    defaults which are not 0. We simply need to do nothing.
    
    License: MIT
    Signed-off-by: Hector Sanjuan <code@hector.link>
    
    * Update sharness/t0032-ctl-health.sh
    
    Fix the pid extraction in test.
    
    Co-Authored-By: hsanjuan <hsanjuan@users.noreply.github.com>
    
    License: MIT
    Signed-off-by: Hector Sanjuan <code@hector.link>
    
    * sharness: test should check agains cluster peer ID
    
    License: MIT
    Signed-off-by: Hector Sanjuan <code@hector.link>
    
    * Release 0.8.0-rc1
    
    License: MIT
    Signed-off-by: Hector Sanjuan <code@hector.link>
    
    * gx publish 0.8.0-rc1
    
    License: MIT
    Signed-off-by: Hector Sanjuan <code@hector.link>
    
    * Changelog for 0.8.0 release
    
    License: MIT
    Signed-off-by: Hector Sanjuan <code@hector.link>
    
    * Release 0.8.0
    
    License: MIT
    Signed-off-by: Hector Sanjuan <code@hector.link>
    
    * gx publish 0.8.0
    
    License: MIT
    Signed-off-by: Hector Sanjuan <code@hector.link>
    
    * Fix changelog date
    
    License: MIT
    Signed-off-by: Hector Sanjuan <code@hector.link>
    
    * Fix bug in filesWrite and add NamePublish.
    
    Signed-off-by: Yi Wang <wangyi@storswift.com>
    
    * add uid/info API
    
    Signed-off-by: Yi Wang <wangyi@storswift.com>
Commits on Jan 19, 2019
  1. enable files/write API (#4)

    yeewang authored and coder-lb committed Jan 19, 2019
    * Add the build tools download gateway.
    
    Signed-off-by: Yi Wang <wangyi8848@gmail.com>
    
    * add hive.cluster mark.
    due to this change, hive.cluster will be isolated from typical ipfs.cluster.
    
    Signed-off-by: Yi Wang <wangyi@storswift.com>
    
    * Fix HTTPs with DNS multiaddresses
    
    Before we resolved all /dns*/ multiaddresses before we used them.
    
    When using HTTPs, the Go HTTP Client only sees the resolved IP address
    and it is unable to negotiate TLS with a cerficate because the request
    is not going to the hostname the certificate is signed for, but to
    the IP. This leverages a recent feature in go-multiaddr-net
    and uses directly the user-provided hostname.
    
    License: MIT
    Signed-off-by: Hector Sanjuan <code@hector.link>
    
    * Fix interpreting Host parameter correctly.
    
    We should deprecate passing in Host/Port in the config,
    but in the meantime, it hardcoded /dns4/, meaning that if
    someone placed an ipv6 address in there things would break badly
    and weirdly.
    
    License: MIT
    Signed-off-by: Hector Sanjuan <code@hector.link>
    
    * add uid register and uid name changing API.
    
    Signed-off-by: Yi Wang <wangyi@storswift.com>
    
    * add hive api: UidNew, UidLogIn, FilesCp, FilesFlush, FilesLs
    
    Signed-off-by: Yi Wang <wangyi@storswift.com>
    
    * add FilesMkdir, FilesMv, and FilesRm API.
    
    Signed-off-by: Yi Wang <wangyi@storswift.com>
    
    * add FilesRead, FilesStat, FilesWrite.
    
    Known bug: FilesWrite may occur writing interrupt.
    
    Signed-off-by: Yi Wang <wangyi@storswift.com>
    
    * Fix bug in filesWrite and add NamePublish.
    
    Signed-off-by: Yi Wang <wangyi@storswift.com>
    
    * add uid/info API
    
    Signed-off-by: Yi Wang <wangyi@storswift.com>
Commits on Jan 18, 2019
  1. Update LICENSE (#3)

    stiartsly authored and yeewang committed Jan 18, 2019
  2. Update the READEME (#2)

    stiartsly authored and yeewang committed Jan 18, 2019
Commits on Jan 17, 2019
  1. Pre release hive alpha v0.1.2 (#1)

    yeewang authored and stiartsly committed Jan 17, 2019
    * rename repo name.
    * add README.md
    Signed-off-by: Yi Wang <wangyi@storswift.com>
Commits on Jan 13, 2019
  1. release hive_alpha-v0.1.1

    Yi Wang
    Yi Wang committed Jan 13, 2019
Commits on Dec 20, 2018
  1. Merge pull request ipfs#623 from ipfs/fix/proxy-headers

    hsanjuan committed Dec 20, 2018
    Fix ipfs#382: Extract headers from IPFS API requests and apply them to hijacked ones.
  2. proxy: Check all headers to decide if we need to request

    hsanjuan committed Dec 20, 2018
    And do it by only loading them from the sync.Map once.
    
    License: MIT
    Signed-off-by: Hector Sanjuan <code@hector.link>
  3. proxy: Rename helper to ipfsHeadersKnown()

    hsanjuan committed Dec 20, 2018
    License: MIT
    Signed-off-by: Hector Sanjuan <code@hector.link>
Commits on Dec 18, 2018
  1. Merge pull request ipfs#624 from ipfs/libp2p-6.0.29

    hsanjuan committed Dec 18, 2018
    Update to libp2p-6.0.29 (and general dep alignment)
  2. Update to libp2p-6.0.29 (and general dep alignment)

    hsanjuan committed Dec 18, 2018
    License: MIT
    Signed-off-by: Hector Sanjuan <code@hector.link>
  3. Fix ipfs#382: Extract headers from IPFS API requests & apply them to …

    hsanjuan committed Dec 18, 2018
    …hijacked ones.
    
    This commit makes the proxy extract useful fixed headers (like CORS) from
    the IPFS daemon API responses and then apply them to the responses
    from hijacked endpoints like /add or /repo/stat.
    
    It does this by caching a list of headers from the first IPFS API
    response which has them. If we have not performed any proxied request or
    managed to obtain the headers we're interested in, this will try triggering a
    request to "/api/v0/version" to obtain them first.
    
    This should fix the issues with using Cluster proxy with IPFS Companion and
    Chrome.
    
    License: MIT
    Signed-off-by: Hector Sanjuan <code@hector.link>
Commits on Dec 17, 2018
  1. Merge pull request ipfs#613 from ipfs/gx/files2

    hsanjuan committed Dec 17, 2018
    go-ipfs-files 2.0 updates
  2. API/client: Do not clean folders mid-test.

    hsanjuan committed Dec 17, 2018
    License: MIT
    Signed-off-by: Hector Sanjuan <code@hector.link>
  3. Update to go-ipfs-files 2.0.3

    hsanjuan committed Dec 17, 2018
    License: MIT
    Signed-off-by: Hector Sanjuan <code@hector.link>
  4. Unrewrite deps

    hsanjuan committed Dec 6, 2018
    License: MIT
    Signed-off-by: Hector Sanjuan <code@hector.link>
  5. files2.0: Close subfiles in adder

    magik6k authored and hsanjuan committed Dec 3, 2018
    License: MIT
    Signed-off-by: Łukasz Magiera <magik6k@gmail.com>
  6. files2.0: use type helpers

    magik6k authored and hsanjuan committed Dec 3, 2018
    License: MIT
    Signed-off-by: Łukasz Magiera <magik6k@gmail.com>
  7. files2.0: update for no errors from NewMultiFileReader

    magik6k authored and hsanjuan committed Dec 3, 2018
    License: MIT
    Signed-off-by: Łukasz Magiera <magik6k@gmail.com>
  8. files2.0: fix ContextCancelled test

    magik6k authored and hsanjuan committed Dec 3, 2018
    License: MIT
    Signed-off-by: Łukasz Magiera <magik6k@gmail.com>
  9. go-ipfs-files 2.0 updates

    magik6k authored and hsanjuan committed Dec 1, 2018
    License: MIT
    Signed-off-by: Łukasz Magiera <magik6k@gmail.com>
  10. Merge pull request ipfs#617 from ipfs/issue_616

    hsanjuan committed Dec 17, 2018
    Remove `proxy_` and `Proxy` from proxy config
  11. Remove proxy_ prefix from testing configurations

    hsanjuan committed Dec 17, 2018
    License: MIT
    Signed-off-by: Hector Sanjuan <code@hector.link>
  12. Fix proxy config compatibility

    hsanjuan committed Dec 17, 2018
    License: MIT
    Signed-off-by: Hector Sanjuan <code@hector.link>
  13. Put a note for deprecating json fields

    kishansagathiya committed Dec 17, 2018
    Put a note for deprecating json fields that they are only here to
    maintain compatibility and they will be removed in future
    
    Start using env vars starting with `CLUSTER_IPFSPROXY`
    
    License: MIT
    Signed-off-by: Kishan Mohanbhai Sagathiya <kishansagathiya@gmail.com>
Older
You can’t perform that action at this time.