Compare commits
2 Commits
master
...
fediverse-
Author | SHA1 | Date |
---|---|---|
Fabio Manganiello | 5631c3a57d | |
Fabio Manganiello | 29cfb6e889 |
|
@ -18,3 +18,4 @@ $ git clone https://git.platypush.tech/platypush/blog.git
|
|||
$ cd blog
|
||||
$ madblog
|
||||
```
|
||||
|
||||
|
|
Binary file not shown.
Before Width: | Height: | Size: 189 KiB |
File diff suppressed because it is too large
Load Diff
|
@ -95,7 +95,7 @@ First things first: in order to get your assistant working you’ll need:
|
|||
|
||||
I’ll also assume that you have already installed Platypush on your device — the instructions are provided on
|
||||
the [Github page](https://git.platypush.tech/platypush/platypush), on
|
||||
the [wiki](https://git.platypush.tech/platypush/platypush/wiki/Home#installation) and in
|
||||
the [wiki](https://git.platypush.tech/platypush/platypush/-/wikis/home#installation) and in
|
||||
my [previous article](https://blog.platypush.tech/article/Ultimate-self-hosted-automation-with-Platypush).
|
||||
|
||||
Follow these steps to get the assistant running:
|
||||
|
|
|
@ -325,10 +325,10 @@ can run a UNIX-like system and it has HTTP access to the instance that hosts
|
|||
your bot.
|
||||
|
||||
Install Python 3 and `pip` if they aren't installed already. Then install
|
||||
Platypush with the `rss` integration:
|
||||
Platypush with the `rss` and `mastodon` integrations:
|
||||
|
||||
```bash
|
||||
[sudo] pip3 install 'platypush[rss]'
|
||||
[sudo] pip3 install 'platypush[rss,mastodon]'
|
||||
```
|
||||
|
||||
Now create a configuration file under `~/.config/platypush/config.yaml` that
|
||||
|
@ -359,12 +359,6 @@ Fortunately, the admins of `nitter.net` still do a good job in bridging Twitter
|
|||
timelines to RSS feeds, so in `rss.subscriptions` we use `nitter.net` URLs as a
|
||||
proxy to Twitter timelines.
|
||||
|
||||
> UPDATE: `nitter.net` has got a lot of traffic lately, especially after the
|
||||
> recent events at Twitter. So keep in mind that the main instance may not
|
||||
> always be accessible. You can consider using other nitter instances, or, even
|
||||
> better, run one yourself (Nitter is open-source and light enough to run on a
|
||||
> Raspberry Pi).
|
||||
|
||||
Now create a script under `~/.config/platypush/scripts` named e.g.
|
||||
`mastodon_bot.py`. Its content can be something like the following:
|
||||
|
||||
|
|
|
@ -95,8 +95,8 @@ camera module.
|
|||
This post assumes that you have already installed and configured Platypush on your system. If not, head to my post on
|
||||
[getting started with Platypush](https://blog.platypush.tech/article/Ultimate-self-hosted-automation-with-Platypush),
|
||||
the [readthedocs page](https://docs.platypush.tech/en/latest/), the
|
||||
[repository page](https://git.platypush.tech/platypush/platypush) or
|
||||
[the wiki](https://git.platypush.tech/platypush/platypush/wiki).
|
||||
[Gitlab page](https://git.platypush.tech/platypush/platypush) or
|
||||
[the wiki](https://git.platypush.tech/platypush/platypush/-/wikis/home).
|
||||
|
||||
Install also the Python dependencies for the HTTP server, the MLX90640 plugin and Tensorflow:
|
||||
|
||||
|
|
|
@ -475,7 +475,7 @@ no cloud!), or loaded from a URL.
|
|||
## Work in Progress
|
||||
|
||||
The extension is still under development, and I’m open to suggestions, tickets, and pull requests on the
|
||||
[repository page](https://git.platypush.tech/platypush/platypush-webext). Two features, in particular, are next on my
|
||||
[Gitlab page](https://git.platypush.tech/platypush/platypush-webext). Two features, in particular, are next on my
|
||||
roadmap:
|
||||
|
||||
### Integration with the Platypush WebSocket protocol
|
||||
|
|
|
@ -68,7 +68,7 @@ a few sensors on a small Raspberry Zero is guaranteed to take not more than 5-10
|
|||
|
||||
The flexibility of Platypush comes however a slightly steeper learning curve, but it rewards the user with much more
|
||||
room for customization. You are expected to install it via [pip](https://pypi.org/project/platypush/) or
|
||||
the [git repo](https://git.platypush.tech/platypush/platypush), install the dependencies based on the plugins you
|
||||
the [Gitlab](https://git.platypush.tech/platypush/platypush) repo, install the dependencies based on the plugins you
|
||||
want (although managing per-plugin dependencies is quite easy via `pip`), and manually create or edit a configuration
|
||||
file. But it provides much, much more flexibility. It can listen for messages on MQTT, HTTP (but you don’t have to run
|
||||
the webserver if you don’t want to), websocket, TCP socket, Redis, Kafka, Pushbullet — you name it, it has probably got
|
||||
|
|
Loading…
Reference in New Issue