"listen_on": ["192.168.1.20", 4041],

...and you should be good to go.

Upgrading cryptoGlance is easy. First off, it never hurts to make a backup copy of your entire cryptoGlance folder. Files that should be kept particularly safe are:

• /user_data folder

Next, you'll need to Enable cryptoGlance Updates on the Settings page. Then, choose your release type:

• Release: Stable code, should have very few bugs/issues (if any).
• Beta: Slightly experimental for testing new features and bug-fixes.
• Nightly: Bleeding-edge code commits, will most likely have bugs, but they shouldn't be very serious.

Windows App:

Since the Windows App works a bit differently, in the sense that it has its own webserver with PHP installed and configured, updates aren't usually frequent, and separate from the main release version numbers. However, if you do use the Windows App, it may be a good idea to check for the latest version on SourceForge from time to time. Simply install the program to the same directory. Your /user_data folder will not be overwritten.

If you've made edits to {{ install-dir }}\settings.json (optional modification for accessing cryptoGlance externally on other devices), then you'll need to re-apply them after the installation finishes.

With every major Release, we include a concise changelog of all updates contained within. Alternatively, you can check out our live commits if you are running Beta or Nightlies:

• View the Live Beta changelog
• View the Live Nightly changelog

* Remember, you can choose if you'd like to be alerted to cryptoGlance updates by checking the Settings page, and selecting Enable cryptoGlance Updates. After that, choose the version type you'd like, hit Save and you're good to go.

Q. What is the difference between the Windows and Source downloads?

A. The Windows Version is a pre-packaged solution which allows cryptoGlance to run under its own PHP web server (Mongoose), without the need to setup any external apps/services. This version is recommended for Windows users who are not familiar with server configuration.

The Run from Source version is for users who know how to setup a (simple) PHP site. An ideal use of this version is to clone the repo from Github to a virtual directory that is served by your choice application (Apache, IIS, etc.). This method allows you to update quite easily, and also prepare code that can be contributed back to the project via a pull request.

Q. I am (understandably) careful with my crypto-currency. Can I trust cryptoGlance?

A. Most definitely! The code is completely open source, and you run cryptoGlance on your own web server (even the Windows version). There's no calls to home, or anything of the sort. No private keys are requested, passwords (stored as salted hashes) and API keys are within a protected /user_data directory, excluded from source.

Q. How do I backup my cryptoGlance settings?

A. Just look for the /user_data folder in the following locations, and copy it somewhere safe:

• {{ project-root }}/user_data
• Windows App users need to backup {{ install-dir }}\application\user_data and {{ install-dir }}\settings.json (optional modification for accessing cryptoGlance externally on other devices)

Q. I cannot get cryptoGlance to run. What can I check?

A. The Windows version should work quite well out of the box, but getting cryptoGlance setup under your own web server requires a bit of knowledge. Most often times, you can search for any specific errors you see, or try the following:

Windows Version:

• Configure any firewalls/anti-virus to allow cryptoGlance.exe traffic through
• Note the default port for the Windows app is 4041. If you are configuring cryptoGlance to be externally accessible, you'll need to forward port 4041 to the IP of the Windows box running it, or change the port via the app's config file here:
• {{ install-dir }}\settings.json
• Simply open it in a text editor, and search for "listen_on": ["127.0.0.1", 4041]
• Investigate the {{ cG Install Dir }}\debug.log file for traces of errors

Running from source:

• Confirm that PHP is installed and working properly
• Ensure that the php_sockets extension is loaded via php.ini
• (Linux) Ensure that you have the following packages installed:
• apache2
• php5
• libapache2-mod-php5
• php5-json
• php5-curl
• Adjust permissions to allow for write access on the /user_data folder

Q. The cryptoGlance site loads, but after adding a rig, no data or stats are displayed. Why?

A. Your mining utility (cgminer) requires that API access is allowed. Here's an example excerpt from the .conf:

...
"api-allow" : "127.0.0.1,192.168.1/24",
"api-listen" : true,
"api-mcast-port" : "4028",
"api-port" : "4028",
...

Q. Why do certain rig commands not work?

A. Some functions require API write access in order to issue commands to the miner. An example of these would be Switch Pools, and other such commands that don't simply read data. In order to fix this, open your miner .conf file (or modify your .bat), and ensure that you have a "W:" notation before each IP that you wish to grant write access to:

"api-allow" : "W:127.0.0.1,W:192.168.1/24",

Q. After adding a pool panel, I see a lot of NULL values. What's up?

A. This is most often caused by entering any one of the pool inputs incorrectly. Try removing the panel, and adding it again with accurate information.

Q. Why is my wallet balance 0?

A. Double-check that you've entered your address information accurately. Note that cryptoGlance will never ask for private keys or any other sensitive information.

Q. Can I include cryptoGlance in my custom Linux distribution, or with hardware that I offer?

A. Yes, you may include it only in non-commercial distributions. If you wish to include it along with software or hardware that you sell, please get in touch with a channel operator in #cryptoGlance on Freenode IRC (use the chat widget on http://cryptoglance.info) to discuss.

• WebhostingHub Glyphs
• Flat icon social media by Guilherme Spigolan
• PHP Desktop
• PHP Markdown by Michel Fortin
• (elements of) PHPMailer
• Bootstrap CSS Framework

Hope you enjoy what we're trying to do here, and thanks to all of the other similar OSS projects like this for help and inspiration (we give extra special thanks to Anubis for that!).

We've put a lot of our time and effort into cryptoGlance, and it hasn't been easy. We also wanted to make this tool free to everyone, however donations keep our fire lit, and more features/improvements coming out. If you like what we've built, or at least appreciate our efforts, please send code, or a donation to any of the following addresses:

Bitcoin
12PqYifLLTHuU2jRxTtbbJBFjkuww3zeeE

Reddcoin
RiJuGDb1e1SLVaTseHeMXMUrzhei2ex5AQ

/end README.md