#solid

5267 (done)

/ configedit / Leave a comment

Becoming a Solid IDP

  • deploying CSS on a remote machine means you are a public accessible Pod Provider
  • the pure installation of CSS is relatively simple (a couple of npm commands) but there is more needed, e.g. the certificates, the underlying web server (if wanted) or the configuration of the server, the service and the setup of the webroot
  • detailed steps can be seen here https://gist.github.com/ewingson/dbfee4d329c803aed0b0bd87e7a2fa00 but this may vary depending on the hosting service provider and the booked virtual server (this must be a root machine, means you need ssh-access as user root)
  • I’m not really sure, if using the SSL-options of the provider can simplify the process, I doubt that
  • I’ll try to get into the details now
  1. sign the domain name at a hosting service provider
  2. sign the server package at a hosting service provider (here it is called “virtual server” and you get along with 10 bucks a month) (this may be a different provider as 1., but for simplicity I’ll recommend booking both on the same service)
  3. OS: Debian 10 (or if possible 11)
  4. the price of 1. depends on the Top Level Domain, the price of 2. depends on the booked (virtual) hardware (vCores, storage, memory)
  5. you don’t need to book SSL cause that’s handled by letsencrypt
  6. configure a root-password for the vServer (accessed by IP or FullyQualifiedDomainName)
  7. connect the IP of 2. to the domain name, this means setup of DNS (IPv4 and IPv6) and a configuration in the customer GUI of the provider
  8. ssh into the machine (console: ssh root@ip, then confirm storing the key on the local machine)
  9. install node and npm (I’ll find out my versions, maybe possible to use nvm to handle different versions, but I chose to go without) ((>= node 12.7 is needed, I use node 12.22.7 and npm 6.14.15 but this is, because I have NSS and CSS running on the same machine, for CSS I’ll recommend @latest of node and npm))
  10. decide whether using an nginx (web server) with solid or ONLY the solid server (I’ll recommend using nginx because we need a reverse proxy, as which nginx can act)
  11. https://certbot.eff.org/ to install certbot (possibly using pip)
  12. run certbot command
  13. leave the certbot command hanging and open a parallel browser window with the DNS settings of the hosting service provider
  14. DNS-Challenge works with deploying two DNS-Text-Records in a parallel window, call them both _acme-challenge I think, detailed instructions how to call the file in the instructions of the terminal of 12.
  15. wait a minute or 2, if want to be sure 5, but that’s a bit paranoid
    1. will tell you where the keys are stored
  17. delete the text records
  18. install nginx latest (if I remember right including a thing or option called “express”)
  19. npm install -g @solid/community-server
  20. proceed with https://gist.github.com/ewingson/dbfee4d329c803aed0b0bd87e7a2fa00
  21. check and install https://github.com/solid/community-server-recipes for mashlib, adjust the service command
  22. I think this gives an impression of the complexity
  23. be careful with the steps, cause one single mistake can fuck up the whole system
view raw Becoming a Solid IDP.md hosted with ❤ by GitHub

5168 (imagine)

/ configedit / Leave a comment

Introduction

tags: solid intro

Solid is a standard. a protocol. a specification. a movement. a server. a project. a set of rules. a layer. an OS. a community. a site. a platform. a system. a method. a social thing. a thing. that’s it but it is more than the sum of all the parts.

timbl was worried about the direction, that his invention took. so we needed an update. the data should belong to their owners (the user) and not be kept in silos and walled gardens.

so what do you get ? a Webid and a Pod.

the webid is a simple URL (well it could be server.net/i)

the pod is your place on the web. a data storage.

let’s switch to mother tongue. imagine:

… Du brauchst Name, Adresse, Email, Login, bank account, phone, (von mir aus shoesize für den Schuhmacher) nur noch ein einziges Mal eingeben.

… Die Firmen (ja, alle) müssen DICH fragen, ob sie Deine Daten benutzen dürfen und Deine Daten (Fotos, Likes, Kommentare, Musik, Histories, Chats) werden zu Deinem Wohl arbeiten.

… Deine Apps werden interoperabel, das heisst App A versteht und spricht mit App B und wenn Dir App xyz nicht mehr gefällt, entziehst Du ihr die Rechte und benutzt stattdessen App lmn.

… Du kannst Deine Körper- und Fitnesswerte Deinem Arzt zur Verfügung stellen und er kann Dir die beste Therapie zur Verfügung stellen.

