@kikobar@acc4e.com
@kikobar@acc4e.com avatar

kikobar

@kikobar@acc4e.com

Human being. Temporary dweller of this planet. Permanently searching for ways of making tomorrow better than today. Open-minded. All ideas are welcome.

Opinions here are my own; I am not speaking on behalf of any individual, company or organisation.

Boosts don't mean "I support"; they mean "I think you should read this".

Posts and replies are searchable and licensed under Creative Commons Attribution-NoDerivatives 4.0 International License, see https://creativecommons.org/licenses/by-nd/4.0/

This profile is from a federated server and may be incomplete. Browse more on the original instance.

kikobar, to transit
@kikobar@acc4e.com avatar
fabio, to history
@fabio@manganiello.social avatar

#Platypush 1.0 is out!

Itโ€™s been 10 months and 1049 commits since the latest release of Platypush, 7 years since the first commit, and 10 years since the first release of its ancestor, https://github.com/blacklight/evesp.

The past few months have been quite hectic and I have nearly rewritten the whole codebase, but I feel like the software is now at a stage where itโ€™s mature and stable enough to be used by a larger audience.

The changelog is quite big, but it doesnโ€™t even cover all the changes, as many integrations have been completely rewritten.

The biggest (breaking) change is the merge between plugins and backends. Now, except for those integrations that actually listen for messages and execute them (like HTTP and Redis), all the other integrations are plugins. This greatly simplifies the configuration and removes a lot of confusion for new users.

The Docker support has been greatly improved too. There are now officially supported multi-arch images for Alpine, Debian, Ubuntu and Fedora, an official docker-compose.yml file, and both the platydock and platyvenv utilities have been almost completely rewritten to seamlessly automate the creation and configuration of containers and virtual environments (respectively) starting from a single config.yaml.

And the Python API has become much simpler and consistent. No more __init__.py files that the user had to manually create in each subfolder of scripts, just drop a .py file with your automation in the scripts dir and itโ€™ll be picked up. Moreover, the most common imports are now available on top level as well, and thereโ€™s no more need to create procedures/hooks/crons with varargs:

from platypush import run, when
from platypush.events.sun import SunsetEvent

@when(SunsetEvent)
def sunset_lights_on():
  run('light.hue.on')

Thereโ€™s also a revamped documentation portal, which now includes both the wiki and the plugin reference.

Most of the integrations have been rewritten at different degrees, and in the process many bugs have been squashed, many features added and many APIs updated to be more consistent, so make sure to check the documentation pages of your integrations in order to migrate.

And if you have more requests or questions, feel free to open a ticket, a PR or ask on the Lemmy server.

https://blog.platypush.tech/article/Platypush-1.0-is-out

kikobar,
@kikobar@acc4e.com avatar

Congrats @fabio
Thanks for sharing!

kikobar, to keyboards
@kikobar@acc4e.com avatar

Now I type with this... They a lot of fun to use.

is great!

yeri, to climate
@yeri@superuser.one avatar
kikobar,
@kikobar@acc4e.com avatar

@yeri are we late yet? ๐Ÿ™„

  • All
  • Subscribed
  • Moderated
  • Favorites
  • โ€ข
  • JUstTest
  • ngwrru68w68
  • everett
  • InstantRegret
  • magazineikmin
  • thenastyranch
  • rosin
  • GTA5RPClips
  • Durango
  • Youngstown
  • slotface
  • khanakhh
  • kavyap
  • DreamBathrooms
  • provamag3
  • ethstaker
  • osvaldo12
  • tester
  • cubers
  • cisconetworking
  • mdbf
  • tacticalgear
  • modclub
  • Leos
  • anitta
  • normalnudes
  • megavids
  • lostlight
  • All magazines