SolidOS for devs: https://github.com/solidos/solidos SolidOS Pod: https://solidos.solidcommunity.net/
timbl @timbl did
git pull origin bug/issue7 expecting it t s switch to that branch
tried … seems to work
1 reply
^^ on :8443 test server
^^ testing a new index.html page
Added a scheencast ofnit working for good measure .. playing with OBS
Just trie it between chrome and FF in fiff windows, one folder tree tracks the other one, evn if you delete a folder with more stuff in it.
Whatever happned to the folderTable pane I wonder .. should be able to do live update between the two
timbl @timbl heads off - till tomorrow
@bourgeoa there is something wrong with the test server - mashlib.js is not the same as mashlib.min.js. If you go tohttps://jeff-zucker.solidcommunity.net:8443/test/mash.html and https://jeff-zucker.solidcommunity.net:8443/test/mashmin.html, the only difference is that one uses /mashlib.js and the other /mashlib.min.js. Clicking login in mash.html opens the IDP modal as it should in the new auth. Clicking login in mashmin.html opens a popup window like the old flow.
thought it might be just me, so checked
I merged solid/folder-pane#23 after having it backwards for a bit.
Added a screencast of it working for good measure .. playing with OBS
Screencast should be nice for the solidos user documentation
@jeff-zucker
deleted the branch locally, recreated it, npm ci && npm run build
root@DESKTOP-PIRJOCS:/mnt/d/github/solid/solidos-auth-upgrade/workspaces/mashlib# git branch -d auth-upgrade
warning: deleting branch 'auth-upgrade' that has been merged to
'refs/remotes/origin/auth-upgrade', but not yet merged to HEAD.
Deleted branch auth-upgrade (was f7e9911).
root@DESKTOP-PIRJOCS:/mnt/d/github/solid/solidos-auth-upgrade/workspaces/mashlib# git checkout --track origin/auth-upgra
de
Branch 'auth-upgrade' set up to track remote branch 'auth-upgrade' from 'origin'.
Switched to a new branch 'auth-upgrade'
root@DESKTOP-PIRJOCS:/mnt/d/github/solid/solidos-auth-upgrade/workspaces/mashlib# npm ci && npm run buildWith exactly the same sizes on the test-server and also on solidos/workspaces/node-solid-server with npm ci
root@DESKTOP-PIRJOCS:/mnt/d/github/solid/solidos-auth-upgrade/workspaces/mashlib/dist# ls -al
total 24124
drwxrwxrwx 1 root root 512 Oct 3 18:57 .
drwxrwxrwx 1 root root 512 Oct 3 18:57 ..
-rwxrwxrwx 1 root root 3333 Oct 3 18:57 browse.html
-rwxrwxrwx 1 root root 589 Oct 3 18:57 databrowser.html
-rwxrwxrwx 1 root root 22462 Oct 3 18:57 mash.css
-rwxrwxrwx 1 root root 45117 Oct 3 18:57 mash.css.map
-rwxrwxrwx 1 root root 5964523 Oct 3 18:57 mashlib.js
-rwxrwxrwx 1 root root 6284529 Oct 3 18:57 mashlib.js.map
-rwxrwxrwx 1 root root 2809270 Oct 3 18:57 mashlib.min.js
-rwxrwxrwx 1 root root 9553918 Oct 3 18:57 mashlib.min.js.map
@/all - I am running into a major roadblock with handling the index.html pages in the new auth flow. Please look at https://github.com/solid/node-solid-server/issues/1619#issuecomment-933011704 and give me your thoughts.
26 replies
you use them both
in NSS we have /var/www/servername/data/user/index.html for pod root
and /var/www/servername/index.html for server root.
in CSS we have /usr/lib/node_modules/@solid/community-server/templates/root/index.html
that generates the server root in /var/www/servername/index.html
where is the template for the user pod root in CSS ?
will changes only apply for new users ?
will we take the new authN for both servers ?
things to keep an eye on...
is it the goal to make SolidOS standard on both ?
7 replies
sorry for the poor markdown
Regarding the login on the server.
I want to point to the diagram I created some time ago: https://miro.com/app/board/o9J_lsrieoc=/?invite_link_id=802499867311 about user experience (regarding onboarding).
In the ticket: solid/node-solid-server#1619 there are actually 2 issues discusses:
1) change of current login code
2) change in user experience
I want to suggest to split these in 2 separate issues because I want to discuss the UX in detail. As it is now, the user needs to login twice to the pod and is shown different UIs depending where they come from.
I also propose now to just focus on the code update to finalize the auth-upgrade.
I want to point to the diagram I created some time ago: https://miro.com/app/board/o9J_lsrieoc=/?invite_link_id=802499867311 about user experience (regarding onboarding).
In the ticket: solid/node-solid-server#1619 there are actually 2 issues discusses:
1) change of current login code
2) change in user experience
I want to suggest to split these in 2 separate issues because I want to discuss the UX in detail. As it is now, the user needs to login twice to the pod and is shown different UIs depending where they come from.
I also propose now to just focus on the code update to finalize the auth-upgrade.
12 replies
Related to documentation: I'd like your opinion on what should be standard links we'd like everyone to know about and place in prominent places on documentations (which we mentioned in previous team meetings we want to have).
Here a collected list: https://github.com/solid/solidos/discussions/65 Pls comment and add you suggestions too.
Here a collected list: https://github.com/solid/solidos/discussions/65 Pls comment and add you suggestions too.
Besides solid/node-solid-server#1619 which is now sort of settled, which needs implementing, how can I help?
Can we update the auth-upgrade issues: https://github.com/solid/solidos/issues? Which ones are solved and still open?
Can we update the auth-upgrade issues: https://github.com/solid/solidos/issues? Which ones are solved and still open?
5 replies
@bourgeoa the test server is still completely messed up. Look at these two files, they are identical except that one uses /mashlib.js and the new login flow and other uses /mashlib.min.js and the old login flow. Just click on the two login buttons to see. This means that it is really impossible to test the new auth. Please re-investigate, something is very wrong.
^^Is it possible that Jackson inadvertently changed perms on one of the files or something when he directly edited on the server?
I just fixed a long-standing bug - inability to create or read .js files with the databrowser. Fixed with solid/source-pane#24