130 lines
7.6 KiB
HTML
130 lines
7.6 KiB
HTML
<!DOCTYPE html>
|
|
<html lang="en">
|
|
<head>
|
|
<meta charset="UTF-8">
|
|
<title>Nenjim Documentation</title>
|
|
<style>
|
|
body {
|
|
font-family: Arial, sans-serif;
|
|
background-color: #f8f9fa;
|
|
color: #333;
|
|
margin: 0;
|
|
padding: 0;
|
|
}
|
|
.container {
|
|
width: 80%;
|
|
max-width: 1000px;
|
|
margin: auto;
|
|
padding: 20px;
|
|
background-color: #fff;
|
|
}
|
|
h1, h2 {
|
|
color: #0056b3;
|
|
}
|
|
.toc {
|
|
background: #e7f1ff;
|
|
padding: 10px 20px;
|
|
border-left: 4px solid #0056b3;
|
|
margin-bottom: 30px;
|
|
}
|
|
.footer {
|
|
text-align: center;
|
|
padding: 20px;
|
|
border-top: 1px solid #ddd;
|
|
margin-top: 40px;
|
|
color: #777;
|
|
}
|
|
</style>
|
|
</head>
|
|
<body>
|
|
<div class="container">
|
|
<h1>Nenjim Documentation</h1>
|
|
<div class="toc">
|
|
<h2>Table of Contents</h2>
|
|
<ul>
|
|
<li><a href="#1-introduction-to-nenjim">1. Introduction to Nenjim</a></li>
|
|
<li><a href="#2-versioning-and-dependencies">2. Versioning and Dependencies</a></li>
|
|
<li><a href="#3-updates-and-security">3. Updates and Security</a></li>
|
|
<li><a href="#4-payment-system-and-integration-with-assetaz">4. Payment System and Integration with AssetAZ</a></li>
|
|
<li><a href="#5-backing-store-and-flexibility">5. Backing Store and Flexibility</a></li>
|
|
<li><a href="#6-standardized-and-automated-package-management">6. Standardized and Automated Package Management</a></li>
|
|
<li><a href="#7-importance-of-semantic-versioning">7. Importance of Semantic Versioning</a></li>
|
|
<li><a href="#8-integration-of-plugins-and-central-registry">8. Integration of Plugins and Central Registry</a></li>
|
|
<li><a href="#9-integration-with-assetaz-and-economic-activity">9. Integration with AssetAZ and Economic Activity</a></li>
|
|
</ul>
|
|
</div>
|
|
<h1>Nenjim Documentation</h1>
|
|
<h2 id="1-introduction-to-nenjim">1. Introduction to Nenjim</h2>
|
|
<p>Nenjim is an innovative system that enables handling multiple versions of software packages simultaneously.</p>
|
|
<p>The system solves the challenge of dependencies and versioning by using unique version numbers in the naming of
|
|
packages,</p>
|
|
<p>which ensures that multiple versions of the same software package can exist side by side without conflicts.</p>
|
|
|
|
<h2 id="2-versioning-and-dependencies">2. Versioning and Dependencies</h2>
|
|
<p>Nenjim uses a method where packages are named with the version number directly in the package name. However,
|
|
this is managed in so-called journals outside of the actual code, so that the Java code itself does not depend
|
|
on Nenjim.</p>
|
|
<p>This ensures that developers do not have to worry about version conflicts, as each dependency refers precisely
|
|
to the version it needs. The system ensures that all necessary modules are available and kept up to date in
|
|
the background.</p>
|
|
|
|
<h2 id="3-updates-and-security">3. Updates and Security</h2>
|
|
<p>Nenjim automatically monitors for updates through what are called journals. If a security vulnerability is
|
|
discovered in a particular version, the developers update the journal, and all NenjimHubs will automatically
|
|
fetch the new secure version, or downgrade to a previous version until an update is ready. In this way,
|
|
updates are distributed quickly and efficiently throughout the entire network.</p>
|
|
|
|
<h2 id="4-payment-system-and-integration-with-assetaz">4. Payment System and Integration with AssetAZ</h2>
|
|
<p>To support payment for software packages, Nenjim integrates with AssetAZ. This means that developers can choose
|
|
to receive payment for their packages either as a one-time fee, as a subscription, or per use. All transactions
|
|
are handled via cryptocurrency.</p>
|
|
|
|
<h2 id="5-backing-store-and-flexibility">5. Backing Store and Flexibility</h2>
|
|
<p>Nenjim provides complete flexibility regarding where data is stored. This can be via IPFS, in a local folder,
|
|
or even in a database. The system is designed to be so flexible that developers can choose the solution that
|
|
best fits their needs.</p>
|
|
|
|
<h2 id="6-standardized-and-automated-package-management">6. Standardized and Automated Package Management</h2>
|
|
<p>One of the major advantages of Nenjim is that users no longer have to manually search for dependencies on the
|
|
Internet. Nenjim uses a standardized method to automatically find and download packages, for example via IPFS.
|
|
This means that all packages are easily accessible and can be retrieved in a consistent manner, which saves
|
|
time and ensures a more streamlined experience for both developers and users.</p>
|
|
|
|
<h2 id="7-importance-of-semantic-versioning">7. Importance of Semantic Versioning</h2>
|
|
<p>For Nenjim to function optimally, it is essential that all packages follow the principles of semantic versioning.
|
|
This means that each version of a package clearly indicates whether it is a minor update, a bug fix, or a major,
|
|
potentially incompatible change. By adhering to these versioning rules, Nenjim can easily and safely handle
|
|
updates and ensure that the system is always stable and fully functional.</p>
|
|
|
|
<h2 id="8-integration-of-plugins-and-central-registry">8. Integration of Plugins and Central Registry</h2>
|
|
<p>One of the unique advantages of using Nenjim is that applications can communicate directly with the NenjimHub to
|
|
find and integrate new plugins. Through a global registry, applications can search for plugins that implement
|
|
specific interfaces of certain versions, making it easy to extend their functionality. This flexibility allows
|
|
users to add new features or improvements, such as codecs for a video player, while also being able to see the
|
|
cost of different plugins.</p>
|
|
|
|
<h2 id="9-integration-with-assetaz-and-economic-activity">9. Integration with AssetAZ and Economic Activity</h2>
|
|
<p>Nenjim is designed to be an open and free tool for managing dependencies, versioning, and the execution of
|
|
software packages. The system can be used without any form of payment, and all basic features—such as local
|
|
injection, dependency analysis, and dynamic classloading—are available without any economic interaction
|
|
required.</p>
|
|
<p>However, in cases where the user wants to make their software publicly available to others—for example, by
|
|
propagating packages to a registry or selling their software—a small economic cost will be associated with
|
|
these actions.</p>
|
|
<p>To support this kind of activity, Nenjim uses the digital AssetAZ crypto token. This token is part of the
|
|
broader AssetAZ platform and enables micropayments in connection with software distribution.</p>
|
|
<p>By using a dedicated token, a decentralized and transparent settlement mechanism is achieved, while also
|
|
creating a natural connection to AssetAZ, where the entire economic infrastructure is anchored.</p>
|
|
<p>It is important to note that this integration does not limit the use of Nenjim in regular, non-commercial
|
|
contexts, but as soon as you wish to publish and distribute software for commercial purposes—and thus also
|
|
participate in registration and transaction logic—it requires the use of AssetAZ and its token.</p>
|
|
<p>In this way, a sustainable ecosystem is created where it is free to use and experiment, but there is a small
|
|
cost for commercial activity.</p>
|
|
|
|
<div class="footer">
|
|
<p>Translated and rendered from Nenjim.md</p>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html>
|