• Huskydocs

    From Paul Hayton@3:770/100 to All on Saturday, May 08, 2021 12:27:34
    Where is the best place to find the latest manuals for the Husky software?

    I was using mimac.bizzi.org/huskydocs but the site seems to have stopped working.

    From memory some windows versions of the software shipped with html versions and txt versions of the manuals. I looked in some of the areas I pulled down from github but can't see just a docs repo to clone.

    Thanks, Paul
    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)
  • From Tommi Koivula@2:221/360 to Paul Hayton on Saturday, May 08, 2021 07:38:03
    Hello, Paul Hayton.
    On 08/05/2021 12.27 you wrote:

    Where is the best place to find the latest manuals for the Husky software?
    I was using mimac.bizzi.org/huskydocs but the site seems to have stopped working.
    From memory some windows versions of the software shipped with html versions and txt versions of the manuals. I looked in some of the areas I pulled down from github but can't see just a docs repo to clone.

    How about http://download.huskyproject.org/docs/ ?

    Tommi

    ---
    * Origin: nntp://news.fidonet.fi (2:221/360)
  • From Fabio Bizzi@2:335/364.3 to Paul Hayton on Saturday, May 08, 2021 09:22:28
    Hello, Paul Hayton.
    On 08/05/21 12:27 you wrote:

    I was using mimac.bizzi.org/huskydocs but the site seems to have
    stopped working.
    Thank you for the reporting, I'll try to fix it as sson as I can, maybe an Apache update modified the confif.
    --
    Ciao.
    Fabio.
    --- Hotdoged/2.13.5/Android
    * Origin: ]\/[imac Boss Android Point (2:335/364.3)
  • From Oli@2:280/464.47 to Tommi Koivula on Saturday, May 08, 2021 08:40:42
    Tommi wrote (2021-05-08):

    Where is the best place to find the latest manuals for the Husky
    software? I was using mimac.bizzi.org/huskydocs but the site seems to
    have stopped working.
    From memory some windows versions of the software shipped with html
    versions and txt versions of the manuals. I looked in some of the
    areas I pulled down from github but can't see just a docs repo to
    clone.

    How about http://download.huskyproject.org/docs/ ?

    and there is documentation in the projects's github wiki. very confusing for new users ...

    ---
    * Origin: . (2:280/464.47)
  • From Fabio Bizzi@2:335/364.3 to Paul Hayton on Saturday, May 08, 2021 09:46:37
    Hello, Paul Hayton.
    On 08/05/21 12:27 you wrote:

    I was using mimac.bizzi.org/huskydocs but the site seems to have
    stopped working.

    Fixed, thank you and sorry for the issue. :)

    --
    Ciao.
    Fabio.
    --- Hotdoged/2.13.5/Android
    * Origin: ]\/[imac Boss Android Point (2:335/364.3)
  • From Fabio Bizzi@2:335/364.1 to Oli on Saturday, May 08, 2021 17:45:08
    Hello Oli!

    08 May 21 08:40, you wrote to Tommi Koivula:

    How about http://download.huskyproject.org/docs/ ?

    and there is documentation in the projects's github wiki. very
    confusing for new users ...

    It's like Debian versions, download.huskyproject.org is for the "stable" version, or better, it's a snapshot at a specified date, the github is the work
    in progress or "unstable" version (more or less) :)

    Ciao!
    Fabio
    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: ]\/[imac Rebirth Boss Point (2:335/364.1)
  • From Fabio Bizzi@2:335/364.3 to Paul Hayton on Sunday, May 09, 2021 10:12:02
    Hello, Paul Hayton.
    On 09/05/21 11:27 you wrote:

    Thanks I'll take a look. I do find trying to figure out the best
    place to get the latest Husky software a bit of a mystery. Up
    until now I have been using a repo on Github.
    It's not too complicated. :)

    The download site has a periodic "snapshot" for all the suite at GitHub, it's good for sysops that don't want to pull and build the suite every time a commit
    occours.

    The GitHub site has always the latest versions of all the software, you can clone/pull the updated piece of software and build the latest brand new version, this is useful, for example, if need to run new functionalities, or to
    solve a bug fixed in the latest version. :)

    --
    Ciao.
    Fabio.
    --- Hotdoged/2.13.5/Android
    * Origin: ]\/[imac Boss Android Point (2:335/364.3)
  • From Paul Hayton@3:770/100 to Fabio Bizzi on Sunday, May 09, 2021 20:30:05
    On 09 May 2021 at 10:12a, Fabio Bizzi pondered and said...

    It's not too complicated. :)

    :)

    The download site has a periodic "snapshot" for all the suite at GitHub, it's good for sysops that don't want to pull and build the suite every time a commit occours.

    OK thanks. Yep that makes sense

    The GitHub site has always the latest versions of all the software, you can clone/pull the updated piece of software and build the latest brand new version, this is useful, for example, if need to run new functionalities, or to solve a bug fixed in the latest version. :)

    This is fast becoming the way I like to go :)

    I just need to write a script that will automate all the pulling and building :)
    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)
  • From Fabio Bizzi@2:335/364.3 to Paul Hayton on Sunday, May 09, 2021 12:08:18
    Hello, Paul Hayton.
    On 09/05/21 20:30 you wrote:

    I just need to write a script that will automate all the pulling
    and building :)
    Check back in this Echo Area, Michael provided one to me. :)
    --
    Ciao.
    Fabio.
    --- Hotdoged/2.13.5/Android
    * Origin: ]\/[imac Boss Android Point (2:335/364.3)
  • From Paul Hayton@3:770/100 to Tommi Koivula on Sunday, May 09, 2021 11:27:17
    On 08 May 2021 at 07:38a, Tommi Koivula pondered and said...

    How about http://download.huskyproject.org/docs/ ?

    Thanks I'll take a look. I do find trying to figure out the best place to get the latest Husky software a bit of a mystery. Up until now I have been using
    a repo on Github.
    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)
  • From Paul Hayton@3:770/100 to Fabio Bizzi on Sunday, May 09, 2021 11:27:33
    On 08 May 2021 at 09:22a, Fabio Bizzi pondered and said...

    Thank you for the reporting, I'll try to fix it as sson as I can, maybe
    an Apache update modified the confif.

    Thank you for taking a look at this :)
    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)
  • From Paul Hayton@3:770/100 to Oli on Sunday, May 09, 2021 11:28:13
    On 08 May 2021 at 08:40a, Oli pondered and said...

    and there is documentation in the projects's github wiki. very confusing for new users ...

    Forgot about that bit, just went looking in each repo like HPT in the docs folder to start with... but they did not have the html ref stuff.
    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)
  • From Paul Hayton@3:770/100 to Fabio Bizzi on Sunday, May 09, 2021 11:28:36
    On 08 May 2021 at 09:46a, Fabio Bizzi pondered and said...

    Fixed, thank you and sorry for the issue. :)

    Wow, thanks :) Appreciate you putting it up there.
    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)
  • From Alan Ianson@1:153/757 to Paul Hayton on Saturday, May 08, 2021 16:33:44
    Hello Paul,

    Forgot about that bit, just went looking in each repo like HPT in the
    docs folder to start with... but they did not have the html ref stuff.

    There is an hpt.texi in the hpt/doc directory. You can make info, html and even
    a plain text from that with makeinfo. Run make in that directory and see what you get.

    The same is true for htick in the htick/doc directory although I had to mess with the makefile to get an english html or text.

    Ttyl :-),
    Al

    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)
  • From Paul Hayton@3:770/100 to Alan Ianson on Sunday, May 09, 2021 12:11:14
    On 08 May 2021 at 04:33p, Alan Ianson pondered and said...

    There is an hpt.texi in the hpt/doc directory. You can make info, html
    and even a plain text from that with makeinfo. Run make in that
    directory and see what you get.

    OK thanks :)
    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)
  • From Kai Richter@2:240/77 to Michael Dukelsky on Thursday, May 13, 2021 00:11:54
    Hello Michael!

    10 May 21, Michael Dukelsky wrote to Kai Richter:

    How about http://download.huskyproject.org/docs/ ?

    Is it better to remove it from wiki?

    Maybe i misunderstood. Did you talked about the docs itself or the link to huskyproject?

    To provide a fast and easy access to latest documentation i'd
    like to suggest to place a prebuild .txt ascii version for each
    module to the github.

    First of all I want to say that the documentation in the wiki was made partly manually, I did not manage to make it automatically, so it
    cannot be the latest version.

    Date shows 2018 and that's the reason why i was looking for a more recent version. Could it become a yearly update event?

    As to the latest documentation it can be made in several forms. Those
    who run a UNIX-like OS may clone the GitHub repo and using a simple command get info- and/or man-pages. From my point of view this is
    better than plain ascii.

    Yes, i do agree. I have to admit that i'm not on the latest version and that i'm to lazy to pull the git and do a compilation of the docs for the purpose of
    a check for the actual keywords when i tried to support the route configuration. I copied the text from the texi and edited it to ascii manually.
    Lazy as i am the idea was to have quickly accessable file for reference.

    GitHub repo contains sources and it is not good to place anything
    compiled from the sources to the repo including a prebuilt ascii text.

    I do understand. Is it possible to use other mechanisms of github? I noticed

    https://www.toolsqa.com/git/github-releases/

    that github could handle releases too. But i don't know how that work. In the long term i'd like to see the project focused at one point for latest files.

    Regards

    Kai
    --- GoldED+/LNX 1.1.4.7
    * Origin: Monobox (2:240/77)
  • From Michael Dukelsky@2:5020/1042 to Kai Richter on Thursday, May 13, 2021 15:09:36
    Hello Kai,

    Thursday May 13 2021, Kai Richter wrote to Michael Dukelsky:

    How about http://download.huskyproject.org/docs/ ?

    Is it better to remove it from wiki?

    Maybe i misunderstood. Did you talked about the docs itself or the
    link to huskyproject?

    My reply about wiki was to Oli who said that wiki was an inappropriate place for the documentation if I understood him correctly. The wiki is here:

    https://github.com/huskyproject/hpt/wiki

    To provide a fast and easy access to latest documentation i'd
    like to suggest to place a prebuild .txt ascii version for each
    module to the github.

    First of all I want to say that the documentation in the wiki was
    made partly manually, I did not manage to make it automatically,
    so it cannot be the latest version.

    So here I talked about wiki and not about download.huskyproject.org.

    Date shows 2018 and that's the reason why i was looking for a more
    recent version. Could it become a yearly update event?

    Here you talk about download.huskyproject.org. There is no sense to publish the
    documentation yearly, it is much better to publish it when it changes as it is now.

    As to the latest documentation it can be made in several forms.
    Those who run a UNIX-like OS may clone the GitHub repo and using
    a simple command get info- and/or man-pages. From my point of
    view this is better than plain ascii.

    Yes, i do agree. I have to admit that i'm not on the latest version
    and that i'm to lazy to pull the git and do a compilation of the docs
    for the purpose of a check for the actual keywords when i tried to
    support the route configuration. I copied the text from the texi and edited it to ascii manually. Lazy as i am the idea was to have quickly accessable file for reference.

    You are lazy? Oh, no! You spent much more time for editing texi, you could get the info-pages of the docs within a minute.

    Is it possible to use other mechanisms of github? I noticed that
    github could handle releases too.

    Yes, it is possible to publish the docs in GitHub releases.

    Michael

    ... node (at) f1042 (dot) ru
    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: Moscow, Russia (2:5020/1042)
  • From Kai Richter@2:240/77 to Michael Dukelsky on Friday, May 14, 2021 11:08:24
    Hello Michael!

    13 May 21, Michael Dukelsky wrote to Kai Richter:

    https://github.com/huskyproject/hpt/wiki

    Date shows 2018 and that's the reason why i was looking for a
    more recent version. Could it become a yearly update event?

    Here you talk about download.huskyproject.org.

    No. At

    https://github.com/huskyproject/hpt/wiki/hpt

    is a rev date of dec 9, 2018.

    There is no sense to publish the documentation yearly, it is much
    better to publish it when it changes as it is now.

    The latest local updates are done with the build/make update run. An online publication is for people like me who are not on the latest version. Yes, "me" are not many and maybe i'm the only one. On the other hand there are many man pages available online. The idea for yearly updates was to reduce the manual page updates but have a more recent manual than from 2018.

    text from the texi and edited it to ascii manually. Lazy as i am
    the idea was to have quickly accessable file for reference.

    You are lazy? Oh, no! You spent much more time for editing texi, you
    could get the info-pages of the docs within a minute.

    I would if it's that easy. But there is no makeinfo for my system. The steps that are required to get it can't be done in a minure and would be temporary. The "lazy" solution would be a system migration which is already in progress but because of never touch a running system the node is on the todo list with low priority. My actual situation is like the two locations of the husky project, where github is active and the sf net is still there.

    Regards

    Kai
    --- GoldED+/LNX 1.1.4.7
    * Origin: Monobox (2:240/77)
  • From Michael Dukelsky@2:5020/1042 to Kai Richter on Saturday, May 15, 2021 12:07:12
    Hello Kai,

    Friday May 14 2021, Kai Richter wrote to Michael Dukelsky:

    https://github.com/huskyproject/hpt/wiki

    Date shows 2018 and that's the reason why i was looking for a
    more recent version. Could it become a yearly update event?

    Here you talk about download.huskyproject.org.

    No. At
    https://github.com/huskyproject/hpt/wiki/hpt
    is a rev date of dec 9, 2018.

    Oh, I see.

    There is no sense to publish the documentation yearly, it is much
    better to publish it when it changes as it is now.

    The latest local updates are done with the build/make update run. An online publication is for people like me who are not on the latest version. Yes, "me" are not many and maybe i'm the only one. On the
    other hand there are many man pages available online. The idea for
    yearly updates was to reduce the manual page updates but have a more recent manual than from 2018.

    text from the texi and edited it to ascii manually. Lazy as i am
    the idea was to have quickly accessable file for reference.

    You are lazy? Oh, no! You spent much more time for editing texi,
    you could get the info-pages of the docs within a minute.

    I would if it's that easy. But there is no makeinfo for my system. The steps that are required to get it can't be done in a minure and would
    be temporary. The "lazy" solution would be a system migration which is already in progress but because of never touch a running system the
    node is on the todo list with low priority. My actual situation is
    like the two locations of the husky project, where github is active
    and the sf net is still there.

    OK, I understood you. Maybe the easiest way will be publishing docs in html and
    plain text via "GitHub releases".

    Michael

    ... node (at) f1042 (dot) ru
    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: Moscow, Russia (2:5020/1042)
  • From Oli@2:280/464.47 to Michael Dukelsky on Saturday, May 15, 2021 11:13:12
    Michael wrote (2021-05-15):

    OK, I understood you. Maybe the easiest way will be publishing docs in html and plain text via "GitHub releases".

    What about huskyproject.github.io? Would it be possible to publish the documentation there?

    ---
    * Origin: . (2:280/464.47)
  • From Michael Dukelsky@2:5020/1042 to Oli on Saturday, May 15, 2021 18:03:04
    Hello Oli,

    Saturday May 15 2021, Oli wrote to Michael Dukelsky:

    OK, I understood you. Maybe the easiest way will be publishing
    docs in html and plain text via "GitHub releases".

    What about huskyproject.github.io? Would it be possible to publish the documentation there?

    Maybe it is possible but for me it is much easier to handle the releases.

    Michael

    ... node (at) f1042 (dot) ru
    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: Moscow, Russia (2:5020/1042)
  • From Oli@2:280/464.47 to Michael Dukelsky on Sunday, May 16, 2021 10:27:23
    Michael wrote (2021-05-15):

    Hello Oli,

    Saturday May 15 2021, Oli wrote to Michael Dukelsky:

    OK, I understood you. Maybe the easiest way will be publishing
    docs in html and plain text via "Ghuskyproject.github.ioitHub releases".

    What about huskyproject.github.io? Would it be possible to publish
    the documentation there?

    Maybe it is possible but for me it is much easier to handle the releases.

    What does it mean exactly? A downloadable html or plaintext file from the release page?

    Anyway it would be good to update huskyproject.github.io with links to current releases and documentation. (The website src used to use C #includes for assembling the pages, interesting and simple approach).

    I could commit some updates (without adding anything fancy - I like plain html).

    ---
    * Origin: . (2:280/464.47)
  • From Kai Richter@2:240/77 to Oli on Sunday, May 16, 2021 09:07:52
    Hello Oli!

    15 May 21, Oli wrote to Michael Dukelsky:

    What about huskyproject.github.io? Would it be possible to publish the documentation there?

    Uh, should we? Look at the dates. Which revision is that? No, please don't answer, that's a rhetorical question. The real question is "Do we want a third place to look for latest husky stuff?"

    Regards

    Kai

    --- GoldED+/LNX 1.1.4.7
    * Origin: Monobox (2:240/77)
  • From Michael Dukelsky@2:5020/1042 to Oli on Sunday, May 16, 2021 17:45:14
    Hello Oli,

    Sunday May 16 2021, Oli wrote to Michael Dukelsky:

    OK, I understood you. Maybe the easiest way will be publishing
    docs in html and plain text via "GitHub releases".

    What about huskyproject.github.io? Would it be possible to
    publish the documentation there?

    Maybe it is possible but for me it is much easier to handle the
    releases.

    What does it mean exactly? A downloadable html or plaintext file from
    the release page?

    The same way as archives of source code and binaries were published

    https://github.com/huskyproject/hpt/releases

    an archive with documentation can be published.

    Anyway it would be good to update huskyproject.github.io with links to current releases and documentation. (The website src used to use C #includes for assembling the pages, interesting and simple approach).

    I could commit some updates (without adding anything fancy - I like
    plain html).

    Oh, it would be nice! Feel free to make a pull request.

    Michael

    ... node (at) f1042 (dot) ru
    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: Moscow, Russia (2:5020/1042)