dspaan wrote:But that sounds more like 'Vicidial documentation' as opposed to 'Vicibox'. Will this be a complete guide for Vicidial or only the installation of Vicibox?
If it's going to be a total documentation portal for everything Vicidial than i propose to migrate these docs too:
http://vicidial.org/docs/
Well the idea behind the ViciBox Manual is for anything that's ViciDial adjacent on the back end. So a good example would be if someone had an implementation of Fail2Ban that worked with or around ViciDial/ViciBox. Such an implementation would require you to log into the CLI and start hacking away at stuff under the hood. That's the sort of thing I was envisioning for the ViciBox Manual.
This to me could apply to things like backup/migration instructions, VPN setups, carrier issues, or even a cursed VM section. I converted the ViciBox Manual to a community project to make it easier to participate. That's why it's sourced on github and hosted by readthedocs. The restructured text format takes a hot minute to get used to and I still need to add a style/coding guide for things. There is already some of that on there but that's more for reading conventions. There's a handful of actual coding conventions that are user defined that have to be followed but it's not too bad.
As far as legacy ViciDial docs I'm not opposed to moving those into the ViciBox Manual. What I am mostly looking to add myself are things that deal with the CLI and hacking around in the OS. If there's a particular one that you are interested in having included then you are welcome to submit it. If you want to do the initial work of getting it laid out I can then go through and figure out how to best integrate it in. The idea should be that what gets submitted is reformatted to make it easier to read and understand. This would include breaking the document down into various sections, adding screenshots or explanations or code blocks where needed, etc. At a minimum any submission should take the original text and chop it down into readable sections. Adding screenshots or any of that is up to whoever is doing the work.
What I want to avoid is just a copy-paste blob of the original text. If that is all that's needed then I can create a "Legacy/Other Docs" sections on the ViciBox Manual to link to them. Might not be a bad idea to add that anwyays.