I’m waiting 
Done!
I’m a brand new github user…but when I try to login into the dokuwiki a get a 404 error (page not found) with github as well with google+
I cannot see you in the database of users
ok, the url move broke up the github authentication, will do it ASAP
OK but if you want I can register within internal dokuwiki user database.
Oauth is back again for github and google, for internal authentication you can use the register link
2 Likes
OK I’m in!
Thanks @stephdl
I was looking this page
http://wiki.nethserver.org/doku.php?id=developer
And I ask myself: Can we put variuos tags on a how to?
Actualy all is in the same melpot.
I would suggest to make section for this develloper page: environment ( set up the environment, repository), e-smith, netgui, rpm.
What is your opinion about this?
The same observation for this page:
http://wiki.nethserver.org/doku.php?id=howto_s
The howto create howto is on the middle of all.
I would suggest a special section to place this one a the first and separation how to.
And create section to organize as coresystem, application. If possible to organize as general audience, intermediate and advanced,
2 Likes
You can use several tags when you declare a category at the end of your wiki page, see http://wiki.nethserver.org/doku.php?id=howto:wiki_help#tag_plugin
when you search a page you have two possibilities, at least this is how I do
- with the search box in the top, it is really powerfull…I use it often
- with the category filter of the left menu http://wiki.nethserver.org/doku.php?id=category but indeed it asks to have several tags/categories.
I don’t know if we need to do other pages for each category, from my experience the http://wiki.nethserver.org/doku.php?id=category should be enough.
I suppose that for the beginning we can look after the category page and find a good (some) relevant tag(s) for your content…if it doesn’t exist, then you must determine what is/are the best tag(s) for the page you are writing.
the category page will list all tags with at least one page, it is automatic.
2 Likes
I agree and sustain your point. It will be necessary to add more tags for the how-to’s.
BR
Bogdan
Don’t misunderstand me, I don’t want more pages per categories.
One page is good, but more section or chapter to be clear and more structured
then somewhere in a page add :
{{topic>Tag1}}
and you will retrieve all page tagged with Tag1
Actually in the tag ‘developer’ I made two subcategories ‘rpm’ and ‘git’, but indeed I should do and third category ‘esmith’ for all ‘perldoc’ I did.
1 Like
done
another way if you want to list all tags in another page (without created it) → see developer:rpm_documentation [NethServer Wiki]
look → we hold some documentations on the wiki, see the git category
look → We hold some documentations on our wiki, browse the rpm category
add {{tagpage>TagName}}
1 Like
IMHO at the moment the tags will do the job but if we have much more Howto’s it will be difficult to find the right one. As I mentioned before
If we have more Howto’s I suggest to categorise it to get a structure in as @Jim mentioned it.
I just looked at howto’s section in the wiki… excellent BUT howtos MUST be NS compliant…
please, read:
http://wiki.nethserver.org/doku.php?id=howto:how_to_make_nethserver_os_x_friendly_-avahi
and
http://wiki.nethserver.org/doku.php?id=howto:how_to_make_nethserver_os_x_friendly-_afp
there are (way too) many problems:
- direct editing of conf file
- no template/fragments creation
- development tools installation on the server
- no warning about the risks of doing so
- no suggestion to use a different/test server to compile packages
- no warning about compiling rpms using external (unknown) sources
- use of rpm instead of yum (for dependencies solving)
let me point out that I don’t expect people knows everything about NS’ internals since the beginning, but some rules must be used…
- everything that is not NS compliant should be evidenced
- everything that can reduce security must be evidenced
otherwise, we could have some compromised/broken server just following an “official” howto, and that’s no good at all
as usual, my 2c
3 Likes
As always: feel free to adjust documentation or send recommendations for adjustment.
Often documentation is WIP (work in progress). It often needs additional work and proofreading. Since the wiki does not have a ‘staging’ area, this must be done in the wiki itself.
1 Like
Believe or not, I was thinking about this.
Actually I not satisfied with developer tools on the server.
I was Imagining to make this procedure in a VM and at the end put the rpm on the server to install it.
Thank you for your suggestion, and for the interrest to enhance the existing stuff
@stephdl
In the dokuwiki is on the left side the links: Discoursee which links to the community. Why did you name it as “Discourse” and not as “Community”? Normally Community is used as a reference and to use Discourse create confusion IMHO.
4 Likes
I support this suggestion, I always tried to name this place “Community” because what matters here are people not the tool used.
2 Likes
done…
4 Likes