Every week we say hi to new friends,
what should every newcomer know about NethServer? Would you like to give some tips, advice, mistakes to avoid, starting points, mandatory topics/discussions/docs to read?
What you have learned along the way could be helpful for NethServer newbies.
NethServer is a great product That aside, it really pays to test it off first before deploying in production environment. This is so true to all systems, not just NS.
What to read? Firstly, the Documentation, then announcements, then the how-tos. Additionally, the support forums, they can learn a thing or two (okay, a lot of things!!!), they can just ask whatever they want and let’s just make sure to help them or point them to the correct solution or forum if similar questions has been asked before… no rude response.
And yes, I agree with @davidep, do not change anything by hand unless you know what you are doing.
Most OpenSource products are as good as their community, and it seems that we have an active one. Keep it coming everyone and cheers!
Plan your system: services you’ll need, how many interfaces.
Test your system: Build a virtual machine, test if your install fits
what you want to achieve.
Don’t add unneeded packages, just add exactly what you need for the
function you want. For example if you want a samba server just add samba
and firewall to secure it, but avoid installing, proxy, mailserver,
owncloud,etc.
Don’t put all your eggs in the same basket: Nethserver is great it can
perform many awesome functions, but sometimes its a better practice to have
separate servers for separate functions. I could think on a firewall ids
with proxy, and a mail or samba server.
5.Ask for help when your stuck with something, thats what the Nethserver
community is about.
If you have to mix reports from other sourcers be sure that they
disabled, and that you enable them just to install that specific package
that you need.
And what about NethServer Community? What would you recommend to a newcomer who has not yet posted?
How to break the ice? Really curious about your insights.
I tried to write down something here, how can I improve it?
a section in wiki for newcommers where there is a short explanation of the template-system, because it is special to NS (and SME)
the user guide “planing network”
the how to “db_command_tutorial”
of course the administrator manual
and the most important advice: Don’t be shy! Ask the community! There will be somebody to help you! Nobody will laugh about your question. This community is polite and respectfull, so there is no reason to be scared.
BTW: I’d like to have a overview about the signal-event commands. Is there somewhere such a document?
When you want to set up a server you need to have very clear the goal.
READ!
When we decided what we want to do, (proxy, mail server …), first of all we read the documentation, especially the sections that are relevant to our project.
The documentation allows us to know the server’s capabilities, giving us ideas for improving the project.
Finally, we find the howto related to our project.
READY!
Check if we have everything you need for the project: for the proxy/firewall we need two network cards, for your mail server must have ADSL with static IP etc.
We prepare the server hardware before proceeding with the installation of the operating system. Nethserver is optimized for the hardware present at installation
Install Nethserver using the correct settings. You can change everything, but if we know how to set it, we avoid unnecessary steps
Never use special characters such as accented letters, apostrophes etc… (I speak from personal experience)
In Nethserver no shortage of logs.
In case of problems, check what are the logs of non-functioning services (thanks google). If you ask for help to the community, bring the log, will simplify the solution of the problem.
The logs are visible both from the web interface or via shell.
We consult the support forum. Perhaps someone has already had the same problem.
The error must be reported with details.
Phrases such as
“the mail does not work”
do not help to understand how to solve the problem. We give accurate information:
"The e-mail comes back with a message
554 Mail Appears to be unsolicited "