Document logging commands
This commit is contained in:
parent
b7791762c9
commit
fa25fa3d1c
@ -16,6 +16,7 @@ jobs:
|
|||||||
repository: registry:8080/dockerhubcache/library/node
|
repository: registry:8080/dockerhubcache/library/node
|
||||||
username: build
|
username: build
|
||||||
password: ((local_registry_key))
|
password: ((local_registry_key))
|
||||||
|
insecure: true
|
||||||
inputs:
|
inputs:
|
||||||
- name: siterepo
|
- name: siterepo
|
||||||
caches:
|
caches:
|
||||||
@ -35,6 +36,7 @@ jobs:
|
|||||||
repository: registry:8080/blasthavers/deploy-base
|
repository: registry:8080/blasthavers/deploy-base
|
||||||
username: build
|
username: build
|
||||||
password: ((local_registry_key))
|
password: ((local_registry_key))
|
||||||
|
insecure: true
|
||||||
inputs:
|
inputs:
|
||||||
- name: sitegen
|
- name: sitegen
|
||||||
- name: siterepo
|
- name: siterepo
|
||||||
|
@ -293,3 +293,31 @@ commands.delay(0.1, "yourusername;yourpassword");
|
|||||||
The delay will allow for the connection to be made before you actually attempt the password.
|
The delay will allow for the connection to be made before you actually attempt the password.
|
||||||
Be aware that if you use this pattern, your MUD password will be stored in your browser and will
|
Be aware that if you use this pattern, your MUD password will be stored in your browser and will
|
||||||
be viewable by anyone with local access to your browser.
|
be viewable by anyone with local access to your browser.
|
||||||
|
|
||||||
|
## Logging and log management
|
||||||
|
|
||||||
|
Sometimes it's helpful to keep logs of what you do in a game.
|
||||||
|
|
||||||
|
Type `#log mudname logname`, where mudname is the name of a MUD you connected to, and
|
||||||
|
logname is any name you pick for the logs to stored (to be used when you retrieve them).
|
||||||
|
You can also use `off` as a special logname to turn off logging.
|
||||||
|
|
||||||
|
The logs are stored in your browser, so you need to use other commands to manage them.
|
||||||
|
Note the storage is separate for each domain you access worldwideportal on.
|
||||||
|
|
||||||
|
Use `#listlogs` to see what logs are stored in the browser - how many under each logname.
|
||||||
|
|
||||||
|
Use `#downloadlogs logname min_date max_date` to retrieve logs. You can optionally leave
|
||||||
|
out `min_date`, in which case only logs up to `max_date` for that logname will be in the
|
||||||
|
download, or leave off both `min_date` and `max_date` to retrieve all logs. Note that
|
||||||
|
downloading a large set of logs can take a long time. Once done, a save dialog in your
|
||||||
|
browser will let you save the file. Dates must be formatted according to ISO 8601, e.g.
|
||||||
|
as 2024-10-05T01:35:51Z - but you can leave off the end. Download ranges is based on
|
||||||
|
sorting, `#downloadlogs foomud 2024-10-05 2024-11-05` would include records from
|
||||||
|
`2024-10-05T01:02:03Z`, because that comes after `2024-10-05` in normal alphabetical
|
||||||
|
sort order, but before `2024-11-05`. It would not include records from `2024-11-05T00:00:00Z`,
|
||||||
|
because that comes after `2024-11-05` in alphabetical sort order.
|
||||||
|
|
||||||
|
Use `#deletelogs logname min_date max_date` to permanently delete logs from the browser.
|
||||||
|
As with downloadlogs, the `min_date` can be left off, or you can leave off both `min_date`
|
||||||
|
and `max_date`. Date formats are the same as for `#downloadlogs`.
|
||||||
|
Loading…
Reference in New Issue
Block a user