SAFE Beaker Browser: Installation Walkthrough


#21

not quite, definitely has errors at every step of the installation :stuck_out_tongue:


#22

heh, that’ll be the problem if that’s not rebuilding then,

Sorry windowsers! you’ll have to please be patient for a windows build. Proper packaging and apps for all OSs will likely be my jumping off point for dev, so I’d hope to get them to yall ASAP.


#23

Installataion works fine, thanks @betterthantrav for the excellent and very clear instructions. But… I can’t browse any SAFE sites. {“errorCode”:-1004,“description”:“DnsError::ServiceNotFound”} or {“errorCode”:-18,“description”:“CoreError::GetFailure::GetError::NoSuchData”}

Do I need to configure a proxy somewhere?


#24

No, but you do need to run the launcher.

Edit: you also need to remove .safenet from any address. For example ian.safenet becomes just ian. The browser will then automatically convert it to safe://ian.

The only reason to use a proxy is because modern browsers don’t recognize the safe:// protocol. The proxy converts something a modern browser can recognize ie http://ian.safenet into a format the safe:// protocol can recognize and use.


#25

If you are using the Safe POC, remove the .safenet at the end of the address.


#26

I fear if we don’t stop using .safenet this confusion will continue to grow.

.safenet was meant to be a temporary fix to the limitations of modern browsers. This is why we are building a safe:// specific browser.


#27

Definitely agreed.

Need to nip this in the bud very early.

Good thing we’re only alpha 1 right now


#28

Fear not, when they are ready to switch to the safe:// syntax all they will have to do is to take down the url for the .pac file. This way all .safenet links will be broken and people will have to make the changes to the safe:// syntax if they want their safesite to keep on working. So I don’t see a big risk of being stuck with it.


#29

Until the SAFE Beaker Browser is up and operational. The only option to develop a website is .safenet

This can create the risk of .safenet becoming widely accepted and a temporary solution turning in to a more permanent solution.


#30

I understand your point of view, I just don’t feel the urgency. Anyway I don’t want to derail this thread, we may agree to disagree.


SAFE Browser Application Packages || Dev Update
#31

I am trying to install on Ubuntu 16.04 and I get the following error when running npm install

npm install

> electron-prebuilt@1.2.7 postinstall /home/rviertel/beaker/node_modules/electron-prebuilt
> node install.js

sh: 1: node: not found
npm WARN optional Skipping failed optional dependency //appdmg:
npm WARN notsup Not compatible with your operating system or architecture: appdmg@0.3.10
npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: fsevents@1.0.15
npm WARN beaker No repository field.
npm WARN beaker No license field.
npm ERR! Linux 4.4.0-51-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "install"
npm ERR! node v4.2.6
npm ERR! npm  v3.5.2
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn

npm ERR! electron-prebuilt@1.2.7 postinstall: `node install.js`
npm ERR! spawn ENOENT
npm ERR! 
npm ERR! Failed at the electron-prebuilt@1.2.7 postinstall script 'node install.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the electron-prebuilt package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node install.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs electron-prebuilt
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls electron-prebuilt
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /home/<username>/beaker/npm-debug.log

any suggestions?


#32

I recommend downloading a SAFE Browser binary from GitHub instead.
Here’s the latest stable version: SAFE Browser v0.4.2 :slight_smile:


#33

I didn’t realize there was a binary. Thanks for pointing that out!

I installed nodejs with

sudo apt-get install nodejs

but still got the errors. Either way, its working now so thanks.


#34

The electron-prebuilt package tries to run node install.js, but it doesn’t work since your Node.js binary is called nodejs.

You could add the following symlink to fix the issue:

sudo ln -s /usr/bin/nodejs /usr/bin/node

#35

thanks that worked perfectly