Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Aug 11 2021 20:52
    @RubenVerborgh banned @mikeadams1
Jeff Zucker
@jeff-zucker
If anyone would like to try the beta of the mashlib against CSS, get an account on solidweb.me and then go to the address below and use its go bar to go to your solidweb account and login. https://jeff-zucker.solidcommunity.net:8443/browse.html
aveltens
@aveltens:matrix.org
[m]
works! great!
jaxoncreed
@jaxoncreed
Quick question: Is there any way to create new classes to plug into CSS without forking the library and adding them there? I see in https://github.com/solid/community-server-recipes that its posible to set up new configurations without modifying the main repo, but these examples don’t show using classes outside of the main library. Is there a way to do this? If so, where can I find an example?
Justin Bingham
@justinwb
@jaxoncreed we just went through the same thing - if you ping @angel.araya:matrix.org he can show you how we went about it
jaxoncreed
@jaxoncreed
Thanks
Ángel Araya
@angel.araya:matrix.org
[m]

@angel.araya:matrix.org It's hard to tell from just the example above, but the Components.js error seems to indicate that it's not finding your resource store. Perhaps this can help, it's another project that has a configuration that uses CSS as a dependency and also has a config with custom stores: https://github.com/KNowledgeOnWebScale/solid-calendar-store/

jaxoncreed (jaxoncreed) I based most of my work in this working example. But let me know if your get stuck anywhere, it might be something I also ran into.

Ruben Verborgh
@RubenVerborgh
@jaxoncreed Also an example in https://github.com/RubenVerborgh/solid-hue
Ruben Verborgh
@RubenVerborgh
Enjoy v2.0.0 of the Community Solid Server — https://github.com/solid/community-server/releases/tag/v2.0.0
Justin Bingham
@justinwb
:clap:
Ruben Verborgh
@RubenVerborgh
Thanks all for your support!
Pete Edwards
@edwardsph
Congratulations - great work!
Ruben Taelman
@rubensworks
Nice work! :rocket:
Justin Bingham
@justinwb

The Solid Editorial Team would like to increase communication with and receive feedback from community members and organizations who are actively implementing Solid compliant server or client technologies, with an aim to:

  • Learn which features or issues are high / low priority, and where applicable, adjust timelines or editorial priorities. This could impact the order in which features are integrated into Solid specifications
  • Surface, discuss, and track open questions or concerns
  • Learn the best way to structure subsequent sessions, and other mechanisms for feedback (e.g. surveys)

Date: Thursday, October 21st, 2021
Duration: 1 Hour
Start Time: UTC: 2PM / EDT (Boston): 10AM / BST (London): 3PM / CEST (Brussels): 4PM / JST (Tokyo): 11PM
URL: https://global.gotomeeting.com/join/654935701

This session is open to the public, and we welcome everyone to attend this session. In an effort to maintain a focus on implementation feedback, only individuals actively engaged in Solid compliant server or client implementation work will be queued to speak by the moderator.

To actively participate, an implementer must:

  1. Be a member of the Solid Community Group

  2. RSVP in advance to feedback@solidproject.org. Must be able to cite active implementation work. Legitimate citations include links to Github repositories, links to product descriptions on websites, or otherwise credible explanation of active work efforts.

Implementers are requested to submit questions, issues, or topics in advance to feedback@solidproject.org, ideally as part of the RSVP. Given the allotted time, space on the agenda will be limited.

Minutes will be recorded, and posted to https://github.com/solid/specification/tree/main/meetings.

Also see https://forum.solidproject.org/t/solid-implementer-feedback-session/4754.

1 reply
Justin Bingham
@justinwb
Please note - for the implementer session posted above - we’re changing the meeting to use https://meet.jit.si/solid-implementer-feedback rather than the posted gotomeeting URL.
Matthias Evering
@ewingson
@RubenVerborgh @joachimvh a) how do I update CSS on the shell ? I tried npm upgrade -g @solid/community-server but became no "success"-logging. that leads me to part b) how do I find the installed version of CSS ? curl -i https://solidweb.me gives no info. do we have a -v option ?
my guess if the upgrade doesn't work would be a npm install in the hope that it overwrites the actual, but want this to make sure works and discuss with you before
Matthias Evering
@ewingson
//of course I meant "got", not "became", but that's cause it's not my mother tongue ;-)
Joachim Van Herwegen
@joachimvh
@ewingson I actually don't have a lot of experience with global npm packages but from what I read you have to use npm update -g ...
good point that the server doesn't expose its version, we might want to update our x-powered-by header in the future to include the version number
Ruben Verborgh
@RubenVerborgh
I can confirm it's npm update -g @solid/community-server
We have a version command indeed:
$ community-solid-server --version
2.0.0
We purposely do not expose a version number over HTTP for security reasons
Matthias Evering
@ewingson
thanx
Matthias Evering
@ewingson

