You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I implemented an additional data accessor (see feat/ipfs-accessor) that uses the IPFS network as an underlying persistency layer. Have a look at this paper for further details.
I am wondering if there is an interest in integrating the new accessor to the main codebase. I definitely have to reactivate the pre-commit hook that I disabled. Then the contribution must be refactored, the config files must be revised, and we might have a discussion if and how the IPFS Content Identifiers (CID) should be exposed. In general, it would be nice to get some feedback on how to proceed.
Some notes on how to start the server:
git checkout feat/ipfs-accessor
# Edit the default ipfs data folder file path (default: /tmp/solid-ipfs1 )
# Start the server
node ./bin/server.js -c config/config-ipfs.json -f /
The text was updated successfully, but these errors were encountered:
As you know, CSS has been explicitly designed to allow easy integration of external modules. This seems like an excellent case to put this into practice.
I propose to publish this as a separate package, like I've for instance published solid-hue. You could add the example configuration there, and/or we could add it to the recipes. That would work really well.
We're about to publish the next CSS version, which has some changes to config structure, so you might want to keep an eye on that.
Let me know if you have any questions regarding the packaging of your module!
I like the idea of publishing it as a separate package and adding the configuration to the recipes.
Great! Then I will go with the newest version.
Actually, yes! I have some troubles while configuring the module.
I created a css-demo-module to start simple. Unfortunately, it does not work yet.
Components.js seems to load the configuration, but then it throws an error as it can not find the module.
@RubenVerborgh I actually took solid-hue as a basis, but not the newest version. Instead, I used the first commit of solid-hue. Anyway, by using the current version together with the default config of v.0.8.1 it worked.