The design of the system allowsįor easy replacement of the packages if better choices becomeĪvailable. The SME Server uses the "best of breed" packagesįrom the open source community. Other third-party developers are used, wherever
#Netatalk src rpm centos software
Software for the SME Server is packaged using RPM Package
#Netatalk src rpm centos Pc
The SME Server runs on commodity PC hardware, and supportsĪ range of configurations and devices such as:Ī variety of Internet connectivity options, including cablemodem, DSL/PPPoE, static IP and dialup The CentOS packages are used unmodified,Īnd configured automatically to emulate "best practice" from Packaged in such a way that no knowledge of Linux is required to SME Server is based on the CentOS Linux server distribution, Into a complete, easy-to-use network server and firewall. On a standard PC in less than thirty minutes, converting it The SME Server is a software package that can be installed
#Netatalk src rpm centos how to
GNU General Public License Preamble TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION How to Apply These Terms to Your New Programs GNU Free Documentation License PREAMBLE APPLICABILITY AND DEFINITIONS VERBATIM COPYING COPYING IN QUANTITY MODIFICATIONS COMBINING DOCUMENTS COLLECTIONS OF DOCUMENTS AGGREGATION WITH INDEPENDENT WORKS TRANSLATION TERMINATION FUTURE REVISIONS OF THIS LICENSE ADDENDUM: How to use this License for Advanced customization principles Leveraging the provisioning system for users, groups, and i-bays Programmatically creating users, groups, and i-bays Reserving accounts to avoid conflicts with user, group, or i-bay names Adding new account properties Using the LDAP server Data backup Using the MySQL database Sending email messages Managing the firewall Starting up programs automatically upon system boot V. Advanced customization of the SME Server 15. The SME Server development environment Configuring your development environment Modifying an SME Server package SourceForge developer CVS access IV. Packaging your application A quick introduction to RPMs Selecting and creating RPMs for your application Setting up your RPM development environment Building an RPM 14. Getting to know how to customize the SME Server Exercise 1: Changing a configuration template Exercise 2: The magic of templates Exercise 3: Using events and actions Exercise 4: Adding new configuration database parameters Exercise 5: Adding a user interface screen Exercise 6: Adding a new event type Exercise 7: Thought experiment - adding a new server application Customization guidelines 13. Getting started Creating a development environment 12. How to create an SME Server package - step by step 11. The server-manager web interface The web directory Web function scripts Common files Panel definitions III. Process startup, supervision and shutdown Process startup Process supervision: runit (and supervise) 10. Configuration file templates Design of the template system The Text::Template module Template expansion 9.
Configuration database Overview The configuration databases Namespace issues 7. Design philosophy Principle 1: Automating best practice Principle 2: Simplicity Principle 3: Extensibility Principle 4: Reliability 5.
0 kommentar(er)
