[docs] Specify which steps are required when installing freeradius for development about django-freeradius

[cappe87]

I agree! Il mar 26 dic 2017, 13:56 Giuseppe De Marco <[email protected]> ha scritto:

…

Could we open two task for ansible-freeradius and ansible-freeradius-dev How this sounds to you? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#77 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AGOvUU52WSwP7X90EPY7tpV0qmVCcH0-ks5tEOz9gaJpZM4RMwD0> .

[peppelinux]

Could we open two task for

ansible-freeradius
and
ansible-freeradius-dev

How this sounds to you?

[peppelinux]

@cappe87 merry xmas :)

We could start extracting what we consider good for us, from this if you agree:

https://github.com/peppelinux/UniTools/blob/master/freeradius/freeradius_3.0.12_debian9.setup.sh

[peppelinux]

@edoput
the guide is very very good!
https://github.com/openwisp/django-freeradius/blob/master/docs/source/general/freeradius.rst

[edoput]

Extracting the script steps to something more readable should be fine.

The guide is very good as it addresses how to configure freeradius but it's not done as it miss key points

• SQL is needed when developing?
• we don't refer that there is a dummy_sql module to remove

Adding a note like this is more than enough to discourage

the sql module is not needed for development purpose of django-freeradius

[nemesifier]

Let's keep it simple and advise to configure as we explain, expert users will figure it out by themselves if they don't need anything, newbies would get confused if we start branching the documentation into different cases.

I'm getting confused because we have different issues related to similar aspect of the docs:

• #53
• #75
• and this one #77

Is there any duplication among these 3 or can we make 3 different independent Google Code-In tasks?

PS: #75 is already a GCI task and @h0n3yc4k3 is working on it in #74

[nemesifier]

thx for the status update