Mercurial > libervia-backend
view doc/libervia-cli/event.rst @ 4212:5f2d496c633f
core: get rid of `pickle`:
Use of `pickle` to serialise data was a technical legacy that was causing trouble to store
in database, to update (if a class was serialised, a change could break update), and to
security (pickle can lead to code execution).
This patch remove all use of Pickle in favour in JSON, notably:
- for caching data, a Pydantic model is now used instead
- for SQLAlchemy model, the LegacyPickle is replaced by JSON serialisation
- in XEP-0373 a class `PublicKeyMetadata` was serialised. New method `from_dict` and
`to_dict` method have been implemented to do serialisation.
- new methods to (de)serialise data can now be specified with Identity data types. It is
notably used to (de)serialise `path` of avatars.
A migration script has been created to convert data (for upgrade or downgrade), with
special care for XEP-0373 case. Depending of size of database, this migration script can
be long to run.
rel 443
author | Goffi <goffi@goffi.org> |
---|---|
date | Fri, 23 Feb 2024 13:31:04 +0100 |
parents | d6837db456fd |
children |
line wrap: on
line source
======================== event: events management ======================== Event commands allows you to create/modify or get data about an event, and to manage your invitees. get === Get metadata about one or more event(s). By default the events are displayed in a format readable, and ``--verbose, -v`` can be used one or more times to show more or less data. As usual, :ref:`libervia-cli_output` can be used to get the data in a different way. example ------- Retrieve events from personal agenda:: $ li event get Get details of a next dentist appointment from personal agenda:: $ li event get -i dentist -vv .. _libervia-cli_event_create: create ====== Create a new event. You can specify the starting time of the event with ``-S TIME_PATTERN, --start TIME_PATTERN``, and either its end time with ``-E TIME_PATTERN, --end TIME_PATTERN`` or its duration with ``-D DURATION, --duration DURATION``. ``--start`` and ``--end`` use a full :ref:`time_pattern` when ``--duration`` uses the relative delta part of it. It's mandatory when creating and event to specify starting and ending time (or duration). If your organsise an item, the ``--rsvp`` flag should be used: it will use the default RSVP form which ask for attendance. If you want to request more information to your guest, ``--rsvp_json JSON`` can be used: the JSON argument is a data dict as described in ``data_dict_2_data_form`` function where the ``namespace`` key is not necessary (it's set automatically): .. autofunction:: libervia.backend.tools.xml_tools.data_dict_2_data_form If the event links to an other one, ``--external JID NODE ITEM`` can be user example ------- Create an event about to celebrate New Year:: $ li event create -s some_pubsub@example.net -n urn:xmpp:events:0/party -i new_year_eve_2022 --start 2022-12-31 --end 2023-01-01 -d "Party to celebrate new year" -H https://example.net/some_image.jpg "New Year's Eve" Add the dentist appointement on coming Tuesday to our personal agenda:: $ li event create -S tuesday -D "1 hour" Dentist modify ====== This command works in the same way as libervia-cli_event_create_ but modify an existing event: all arguments are optional, those specified will override the original ones from the updated event. If the ending time or duration must be modified, the starting must be specified again. example ------- Change the head picture from the New Year event created above:: $ li event modify -s some_pubsub@example.net -n urn:xmpp:events:0/party -i new_year_eve_2022 -H https://example.net/some_other_image.jpg invitee ======= Subcommands to handle guests. Please check :ref:`libervia-cli_event_invitee`.