| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
ogServer GET /stats returns ogServer uptime in seconds.
Transform seconds to days, hours and minutes and print them in the
dashboard.
|
|
|
|
| |
If the server do not have swap, show a warning.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Otherwise, scopes with whitespaces in their names breaks the javascript
code.
From
https://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes/id:
---
Note: Technically, in HTML5, the value for an id attribute may contain
any character, except whitespace characters. However, to avoid
inadvertent errors, only ASCII letters, digits, '_', and '-' should be
used and the value for an id attribute should start with a letter. For
example, . has a special meaning in CSS (it acts as a class selector).
Unless you are careful to escape it in the CSS, it won't be recognized
as part of the value of an id attribute. It is easy to forget to do
this, resulting in bugs in your code that could be hard to detect.
---
|
| |
|
| |
|
|
|
|
| |
Otherwise, this strings are not translatable.
|
|
|
|
|
| |
Constant strings outside of a request must use lazy strings. See
flask-babel documentation for more information.
|
|
|
|
|
|
|
|
|
|
| |
* Rename "ogLives" to "ogLive images".
* Move "Number of images" table to take less space.
* Show storage data as "Storage size | Used (%) | Available (%)".
* Move "Latest images" an "ogLive images" to the bottom.
|
|
|
|
| |
Add certain statistics on memory and swap usage, as well as the uptime.
|
|
|
|
| |
Add a back button to facilitate users to return to the previous page.
|
|
|
|
|
| |
Now users can select clients only in scopes and command views, in any
other view we set the scopes tree read only.
|
|
|
|
|
| |
Change background color and round borders of active/current navbar
link to highlight it.
|
|
|
|
| |
Set the same width to all pills.
|
|
|
|
|
|
|
| |
Some css classes are common to all pills statuses, so we do not need to
add or delete those classes on status change.
It also remove "badge-info" class because is never used.
|
| |
|
|
|
|
| |
When loading any scopes view, its nav button becomes active.
|
|
|
|
|
|
| |
Group related actions in the "scopes" section inside a dropdown button.
Declutters the panel in which the buttons are displayed.
|
| |
|
|
|
|
| |
When loading any command view, its nav button becomes active.
|
|
|
|
| |
Otherwise, "image details" page lose the images tree and buttons.
|
|
|
|
|
| |
Otherwise, this actions pages lose the scopes tree and the scopes
buttons.
|
|
|
|
|
|
| |
Both "Add client" and "Client details" views use client_details.html
template. With this commit, "Add client" extends scopes.html and "Client
details" extend commands.hmlt.
|
|
|
|
|
| |
Draw selected clients from confirmation pages like selected clients from
scopes and commands pages.
|
|
|
|
| |
Otherwise, undesired removal of selected clients pills occurs.
|
|
|
|
| |
Show the number of clients and their IPs.
|
|
|
|
|
| |
Otherwise, this actions pages lose the scopes tree and the commands
buttons.
|
|
|
|
| |
Color pills to represent their state, like scopes tree.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Otherwise, scopes with dots in their names breaks the javascript code.
From
https://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes/id:
---
Note: Technically, in HTML5, the value for an id attribute may contain
any character, except whitespace characters. However, to avoid
inadvertent errors, only ASCII letters, digits, '_', and '-' should be
used and the value for an id attribute should start with a letter. For
example, . has a special meaning in CSS (it acts as a class selector).
Unless you are careful to escape it in the CSS, it won't be recognized
as part of the value of an id attribute. It is easy to forget to do
this, resulting in bugs in your code that could be hard to detect.
---
|
|
|
|
|
| |
Print large number of clients (hundreds) does not make sense, it is
unreadable.
|
|
|
|
| |
Otherwise, the list overflows the screen when users select many clients.
|
|
|
|
| |
Refactor duplicated code as a jinja macro.
|
|
|
|
|
| |
Remove code to draw selected clients. Image creation template do not use
it because only operates one client.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Extend commands.html template to keep scope tree, and action buttons
state.
When in the software inventory view, there exists two options: 'update'
or 'view'. Do not print raw json response from ogserver about the software
inventory/profile.
When vieweing the software list, print a html table using the new
template: software_list.html.
Do not print blank pages with plain text html error codes when something
goes wrong. Instead, print an error message after redirecting to the
commands view.
|
|
|
|
| |
Remove them until we add their functionality.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
On scopes and commands views, draw clients as users selects them in the
scopes tree.
Trigger client drawing on two events:
1."change" event, occurs when the user clicks a client checkbox. This
event is standard [1].
2. "show-client" event, fires when ogcp get selected clients from
localStorage and when an user checks a parent checkbox. This event is
custom.
Dot characters (".") in clients names are replaced by underscore("_")
when used as id to avoid errors.
1. https://developer.mozilla.org/en-US/docs/Web/API/HTMLElement/change_event
|
|
|
|
|
|
|
| |
If something goes wrong, the application shows an error message after
redirecting to the commands view.
Do not show blank pages with plain text error codes.
|
|
|
|
|
| |
Do not show plain text '400 Bad Request'. Instead, show error message
and return to commands view.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Extending from command.html is required for action views to mantain
the scope context on the left side column.
Enables setting dropdown button and action button as active when loading
the hardware inventory view.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Group related actions in the "commands" section inside a
dropdown button.
Declutters the panel in which the buttons are displayed.
Dropdown button jinja block name is used as prefix for the block names
of inside buttons. For example, for the image dropwdown button:
<button class="...{% block nav_image %}{% endblock %}...">
{{ _('Image') }}
</button>
Actions such as restore and create will show a jinja block inside class
attr like:
<input class="... dropdown-item{% block nav_image_restore %}{% endblock %}" ...
<input class="... dropdown-item{% block nav_image_create %}{% endblock %}" ...
|
|
|
|
| |
When loading the setup view, it's nav button becomes active.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Adds empty jinja blocks for the class attribute of all action buttons.
Child templates from command (actions) can set their nav button as
active overriding the corresponding {% block %}.
Currently, not all action templates extends the commands.html template.
This is not a problem, as the blocks are just empty.
This is a preparation for changes on each action template to extend
commands.html template.
|
|
|
|
| |
Use bold font for active nav items.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
{% block %} defined in nav template cannot be overriden by child
templates from base. This is a limitation in jinja.
Merge nav into base template so jinja blocks so no {% include %} is used
and these blocks can be overriden by child templates (commands, images,
dashboard...)
Avoid using request.endpoint to determine active nav item, decoupling
endpoint names from navigation. Instead use child templates to override
jinja blocks.
[1] https://stackoverflow.com/q/40537752
https://stackoverflow.com/a/40562662
https://github.com/pallets/jinja/issues/243
|
|
|
|
|
|
| |
Otherwise, nested scopes are not checked and mislead users.
When a scope is checked, we search all its children and check them too.
|
|
|
|
|
| |
This function stores checksum status if is checked to browser local
storage. Otherwise, it removes checksum from the storage.
|
|
|
|
|
| |
Compacts Commands view with a single "Logs" dropdown button. Dropdown
shows current log commands.
|