| Age | Commit message (Collapse) | Author |
|---|
|
On refactoring,
- standardize the method names on the rescached.js to match with the
Client, for example prefixing block.d operations with Blockd.
- use the GET /block.d, GET /hosts.d, GET /zone.d to fetch the
resources instead of using GET /environment for all.
On bug fixes,
- fix updating SOA record on zone.d due to refactoring
|
|
This also allow the latest/released documentation viewed on
the web user interface under /doc path.
While at it, reformat HTML and CSS files using js-beautify and
JavaScript files using clang-format [1].
[1] https://google.github.io/styleguide/jsguide.html#formatting
|
|
Previously, the zone's records is fetched along with response from
API environment.
If zone have many records, this cause the API environment response
larger, not suited for managing environment itself.
This changes make the zone's records to be fetched immediately when
user click on one of the zone file.
|
|
The latest changes on share module changes type Zone.SOA field type,
which affect the zone.d page.
|
|
Previously, the HTTP API for deleting a record is by passing the
parameters as JSON in the body.
This may cause issue if HTTP client does not support sending body
in DELETE method.
This changes the method to pass the parameters in the query,
DELETE /zone.d/rr?zone=<string>&type=<string>&record=<base64 json>
Parameters,
- zone: the zone name,
- type: the record type,
- record: the content of record with its domain name and value.
|
|
Previously, the request for adding new record on zone file is by passing
the zone name and type inside the path,
/zone.d/:name/rr/:type
This commit changes it to pass all parameters inside the request body
as JSON,
{
"zone": <string>,
"kind": <string>,
"record": <base64 string|base64 JSON>
}
For example, to add A record for subdomain "www" to zone file "my.zone",
the request format would be,
{
"zone": "my.zone",
"kind": "A",
"record": "eyJOYW1lIjoid3d3IiwiVmFsdWUiOiIxMjcuMC4wLjEifQ=="
}
Where "record" value is equal to `{"Name":"www","Value":"127.0.0.1"}`.
On the response, we changes it to return only the new record instead of
all record in the zone.
|
|
Previously, the the HTTP API for creating and deleting zone file is
by passing the zone file name in path of URL.
This changes move the parameter name to POST body when creating new
zone file and in the DELETE query when deleting zone file.
|
|
This is to make all terminology to be consistent, from configuration to
page URL, and API.
|
|
See https://kilabit.info/journal/2022/gpl/ for more information.
|
|
Instead of using px use em unit instead.
|
|
If the RR value is object print the value as "key=value,...".
|
|
Instead of relying on event "oninput" get the value of each record
values from the input element itself.
Also, convert type RR Type and MX Preferences to integer before passing
it to backend.
|
|
|
