-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Get my dev env working for Solid OS and Pivot #1
Comments
My first goal is to see if I can use the Solid OS Dev Container to edit a text somewhere in Solid OS and see it appear. In order to get a clean write-up of these issues, I'll checkout https://github.com/SolidOS/solidos from scratch and start a new dev container for it. |
Open the folder in VSCode, and click 'reopen in dev container' |
Opening Solid OS in a Dev Container (including all the cloning, installing, and building) takes about 15 minutes. After that you can use three terminal windows inside VSCode:
And then in theory, you should be able to browse to http://localhost:3000 and see your solid-panes changes live. Testing that now. |
Hm, that fails -> SolidOS/solidos#214 At the same time, I think I can (temporarily) deprioritise this issue since for the SolidOS/solid-panes#390 we are already testing on https://solidcommunity.net:8443 and for solid-contrib/pivot#4 we discussed to try to do it server-side after all. So pausing work on this issue now, until further notice. |
As part of (or a basis of) the TUBS project we want to offer Solid pod hosting. This involves:
The Solid Community has a number of feature requests for this server, and there are also some bugs that surface from the NSS-to-CSS migration of https://solidcommunity.net.
The milestone for the NSS-to-CSS migration of https://solidcommunity.net is here: https://github.com/solid-contrib/pivot/milestone/1
Some of these issues (in particular SolidOS/solid-panes#390 and solid-contrib/pivot#4) require changes to the mashlib stack, which is why I need to get my dev environment for https://github.com/SolidOS/solidos working.
That's what I've been working on this morning; in particular, due to some problems with node-gyp and python, I went for adding a dev container to Solid OS. That in itself is now working well.
But I'm running into a few issues with the Solid OS dev env. I'm not reporting them directly because at this point it seems pretty likely that they're my own user errors. Documenting them here until I get more of a handle on them.
The text was updated successfully, but these errors were encountered: