10 ms·

It would be cool to provide a deb repo as a way of subscribing to your blog. So `apt update` will pull in all blog posts, `man your-blog` will show the latest

by yegle 3y ago

It would be cool to provide a deb repo as a way of subscribing to your blog. So `apt update` will pull in all blog posts, `man your-blog` will show the latest post with links to the index of all your other posts.

zerojames 3y ago
_adds to their TODO list :D_
- tutfbhuf 3y ago
  Please also create an AUR package for Arch Linux.
  - basilgohar 3y ago
    Release as a Flatpak and make it distro agnostic!
    - gkbrk 3y ago
      Make it even better and release an AppImage!
      - edvinbesic 3y ago
        Even even better, put it on the web so it’s accessible from anywhere
        abulman 3y ago
        wow, there. Lets not get crazy there. It's plenty enough to support multiple package managers, but what you are considering is just too much!
        hk1337 3y ago
        Okay, just create an iOS application.
out_of_memory 3y ago
first thing came to my mind when i read the blog. it would be a very cool thing. i hope this becomes a thing.
dcminter 3y ago
On the one hand this idea is brilliant - on the other hand if it caught on, there are some obvious opportunities for malware intrinsic to the approach :'( I think I'd be too chicken to subscribe.
- codetrotter 3y ago
  Make the CI pipeline create a Docker image that contains Debian slim and the man pages installed.
  - rezonant 3y ago
    On the other hand, it's Docker, so you know every blog will use their own base image.
    - astrea 3y ago
      Guys: Serve your blog via Docker itself. Docker image names are _already_ URLs. You could literally just have people do `docker pull myblog.com/recipes:latest` or `myblog.com/recipes:lasagna`. Edit: and navigate like so: `docker image myblog.com/recipes` to list all recipes. God I love APIs.
      - mrmattyboy 3y ago
        And add search logic to the tag, so you don't need to know the name of the post, just the right word(s) to find it and let the "I'm feeling lucky" algorithm pick the right one :)
        TeMPOraL 3y ago
        And then someone ports that back to regular Docker, and we get a whole new dimension of software supply chain security issues :).
      - tomxor 3y ago
        I can't tell how much of this is sarcasm. Turning what started out as a problem of "How do you load arbitrary remote TROFF sources into man" into "throw docker at it" because someone suggested an intermediate solution of "apt" which introduces security issues and no one posed that there might be an alternative that obviates any need for containerization. I mean these two things could be further from each other on the scale of incredibly lightweight to massively heavyweight. Or maybe this is a microcosm of why docker and kuberwhatever happens so much.
zerojames 3y ago
This is now in progress. https://github.com/capjamesg/jamesg.blog.deb https://github.com/capjamesg/jamesg.blog.deb has all you need to build a man-page-only deb file using: git clone https://github.com/capjamesg/jamesg.blog.deb https://github.com/capjamesg/jamesg.blog.deb cd jamesg.blog.deb dpkg-deb --build --root-owner-group jamesg.blog sudo dpkg -i jamesg.blog.deb You should see: ... Processing triggers for man-db (2.9.1-1) ... Which indicates the man page for `man jamesg.blog` is available. There is just a placeholder in there for now. I will perhaps finish this tomorrow! NB: This may become a blog post soon :D
- deleted 3y ago
  [deleted]
potta_coffee 3y ago
Release your blog as an Electron application please.
- usr1106 3y ago
  How would that fit on a RK07 disk?
dredmorbius 3y ago
There's some precedent for this. Debian used to provide access to the now-defunct Linux Gazette, and still offers numerous informational packages (package docs, manpages, info pages, RFCs, Linux HOWTOs, and more), all of which can be served locally through the dww package, "Read all on-line documentation with a WWW browser": <https://packages.debian.org/bookworm/dwww https://packages.debian.org/bookworm/dwww> (Joerg Jaspert was the former maintainer of Linux Gazette packages: <https://people.debian.org/~joerg/ https://people.debian.org/~joerg/> (2002).) This remains to me one of the best examples of integrating information delivery and documentation on an operating system I've ever encountered. Notably, it makes both manual and info documents more useful and usable than their traditional terminal-based interfaces. There are Debian-associated blogs (Debian Planet), though I don't believe that was ever packaged for Debian itself. Frankly, RSS is probably a better option for blog subscription.
- anthk 3y ago
  You could read LG without dwww just fine by just pointing the file:/// path. I remember getting all of those with the Debian Sarge DVD's, good stuff, among the Anarchist Faq, the 'Derivations' math book, and tons offline documentation when I didn't have internet at home.
  - dredmorbius 3y ago
    dwww need not be limited to localhost access, meaning that a single Debian system can serve docs to others (LAN, intranet, public Internet, ...). Of course, all of the documentation that's exposed via dwww is accessible on that host's filesystem. But dwww also provides a few additional affordances: Web-formatted output, a directory of installed documentation (organised by source / type), and (if you have swish++ installed), full-text search.

by yegle 3y ago

zerojames 3y ago

_adds to their TODO list :D_

tutfbhuf 3y ago
Please also create an AUR package for Arch Linux.
- basilgohar 3y ago
  Release as a Flatpak and make it distro agnostic!
  - gkbrk 3y ago
    Make it even better and release an AppImage!
    - edvinbesic 3y ago
      Even even better, put it on the web so it’s accessible from anywhere
      - abulman 3y ago
        wow, there. Lets not get crazy there. It's plenty enough to support multiple package managers, but what you are considering is just too much!
        hk1337 3y ago
        Okay, just create an iOS application.

out_of_memory 3y ago

first thing came to my mind when i read the blog. it would be a very cool thing. i hope this becomes a thing.

dcminter 3y ago

On the one hand this idea is brilliant - on the other hand if it caught on, there are some obvious opportunities for malware intrinsic to the approach :'( I think I'd be too chicken to subscribe.

codetrotter 3y ago
Make the CI pipeline create a Docker image that contains Debian slim and the man pages installed.
- rezonant 3y ago
  On the other hand, it's Docker, so you know every blog will use their own base image.
  - astrea 3y ago
    Guys: Serve your blog via Docker itself. Docker image names are _already_ URLs. You could literally just have people do `docker pull myblog.com/recipes:latest` or `myblog.com/recipes:lasagna`. Edit: and navigate like so: `docker image myblog.com/recipes` to list all recipes. God I love APIs.
    - mrmattyboy 3y ago
      And add search logic to the tag, so you don't need to know the name of the post, just the right word(s) to find it and let the "I'm feeling lucky" algorithm pick the right one :)
      - TeMPOraL 3y ago
        And then someone ports that back to regular Docker, and we get a whole new dimension of software supply chain security issues :).
    - tomxor 3y ago
      I can't tell how much of this is sarcasm. Turning what started out as a problem of "How do you load arbitrary remote TROFF sources into man" into "throw docker at it" because someone suggested an intermediate solution of "apt" which introduces security issues and no one posed that there might be an alternative that obviates any need for containerization. I mean these two things could be further from each other on the scale of incredibly lightweight to massively heavyweight. Or maybe this is a microcosm of why docker and kuberwhatever happens so much.

zerojames 3y ago

This is now in progress. https://github.com/capjamesg/jamesg.blog.deb https://github.com/capjamesg/jamesg.blog.deb has all you need to build a man-page-only deb file using: git clone https://github.com/capjamesg/jamesg.blog.deb https://github.com/capjamesg/jamesg.blog.deb cd jamesg.blog.deb dpkg-deb --build --root-owner-group jamesg.blog sudo dpkg -i jamesg.blog.deb You should see: ... Processing triggers for man-db (2.9.1-1) ... Which indicates the man page for `man jamesg.blog` is available. There is just a placeholder in there for now. I will perhaps finish this tomorrow! NB: This may become a blog post soon :D

deleted 3y ago
[deleted]

potta_coffee 3y ago

Release your blog as an Electron application please.

usr1106 3y ago
How would that fit on a RK07 disk?

dredmorbius 3y ago

There's some precedent for this. Debian used to provide access to the now-defunct Linux Gazette, and still offers numerous informational packages (package docs, manpages, info pages, RFCs, Linux HOWTOs, and more), all of which can be served locally through the dww package, "Read all on-line documentation with a WWW browser": <https://packages.debian.org/bookworm/dwww https://packages.debian.org/bookworm/dwww> (Joerg Jaspert was the former maintainer of Linux Gazette packages: <https://people.debian.org/~joerg/ https://people.debian.org/~joerg/> (2002).) This remains to me one of the best examples of integrating information delivery and documentation on an operating system I've ever encountered. Notably, it makes both manual and info documents more useful and usable than their traditional terminal-based interfaces. There are Debian-associated blogs (Debian Planet), though I don't believe that was ever packaged for Debian itself. Frankly, RSS is probably a better option for blog subscription.

anthk 3y ago
You could read LG without dwww just fine by just pointing the file:/// path. I remember getting all of those with the Debian Sarge DVD's, good stuff, among the Anarchist Faq, the 'Derivations' math book, and tons offline documentation when I didn't have internet at home.
- dredmorbius 3y ago
  dwww need not be limited to localhost access, meaning that a single Debian system can serve docs to others (LAN, intranet, public Internet, ...). Of course, all of the documentation that's exposed via dwww is accessible on that host's filesystem. But dwww also provides a few additional affordances: Web-formatted output, a directory of installed documentation (organised by source / type), and (if you have swish++ installed), full-text search.