Skip to content

Fix or replace directory browser #537

Description

@RubenVerborgh

The current Solid server integrates Warp, but Warp broke because of #526.

Activity

  1. added
    priority-highto be used for important issues and pull requests that need to be addressed soon
    on Aug 11, 2017
  2. added this to the 4.0.0 milestone on Aug 11, 2017
  3. RubenVerborgh commented on Aug 11, 2017

    @RubenVerborgh
    ContributorAuthor

    Alternative suggested by @dmitrizagidulin: bundle Warp with node-solid-server.

  4. RubenVerborgh commented on Aug 11, 2017

    @RubenVerborgh
    ContributorAuthor

    I just tried bundling Warp by placing it in the common folder, and that works fine.

    One possible plan of action is to include multiple apps into an apps folder on initialization (cloning them from GitHub). These apps could include Warp, mashlib, etc.

    We would implement this as follows:

    • in multi-user mode, place apps on the server's account
    • in single-user mode, place apps on the user's account

    This would require a modification to server-config.js with an extra initializeApps function, that is called from ensureWelcomePage.

  5. timbl commented on Aug 13, 2017

    @timbl
    Contributor

    I counter-propose using the full local databrowser instead of warp,

    • as it gives much more functionality for all kinds of data
    • it avoids the problem of the origin of the web app need ing to be
      I suggest an upgrade of the server pull in the latest mashlib.js and databrowser.html, but making sure that if the user has configured their server to use their own specific databrowser file, that config is not overwritten by the server upgrade.

    I suggest both the small HTML file and the large JS file are provided on the server. An alternative would be for us to serve the JS file from a solid.github.io etc -- a place we control and upgrade.

  6. RubenVerborgh commented on Aug 14, 2017

    @RubenVerborgh
    ContributorAuthor

    Another suggestion is to fix Warp (linkeddata/warp#23).

  7. RubenVerborgh commented on Aug 14, 2017

    @RubenVerborgh
    ContributorAuthor

    Regarding using the full databrowser, my two cents would be to not enable this by default, for the following reasons:

    • I think it is more complicated to use than Warp, and might not be suitable for everybody.
    • Since it feels more like a full application than Warp, it might give people the impression that databrowser = Solid.

    For the last point, a redirect to a public space (such as indeed solid.github.io) might change that impression for some users. This is also what currently happens with Warp.

  8. RubenVerborgh commented on Sep 1, 2017

    @RubenVerborgh
    ContributorAuthor

    Proposal: use #567 (Data Browser).

  9. added a commit that references this issue on Sep 3, 2017
    da916e6
  10. RubenVerborgh commented on Sep 3, 2017

    @RubenVerborgh
    ContributorAuthor

    Data Browser proposal implemented in #573.

  11. added a commit that references this issue on Sep 5, 2017
    9e6e2a4
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    blockerbugpriority-highto be used for important issues and pull requests that need to be addressed soon

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions