Pétrolette issueshttps://framagit.org/yphil/petrolette/-/issues2023-09-17T18:26:10Zhttps://framagit.org/yphil/petrolette/-/issues/146Refactoring of the synchro event(s)2023-09-17T18:26:10ZyPhilRefactoring of the synchro event(s)Refresh is needed several times on the newly synced machine because of a default of [the change event](https://remotestoragejs.readthedocs.io/en/latest/js-api/base-client.html#change-events) implementation, that we are [currently](https:...Refresh is needed several times on the newly synced machine because of a default of [the change event](https://remotestoragejs.readthedocs.io/en/latest/js-api/base-client.html#change-events) implementation, that we are [currently](https://framagit.org/yphil/petrolette/-/blob/master/public/js/PTL.sync.js#L64) managing ourselves :frowning2: Either this is a new feature or I (unlikely) missed it in the docs.v1.7.xhttps://framagit.org/yphil/petrolette/-/issues/147pull petrolette.conf from git2023-12-22T21:00:18ZAlessandro Oppopull petrolette.conf from gitHello and thanks a lot for Petrolette.
I was wondering if it could make sense to add an option to pull the petrolette.conf file from github.com (or another website that uses the git protocol).
I had this idea because in this way it wou...Hello and thanks a lot for Petrolette.
I was wondering if it could make sense to add an option to pull the petrolette.conf file from github.com (or another website that uses the git protocol).
I had this idea because in this way it would be easier to prepare complex homepages about a certain topic.
Eg. If I want a tab with all the American's newspaper, instead of adding them manually, I just find a repository already made that can be updated collectively.
I hope it makes sense. :smiley:
Thanks!https://framagit.org/yphil/petrolette/-/issues/145Cannot export to OPML?2023-06-12T10:03:37ZLaurent PointecouteauCannot export to OPML?Hello!
By reading #123, I understand that Pétrolette is able to export its feeds to an OPML file. However, the "Save" button in the Pétrolette menu only delivers a JSON "petrolette.conf" file, and the "Help" window does not mention any ...Hello!
By reading #123, I understand that Pétrolette is able to export its feeds to an OPML file. However, the "Save" button in the Pétrolette menu only delivers a JSON "petrolette.conf" file, and the "Help" window does not mention any OPML support. Has the feature been disabled since or am I missing something?https://framagit.org/yphil/petrolette/-/issues/144auto hebergement via Docker - SSL Error2023-02-13T10:36:26ZJonasauto hebergement via Docker - SSL ErrorSalut Yphil !
J'espère que tout roule pour toi. Encore merci pour ton projet que j'utilise au quotidien. J'ai bazardé netvibes depuis presque un an maintenant grâce à toi. D'ailleurs, je crois qu'il faut que je relance mon don annuel, j...Salut Yphil !
J'espère que tout roule pour toi. Encore merci pour ton projet que j'utilise au quotidien. J'ai bazardé netvibes depuis presque un an maintenant grâce à toi. D'ailleurs, je crois qu'il faut que je relance mon don annuel, je suis un peu a la bourre.
Mais bref, passons les courbettes :smile:
Le site petrolette.space semble down, du coup comme je suis accro je me suis lancé dans l’auto-hébergement via une stack que j'utilise aussi au quotidien : docker, compose et lets-encrypt
J'ai créé une branche docker que je pousserais en merge request quand ça sera au point, mais je n'arrive à faire touner que le npm run dev. Et pas la prod.
L'idée est que le conteneur letsencryp gère le TLS/HTTPS, puis de rediriger le http vers le conteneur node qui lance npm start.
J'ai en gros un bad gateway sur le port 8001 lorsque le lance npm start.
Tout tourne nickel en ssl sur le port 8000 avec npm run dev.
Enfin, pour le conteneur, j'ai besoin d'un service qui tourne en front. Pas en daemon, sinon le conteneur tombe car il pense n'avoir rien a faire.
J'ai hacké ce truc avec un bête sleep.
Ou puis je voir les logs ? je peux tout a fait faire un tail-f /log comme processus actif :smile:
Grand merci pour ton aide, et encore bravo pour cet outil formidable.
Voici le docker-compose.yml :
```yaml
version: '3.7'
services:
petrolette_node16:
image: node:19
container_name: petrolette_node16
hostname: petrolette_node16
restart: on-failure
# ports:
# - 8001:8001
# - 8000:8000
labels:
# Pour un certificats géré avec Letsencrypt
# ex : https://github.com/TiBillet/Traefik-reverse-proxy
- traefik.enable=true
- traefik.docker.network=frontend
- traefik.http.routers.petrolette_node16.tls.certresolver=tlsresolver
# remplacer par votre propre DNS
- traefik.http.routers.petrolette_node16.rule=Host(`petrolette.localhost`)
- traefik.http.services.petrolette_node16.loadbalancer.server.port=8000
networks:
- frontend
volumes:
- ./:/petrolette
working_dir: /petrolette
command: "bash /petrolette/launch_docker.sh"
command: "npm install && nom run dev && sleep 50d"
networks:
frontend:
external: true
```https://framagit.org/yphil/petrolette/-/issues/141Allow hiding of individual items from feeds2023-01-22T02:09:10ZAlert DebugAllow hiding of individual items from feedsFirstly, thank you for such a well-made piece of Free Software. I'm really glad it exists, and I want to use it a lot, but unfortunately it doesn't seem to keep track of which items I've already seen, which makes the interface a bit ove...Firstly, thank you for such a well-made piece of Free Software. I'm really glad it exists, and I want to use it a lot, but unfortunately it doesn't seem to keep track of which items I've already seen, which makes the interface a bit overwhelming.
I had assumed that showing the read/unread status of each item would be a standard feature for a feed reader, so I searched through the closed issues and found the feature request in issue #121, which I agree with. I also see that you gave some very reasonable justifications for why that request couldn't be implemented.
Instead, then, I'd like to offer a design which might satisfy some users, while also respecting your objections. My main idea is that users should be able to opt in (per feed) to having the software keep track of which items are hidden, so this new functionality wouldn't be the default. When the user selects this option (at feed creation time), there can be a warning displayed that this has a performance penalty, and it could also warn them that more data about them would be stored.
Importantly, though, I want to point out that this feature should allow users to hide items from the feed without actually visiting the page that the item links to. Instead, there should be an icon next to each item (perhaps appearing on-hover) which allows the user to hide it, equivalent to "Mark as read" in an email client.
I'm imagining that the users who use this feature would aim to have no items showing in any of the feeds (equivalent to the "inbox zero method", to use another email client metaphor), so most of the time there wouldn't actually be any private or personal information stored in the database for such users.
Finally, I think it would be helpful to also add a button to show all hidden items, in case a user hides an item by mistake and wants to unhide it again. Similarly there should be a "Hide all" button, to save time if the user doesn't want to click the individual hide buttons for every item.
Thank you again for what you've created so far, and I hope that my suggestion is practical enough to be implemented.yPhilyPhilhttps://framagit.org/yphil/petrolette/-/issues/138Set port configuration inside the config file (and not the - versioned - pack...2023-01-09T10:18:48ZtobiasSet port configuration inside the config file (and not the - versioned - package.json)Hello,
Packaging the new version of petrolette for yunohost, I'm wondering about the configuration of petrolette that tend to split into multiple file. Because there is now a `petrolette.conf.json` file, you may consider to set port con...Hello,
Packaging the new version of petrolette for yunohost, I'm wondering about the configuration of petrolette that tend to split into multiple file. Because there is now a `petrolette.conf.json` file, you may consider to set port configuration inside this file instead of `package.json` ?
With this set up I would'nt have to care about `package.json` anymore !yPhilyPhil