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.
I was using mimac.bizzi.org/huskydocs but the site seems to haveThank you for the reporting, I'll try to fix it as sson as I can, maybe an Apache update modified the confif.
stopped working.
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/ ?
I was using mimac.bizzi.org/huskydocs but the site seems to have
stopped working.
How about http://download.huskyproject.org/docs/ ?
and there is documentation in the projects's github wiki. very
confusing for new users ...
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 ...
How about http://download.huskyproject.org/docs/ ?
Thank you for the reporting, I'll try to fix it as sson as I can, maybe
an Apache update modified the confif.
and there is documentation in the projects's github wiki. very confusing for new users ...
Fixed, thank you and sorry for the issue. :)
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.
Thanks I'll take a look. I do find trying to figure out the bestIt's not too complicated. :)
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. :)
I just need to write a script that will automate all the pullingCheck back in this Echo Area, Michael provided one to me. :)
and building :)
How about http://download.huskyproject.org/docs/ ?
Is it better to remove it from wiki?
How about http://download.huskyproject.org/docs/ ?
Is it better to remove it from wiki?
I'm not on latest but in the past the hpt doc were build from a .texi
file during complilation.
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.
How about http://download.huskyproject.org/docs/ ?
Is it better to remove it from 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.
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.
GitHub repo contains sources and it is not good to place anything
compiled from the sources to the repo including a prebuilt ascii text.
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.
Is it possible to use other mechanisms of github? I noticed that
github could handle releases too.
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.
There is no sense to publish the documentation yearly, it is much
better to publish it when it changes as it is now.
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.
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.
OK, I understood you. Maybe the easiest way will be publishing docs in html and plain text via "GitHub releases".
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?
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 about huskyproject.github.io? Would it be possible to publish the documentation there?
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?
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).
| Sysop: | altere |
|---|---|
| Location: | Houston, TX |
| Users: | 66 |
| Nodes: | 4 (0 / 4) |
| Uptime: | 15:43:44 |
| Calls: | 599 |
| Files: | 7,638 |
| Messages: | 291,683 |