Yes, there could be various ways of packaging it. Right now, you literally just need the sn_httpd binary and the handful of angular text files (js, css, html, etc). The docker container just bundles these together so you can just run the container and then point your browser at it (like I do in the screenshots - on localhost:8080).
I should be able to push a pre-built version of the container up to docker hub or AWS registry too, which will make life easier. Then you would just need to have docker support on your device to run it.
I think the issues with docker connecting to my local test net are only my issues too (which are only needed for dev, obviously). When we get another test net, I’ll try pointing it to there and see how we get on. I suspect it will be smooth enough!
There are other options too. The angular static files could be baked into sn_httpd too, to create a single binary with everything in it. These could be built to different targets and run directly. It could figure out where the live safe network is by itself too. So, you would then just run the binary and point a browser at it - pretty simple!
Going one step further again, you can create standalone apps, which are basically web apps under the hood (e.g. electron). These could integrate the sn_httpd binary and the angular code and wrap it all in a single app to load/use on the desktop. I don’t think it is too tricky, it is just a matter of time/effort really!
So, lots of options. It’s just a case of assembling the components in the most useful and accessible way. For some, a hosted web gateway may be super handy. For others, local instance is better, where it can’t be blocked or censored. Once we have a working native safe browser again, we will get some more options there too!
Thanks, appreciated! I’ve toyed with creating a CLI version for giggles too. I know there are some markdown readers out there and it would just be a case of squirting the data to these in a simple way. There is something more immutable about a CLI too for some reason!
I’ve created a sn_httpd release and built binaries for Linux and Windows 64 too.
If you download the binary, then create the static directory (from the same directory as the binary) with associated i-am-immutable-client files, you should be able to run it that way too (including windows!). Static files are here:
I was planning on writing this up in some blog posts, which talk through the components and design. They maybe better to share with a wider audience, but I don’t mind if anyone wants to link this post anywhere.
The code isn’t my finest work, as its mostly a prototype, but I’m sure folks get that!
That’s awesome! I really appreciate you taking the time to give it a spin!
If the instructions need some refinement (they probably do! ), any notes or even a PR would be welcomed. I know there are a few moving parts to pull together still, but hopefully it wasn’t too bad!
You should stick some images in your test blog there too. It’s quite surprising how quick they load when the browser is instructed to cache them indefinitely.
I want to explore some markdown extensions for music and video links too. From what I’ve read, it should be possible. Being able to stream safe network video and audio to a clear net browser would be pretty cool!
./sn_start_testnet.sh confused me.
I had some issues here but I figured those out. Definitely user error.
The other issue was simply that I did not read the instruction properly.
I was using http://localhost:8080/blog/yourblog
instead of /blog/<blog-index-safe-url>/article/<article-safe-url>
that was due to this post and me not reading the entire README as suggested.
Those were my only hurdles, so nothing really.
Looking at my MyTestBlog though both Home & Article are active (not the case in your screenshot) where have I gone wrong here? Clicking on either clears the screen until I use the back arrow.