@joachimvh @RubenVerborgh @bourgeoa @timbl @jeff-zucker @aveltens:matrix.org @SharonStrats @theRealImy
cross-post in node-solid-server and community-server

I got NSS 5.6.9-beta with old index.html and CSS 1.1.0 running on solidweb.org and solidweb.me.
unfortunately I have messed up node installations when introducing nvm.
but... both systems are up and running.
if I got time and leisure (in the sense of the german word "Muße") I will build the root machine from scratch and bring everything on the actual level (after getting okay from you), so potential 5.6.11 and 2.0.0 including nvm from the very beginning.

back-up'ing the users and save them should be no problem.

have a good weekend and stay tuned. ewingson

aveltens
@aveltens:matrix.org
[m]
Thanks for your efforts. I do not have any important data there but it is very useful for testing
Matthias Evering
@ewingson
saving and restoring will work. I did that once before.
Tim Berners-Lee
@timbl
Are the two server s running on the same filestore?
@ewingson ^ ? That would be an interesting test of switching between them
Matthias Evering
@ewingson
you mean they use the same kb in the codebase ? no completely indepentent, they just share the same root machine. I got /var/www/solidweb.org and /var/www/solidweb.me setup. so different webroots, different certs, one NSS and one CSS, just the same IP.
Jeff Zucker
@jeff-zucker
@ewingson - no, that's not what Tim is asking. We want to know how we are going to transition user data from NSS to CSS so what he is asking is if it's possible to serve the data in the NSS user pod files on your file system through the CSS server. That should be possible and will make the eventual transition of solidcommunity.net from NSS to CSS easier.
Matthias Evering
@ewingson
maybe I just didn't understand the question
Jeff Zucker
@jeff-zucker
do you understand now?
Matthias Evering
@ewingson
same filesystem so should be possible to move from /var/www/solidweb.org/data/ to /var/www/solidweb.me/data/
Jeff Zucker
@jeff-zucker
why move it?
Matthias Evering
@ewingson
no I don* t wanna move it but it would be possible
Jeff Zucker
@jeff-zucker
why not just point CSS's file data to the existing data?
with -f when you start it
Matthias Evering
@ewingson
I don't intend to switch between them
Jeff Zucker
@jeff-zucker
well starting CSS that way will not impact the files (except it might create index.html and profile if you have those in the templats) and the point is not to switch between them, but to learn what problems we'll face when we transition.
although I think a key point is that solidweb.me serves pods as https://solidweb.me/user/ whereas NSS does and CSS can serve them as https://user.solidweb.me/
So there is no easy transition of webids
Matthias Evering
@ewingson
although I think a key point is that solidweb.me serves pods as https://solidweb.me/user/ whereas NSS does and CSS can serve them as https://user.solidweb.me/
isn't it the other way around ?
Jeff Zucker
@jeff-zucker
Solidweb currently serves with the user as a sub-directory. NSS does and CSS can serve with the user as a subdomain.
Matthias Evering
@ewingson
oh sorry I read dot org
Jeff Zucker
@jeff-zucker
You should change the link on solidweb.me to the databrowser to its permanent URI: https://solid.github.io/mashlib/dist/browse.html and you may want to do what CSS does on its user pod roots - add ?uri=https://solidweb.me/username/ to the link and that way it will not only open the databrowser, but open it to the user's CSS pod.
Matthias Evering
@ewingson
but the way I have it now, they can Log in
https://solid.github.io/mashlib/dist/browse.html shows public stuff, doesn't it ?
Jeff Zucker
@jeff-zucker
No, you are pointing to a broken pre-version of it on my pod. The final version is on github at the URI I just gave. You must first go to a pod, then you can login. The login button is hidden unless you are on a pod. If you add the ?uri=foo, it will open that pod with a login button.