… Ein Ruck geht durchs Netz und Du brauchst nur noch ein einziges Login (früher Email, dann “mit Google, mit Twitter, etc.”) jetzt Login mit ID. [nun, in der Realität geschieht wahrscheinlich Folgendes]

… Hate Speech und Fake News wird ein Riegel vorgeschoben.

… Deine Computing-Power in der Hosentasche arbeitet 24/7 für Dich.

… wir verstehen uns und helfen uns untereinander.

… Diversity, Equity und Inclusion wird ein Topic.

Naiv, gewiss, aber wir arbeiten daran. lass mich noch 2 oder 3 Links anfügen.

solidproject.org solidservers.org solidweb.org

genug für den Moment, bald mehr, ausführlicher/detaillierter, und hoffentlich leicht verständlich. GOTO 10.

view raw Introduction.md hosted with ❤ by GitHub

4781 (Pod Provider)

/ configedit / Leave a comment

Becoming a Solid IDP

  • deploying CSS on a remote machine means you are a public accessible Pod Provider
  • the pure installation of CSS is relatively simple (a couple of npm commands) but there is more needed, e.g. the certificates, the underlying web server (if wanted) or the configuration of the server, the service and the setup of the webroot
  • detailed steps can be seen here https://gist.github.com/ewingson/dbfee4d329c803aed0b0bd87e7a2fa00 but this may vary depending on the hosting service provider and the booked virtual server (this must be a root machine, means you need ssh-access as user root)
  • I’m not really sure, if using the SSL-options of the provider can simplify the process, I doubt that
  • I’ll try to get into the details now
  1. sign the domain name at a hosting service provider
  2. sign the server package at a hosting service provider (here it is called “virtual server” and you get along with 10 bucks a month) (this may be a different provider as 1., but for simplicity I’ll recommend booking both on the same service)
  3. OS: Debian 10 (or if possible 11)
  4. the price of 1. depends on the Top Level Domain, the price of 2. depends on the booked (virtual) hardware (vCores, storage, memory)
  5. you don’t need to book SSL cause that’s handled by letsencrypt
  6. configure a root-password for the vServer (accessed by IP or FullyQualifiedDomainName)
  7. connect the IP of 2. to the domain name, this means setup of DNS (IPv4 and IPv6) and a configuration in the customer GUI of the provider
  8. ssh into the machine (console: ssh root@ip, then confirm storing the key on the local machine)
  9. install node and npm (I’ll find out my versions, maybe possible to use nvm to handle different versions, but I chose to go without) ((>= node 12.7 is needed, I use node 12.22.7 and npm 6.14.15 but this is, because I have NSS and CSS running on the same machine, for CSS I’ll recommend @latest of node and npm))
  10. decide whether using an nginx (web server) with solid or ONLY the solid server (I’ll recommend using nginx because we need a reverse proxy, as which nginx can act)
  11. https://certbot.eff.org/ to install certbot (possibly using pip)
  12. run certbot command
  13. leave the certbot command hanging and open a parallel browser window with the DNS settings of the hosting service provider
  14. DNS-Challenge works with deploying two DNS-Text-Records in a parallel window, call them both _acme-challenge I think, detailed instructions how to call the file in the instructions of the terminal of 12.
  15. wait a minute or 2, if want to be sure 5, but that’s a bit paranoid
    1. will tell you where the keys are stored
  17. delete the text records
  18. install nginx latest (if I remember right including a thing or option called “express”)
  19. npm install -g @solid/community-server
  20. proceed with https://gist.github.com/ewingson/dbfee4d329c803aed0b0bd87e7a2fa00
  21. check and install https://github.com/solid/community-server-recipes for mashlib, adjust the service command
  22. I think this gives an impression of the complexity
  23. be careful with the steps, cause one single mistake can fuck up the whole system
view raw Becoming a Solid IDP.md hosted with ❤ by GitHub

4730 (autodidact pins down the progress)

/ configedit / Leave a comment

some more thoughts

  • NSS running 5.6.8
  • ^5.6.9 possibly needing node ^6.0 (resolved, use nvm)
  • CSS running 1.1.0
  • both on the same machine
  • a possible solution would be nvm
  • refactoring the auth-upgrade
  • new index.html template
  • auth-panel-meetings too much of it
  • wednesday SolidOS
  • umai and media-kraken working fine with CSS
  • webclip working fine with solidcommunity.net
  • databrowser needs an entry-point within its own context
  • monitor npmjs
view raw some more thoughts.md hosted with ❤ by GitHub