- code repository¶
A data structure that stores a set of files and directories, plus their change history.
- privileged applications¶
Lino applications that have the “privilege” of having their developer documentation in the Lino Book. This is because explaining a framework is difficult without examples, and because applications that are actually being used are more interesting than a theoretic collection of demo projects.
- stand-alone applications¶
Lino applications that have their own developer documentation, demo projects and technical specs.
- software framework¶
A comprehensive suite of software tools, applications and documentation used by developers who write and maintain applications for their employer or their customers.
- Lino community¶
The natural and legal persons who use the Lino framework and want to collaborate with other members.
- Lino consultant¶
Knows the possibilities and limitations of the Lino framework and gives neutral advice about whether or not to choose Lino as a solution. Helps you with analyzing and formulating your needs and finding the right business partners who will implement a solution.
- service provider¶
A legal or natural person who sells services to a customer.
The work of keeping a given system running.
- demo site¶
A Lino site that contains fictive data used for demonstration or testing purposes.
- production site¶
- Lino server¶
A virtual or physical computer operated in order to run one or several Lino sites.
This makes sense for site operators who have their own server infrastructure.
- production server¶
- demo server¶
- preview site¶
A copy of the production site as it would look when using some newer version of the software.
It is made available to end users so they can preview and test an upcoming version before a site upgrade. The primary goal of a preview site is to help the site operator to test new features and to reduce stress caused by unexpected results after an upgrade.
- client device¶
This can be a desktop or notebook computer, or a mobile device.