A wee update for any folks looking to get rid of the proxy setup.
I’ve spent the last days setting up basic app provisioning for the SAFE Beaker Browser, with some success. We now have windows, linux and osx builds! (I’ve had no linux feedback yet, but windows/osx are looking good!). Which means you can download a browser and run it alongside the SAFE Launcher to have proxy-free access to the network.
Download the SAFE Beaker Browser
You can grab the windows build here.
Note: Clearnet is still enabled, and all browser data is still saved locally. This release is purely a packaging of the POC with the
If you encounter any problems, please let me know. This is still early days, so it’s likely.
The good news is, now that app provisioning is setup, future iterations should be much easier to produce. No more need to go through all the dev setup. (props to @betterthantrav for the dev-build guide there )
My main aim once the gun was fired was to get the application packaging setup. @Viv and @Krishna_Kumar recommended appveyor/travis for builds, so I fired in there (bit of a crash course for myself), but I’m please to say, after wrestling with various build problems (oh windows, how I love you), everything is working (although there’s still some room for improvement ).
This doesn’t sound like such an advancement, but it’s really nice to have builds tested quickly on all platforms, as well as being able to get full app packages built on the native platforms. So it should allow for smoother development going forward, and should remove the need for anyone to have to go through the full dev-build setup to get the browser running.
I’m away on a long-planned holiday next week, so I won’t likely be online so much. But as soon as I’m back the week after I’ll be aiming to:
- Update and stabilise safe-js. Adding in testing for all functionality.
- Implement the full safe-js API functionality in the new beaker-safe plugin so webapp devs can have a native interface to the network.
- Update the beaker plugin with a test suite and CI integration.
- Prevent non
safeprotocol access by default. ( so the safe://tester
banana does not show up).
- Update CI integration configs for smoother app deploys on all builds.
This wave of improvements should get us towards the basic SAFE Beaker Browser implementation. And after that I’ll be planning out steps for the stretch goals.