candidtim / vagrant-appindicator Goto Github PK

UI theme (dark or light) is currently chosen automatically based on color of the pixel at coordinates 2,2. While this works in Unity, this may provide inaccurate estimation on other desktops. Users should be able to change color theme manually in the configuration.

Hello there,

Just thought it would be a nice feature if the icon was different when one or more vagrants were up, could possibly help prevent data loss if it was more visual, so if the user running the vagrant had forgotten it was running and was about to shut down their computer

Cheers

Current VM name format is " ()".

The name format needs to be updated, and, optionally made configurable. By default it should be: " ()".

Update notifications messages: make clearer.

The choice whether to display full path to only the dirname of it may be made configurable via the dedicated "check menu item", as some users may prefer having full path.

In latest Gtk3, file listener doesn't behave as previously and is not working in tests.

In latest releases Gnome 3 dropped support of app indicators in favor of persistent notification messages. This app indicator is not intended for this use and the state of it needs to be documented. This indicator will continue to work in other desktops with Gtk Indicators support.

AppIndicator should notify user if newer version is available:

1. vreify if newer version is available at startup (e.g. by searching newer releases with GutHub REST API), and, if the newer version is indeed available:
2. show popup notification
3. change icon to the one with excalmation mark?
4. add menu item saying there is a newer version; clicking on it might open a wiki page explaning how to update (basically uninstall and install newer version)

Extend the AppIndicator to support Docker, and rename eventually to something else

It is often the case that some VMs may be left in an "inconsistent" state after system restart: some running VMs may have been killed while this will be not tracked in vagrant's machine-index, which is used as the data source for the indicator. As a result, after restart, Vagrant AppIndicator shows VMs as running, while they are actually shut down.

As Vagrant's machine-index doesn't provide means to track these changes made outside of Vagrant, AppIndicator might query Vagrant to find out the states of all known machines. Querying just once att AppIndicator start will cover most of the desynchronization cases.

Could I use it to monitor another service, for example, mysql or httpd (apache)?

Sorry English, I'm Brazilian. [Google Translate]

The applet will crash at startup if no network is available:

Traceback (most recent call last):
  File "/usr/lib/python3.4/urllib/request.py", line 1182, in do_open
    h.request(req.get_method(), req.selector, req.data, headers)
  File "/usr/lib/python3.4/http/client.py", line 1088, in request
    self._send_request(method, url, body, headers)
  File "/usr/lib/python3.4/http/client.py", line 1126, in _send_request
    self.endheaders(body)
  File "/usr/lib/python3.4/http/client.py", line 1084, in endheaders
    self._send_output(message_body)
  File "/usr/lib/python3.4/http/client.py", line 922, in _send_output
    self.send(msg)
  File "/usr/lib/python3.4/http/client.py", line 857, in send
    self.connect()
  File "/usr/lib/python3.4/http/client.py", line 1223, in connect
    super().connect()
  File "/usr/lib/python3.4/http/client.py", line 834, in connect
    self.timeout, self.source_address)
  File "/usr/lib/python3.4/socket.py", line 512, in create_connection
    raise err
  File "/usr/lib/python3.4/socket.py", line 503, in create_connection
    sock.connect(sa)
OSError: [Errno 101] Network is unreachable