| Name | bisos.bpo JSON |
| Version |
0.46
JSON |
| download |
| home_page | None |
| Summary | bisos.bpo: BISOS Portable Objects |
| upload_time | 2025-02-18 03:21:30 |
| maintainer | Mohsen Banan |
| docs_url | None |
| author | Mohsen Banan |
| requires_python | None |
| license | AGPL |
| keywords |
|
| VCS |
|
| bugtrack_url |
|
| requirements |
No requirements were recorded.
|
| Travis-CI |
No Travis.
|
| coveralls test coverage |
No coveralls.
|
=================================
bisos.bpo: BISOS Portable Objects
=================================
.. contents::
:depth: 3
..
Overview
========
\*bisos.bpo (**BISOS Portable Objects**) is a python package which
abstracts Git based portable objects.
bisos.bpo is part of PyCS-BISOS-Framework. BISOS is part of ByStar
*(By*)*.
The **Libre-Halaal ByStar Digital Ecosystem** (*By\* DE*) is an
interdisciplinary, and ethics-oriented non-proprietary digital ecosystem
which challenges the existing proprietary American digital ecosystem
while operating concurrently alongside it. On a global scale, By\*
provide Internet Application Services which preserve autonomy and
privacy of the individual. **BISOS**: (*By\* Internet Services Operating
System*) layered on top of Debian, is a unified and universal framework
for developing both internet services and software-service continuums
that use internet services. BISOS is a layer on top of Debian. **Blee**:
(*BISOS Libre-Halaal Emacs Environment*) is a layer on top of Emacs and
BISOS, which creates a comprehensive integrated usage and development
environment. Blee and BISOS are fully integrated. See the "**Nature of
Polyexistentials**" book for the bigger picture of how all of ByStar
fits together.
For bootstraping BISOS, Blee and ByStar; you can start at:
https://github.com/bxgenesis/start
.. _table-of-contents:
Table of Contents TOC
=====================
- `Overview <#overview>`__
- `BISOS Portable Objects (BPO) <#bisos-portable-objects-bpo>`__
- `Installation <#installation>`__
- `With pip <#with-pip>`__
- `With pipx <#with-pipx>`__
- `Usage <#usage>`__
- `Locally (system command-line) <#locally-system-command-line>`__
- `Remotely (as a service) <#remotely-as-a-service>`__
- `Support <#support>`__
- `Documentation <#documentation>`__
BISOS Portable Objects (BPO)
============================
[sec:BISOSPortableObjects(BPO)]
A fundamental abstraction of BISOS is the concept of BISOS Portable
Objects (BPO). BPOs are packages of information. There are some
similarities between BPOs as packages of information and software
packages such as deb-packages or rpm-packages.
Like software packages, BPOs are named uniquely and can depend on each
other and can be collectively installed and uninstalled. BPOs are used
for many things similar to how the files system is used for many things.
BPOs can be used to hold the complete configuration information of a
system. BPOs can be used to hold configuration information for software
packages. BPOs can be used to hold private user data. BPOs can be used
to hold collections of content and source code.
For its own operation, BISOS uses various BPO types. Other types of BPOs
can be created or generic BPO types (for example the Project type) can
be used.
Each BPO consists of a number of Git Repositories (hereafter called
"repos"). Each of the BPO's repos can be synchronized using generic Git
tools. With Blee/Emacs we use MaGit exclusively.
Scope of access and use of BPOs can be private, group, public or system
oriented.
BPOs can be private, residing entirely in the Inner Rims, and used for
private exclusive use of their owners. Private BPOs are used by their
owners for a variety of purposes. For example, one's address book
(rolodex) can be captured in a private BPO. This allows for
synchronization of the address book as a git based portable object
across different devices and across different environments.
BPOs can be used to facilitate collaboration among groups of autonomous
users. Group BPOs are only accessible to you, and people you explicitly
share access with. Group BPOs are functionally similar to GitHub private
repositories — but in a decentralized fashion instead of GitHub's
central model.
Public BPOs facilitate publication of content and public evolution of
that content through git. Public BPOs are functionally similar to GitHub
public repositories — but in a decentralized fashion instead of GitHub's
central model.
System BPOs are BISOS specific information that contain system related
information. System BPOs can be "materialized" and function as Virtual
Machines and Services and PALS (Possession Assertable Libre Services).
System BPOs can be used to capture System configurations and SBOMs
(Software Bill Of Material). System BPOs can be private or public.
BPOs are currently implemented as Gitlab accounts. Gitlab accounts are
Unix non-login shell accounts. BISOS's interactions with Gitlab is
exclusively through an API (Remote Operations). Each Gitlab account then
can contain repos subject to common access control mechanisms. Gitlab
accounts map to BPO-Identifiers (BPO-Id). Each BPO-id then maps to Unix
non-login shell accounts. The Unix account then becomes the base for
cloning of the repos in the corresponding Gitlab account.
BPOs go through different states and stages. A "Registered" BPO reserves
a particular name/number for that BPO. "Realization" of a BPO results in
creation of the git account that holds the repositories of that BPO and
its subsequent activation. "Activation" of the BPO results in creation
of a non-login account on the system and cloning of the repositories of
that BPO. Activated BPOs can then be kept in sync through Git. An
activated System BPO can then be "Materialized". Materialization of a
System BPO results in creation of BISOS entities.
Combinations of profiled deb-packages for internet application services
and their configurations in the form of BPOs can then create Libre
Services that are possession assertable, portable and transferable.
Installation
============
The sources for the bisos.facter pip package is maintained at:
https://github.com/bisos-pip/facter.
The bisos.facter pip package is available at PYPI as
https://pypi.org/project/bisos.facter
You can install bisos.facter with pip or pipx.
With pip
--------
If you need access to bisos.facter as a python module, you can install
it with pip:
.. code:: bash
pip install bisos.facter
With pipx
---------
If you only need access to bisos.facter on command-line, you can install
it with pipx:
.. code:: bash
pipx install bisos.facter
The following commands are made available:
- facter.cs
- roInv-facter.cs
- roPerf-facter.cs
These are all one file with 3 names. *roInv-facter.cs* and
*roPerf-facter.cs* are sym-links to *facter.cs*
Usage
=====
Locally (system command-line)
-----------------------------
``facter.cs`` does the equivalent of facter.
.. code:: bash
bin/facter.cs
Remotely (as a service)
-----------------------
You can also run
Performer
~~~~~~~~~
Invoke performer as:
.. code:: bash
bin/roPerf-facter.cs
Invoker
~~~~~~~
.. code:: bash
bin/roInv-facter.cs
Support
=======
| For support, criticism, comments and questions; please contact the
author/maintainer
| `Mohsen Banan <http://mohsen.1.banan.byname.net>`__ at:
http://mohsen.1.banan.byname.net/contact
Documentation
=============
Part of ByStar Digital Ecosystem http://www.by-star.net.
This module's primary documentation is in
http://www.by-star.net/PLPC/180047
Raw data
{
"_id": null,
"home_page": null,
"name": "bisos.bpo",
"maintainer": "Mohsen Banan",
"docs_url": null,
"requires_python": null,
"maintainer_email": "libre@mohsen.1.banan.byname.net",
"keywords": null,
"author": "Mohsen Banan",
"author_email": "libre@mohsen.1.banan.byname.net",
"download_url": "https://files.pythonhosted.org/packages/c4/ec/c0db8ac9e745fd8c08253e199bea05fcd9e279b5dc67642bfc7f97d72178/bisos_bpo-0.46.tar.gz",
"platform": null,
"description": "=================================\nbisos.bpo: BISOS Portable Objects\n=================================\n\n.. contents::\n :depth: 3\n..\n\nOverview\n========\n\n\\*bisos.bpo (**BISOS Portable Objects**) is a python package which\nabstracts Git based portable objects.\n\nbisos.bpo is part of PyCS-BISOS-Framework. BISOS is part of ByStar\n*(By*)*.\n\nThe **Libre-Halaal ByStar Digital Ecosystem** (*By\\* DE*) is an\ninterdisciplinary, and ethics-oriented non-proprietary digital ecosystem\nwhich challenges the existing proprietary American digital ecosystem\nwhile operating concurrently alongside it. On a global scale, By\\*\nprovide Internet Application Services which preserve autonomy and\nprivacy of the individual. **BISOS**: (*By\\* Internet Services Operating\nSystem*) layered on top of Debian, is a unified and universal framework\nfor developing both internet services and software-service continuums\nthat use internet services. BISOS is a layer on top of Debian. **Blee**:\n(*BISOS Libre-Halaal Emacs Environment*) is a layer on top of Emacs and\nBISOS, which creates a comprehensive integrated usage and development\nenvironment. Blee and BISOS are fully integrated. See the \"**Nature of\nPolyexistentials**\" book for the bigger picture of how all of ByStar\nfits together.\n\nFor bootstraping BISOS, Blee and ByStar; you can start at:\nhttps://github.com/bxgenesis/start\n\n.. _table-of-contents:\n\nTable of Contents TOC\n=====================\n\n- `Overview <#overview>`__\n- `BISOS Portable Objects (BPO) <#bisos-portable-objects-bpo>`__\n- `Installation <#installation>`__\n\n - `With pip <#with-pip>`__\n - `With pipx <#with-pipx>`__\n\n- `Usage <#usage>`__\n\n - `Locally (system command-line) <#locally-system-command-line>`__\n - `Remotely (as a service) <#remotely-as-a-service>`__\n\n- `Support <#support>`__\n- `Documentation <#documentation>`__\n\nBISOS Portable Objects (BPO)\n============================\n\n\u00a0[sec:BISOSPortableObjects(BPO)]\n\nA fundamental abstraction of BISOS is the concept of BISOS Portable\nObjects (BPO). BPOs are packages of information. There are some\nsimilarities between BPOs as packages of information and software\npackages such as deb-packages or rpm-packages.\n\nLike software packages, BPOs are named uniquely and can depend on each\nother and can be collectively installed and uninstalled. BPOs are used\nfor many things similar to how the files system is used for many things.\nBPOs can be used to hold the complete configuration information of a\nsystem. BPOs can be used to hold configuration information for software\npackages. BPOs can be used to hold private user data. BPOs can be used\nto hold collections of content and source code.\n\nFor its own operation, BISOS uses various BPO types. Other types of BPOs\ncan be created or generic BPO types (for example the Project type) can\nbe used.\n\nEach BPO consists of a number of Git Repositories (hereafter called\n\"repos\"). Each of the BPO's repos can be synchronized using generic Git\ntools. With Blee/Emacs we use MaGit exclusively.\n\nScope of access and use of BPOs can be private, group, public or system\noriented.\n\nBPOs can be private, residing entirely in the Inner Rims, and used for\nprivate exclusive use of their owners. Private BPOs are used by their\nowners for a variety of purposes. For example, one's address book\n(rolodex) can be captured in a private BPO. This allows for\nsynchronization of the address book as a git based portable object\nacross different devices and across different environments.\n\nBPOs can be used to facilitate collaboration among groups of autonomous\nusers. Group BPOs are only accessible to you, and people you explicitly\nshare access with. Group BPOs are functionally similar to GitHub private\nrepositories \u2014 but in a decentralized fashion instead of GitHub's\ncentral model.\n\nPublic BPOs facilitate publication of content and public evolution of\nthat content through git. Public BPOs are functionally similar to GitHub\npublic repositories \u2014 but in a decentralized fashion instead of GitHub's\ncentral model.\n\nSystem BPOs are BISOS specific information that contain system related\ninformation. System BPOs can be \"materialized\" and function as Virtual\nMachines and Services and PALS (Possession Assertable Libre Services).\nSystem BPOs can be used to capture System configurations and SBOMs\n(Software Bill Of Material). System BPOs can be private or public.\n\nBPOs are currently implemented as Gitlab accounts. Gitlab accounts are\nUnix non-login shell accounts. BISOS's interactions with Gitlab is\nexclusively through an API (Remote Operations). Each Gitlab account then\ncan contain repos subject to common access control mechanisms. Gitlab\naccounts map to BPO-Identifiers (BPO-Id). Each BPO-id then maps to Unix\nnon-login shell accounts. The Unix account then becomes the base for\ncloning of the repos in the corresponding Gitlab account.\n\nBPOs go through different states and stages. A \"Registered\" BPO reserves\na particular name/number for that BPO. \"Realization\" of a BPO results in\ncreation of the git account that holds the repositories of that BPO and\nits subsequent activation. \"Activation\" of the BPO results in creation\nof a non-login account on the system and cloning of the repositories of\nthat BPO. Activated BPOs can then be kept in sync through Git. An\nactivated System BPO can then be \"Materialized\". Materialization of a\nSystem BPO results in creation of BISOS entities.\n\nCombinations of profiled deb-packages for internet application services\nand their configurations in the form of BPOs can then create Libre\nServices that are possession assertable, portable and transferable.\n\nInstallation\n============\n\nThe sources for the bisos.facter pip package is maintained at:\nhttps://github.com/bisos-pip/facter.\n\nThe bisos.facter pip package is available at PYPI as\nhttps://pypi.org/project/bisos.facter\n\nYou can install bisos.facter with pip or pipx.\n\nWith pip\n--------\n\nIf you need access to bisos.facter as a python module, you can install\nit with pip:\n\n.. code:: bash\n\n pip install bisos.facter\n\nWith pipx\n---------\n\nIf you only need access to bisos.facter on command-line, you can install\nit with pipx:\n\n.. code:: bash\n\n pipx install bisos.facter\n\nThe following commands are made available:\n\n- facter.cs\n- roInv-facter.cs\n- roPerf-facter.cs\n\nThese are all one file with 3 names. *roInv-facter.cs* and\n*roPerf-facter.cs* are sym-links to *facter.cs*\n\nUsage\n=====\n\nLocally (system command-line)\n-----------------------------\n\n``facter.cs`` does the equivalent of facter.\n\n.. code:: bash\n\n bin/facter.cs\n\nRemotely (as a service)\n-----------------------\n\nYou can also run\n\nPerformer\n~~~~~~~~~\n\nInvoke performer as:\n\n.. code:: bash\n\n bin/roPerf-facter.cs\n\nInvoker\n~~~~~~~\n\n.. code:: bash\n\n bin/roInv-facter.cs\n\nSupport\n=======\n\n| For support, criticism, comments and questions; please contact the\n author/maintainer\n| `Mohsen Banan <http://mohsen.1.banan.byname.net>`__ at:\n http://mohsen.1.banan.byname.net/contact\n\nDocumentation\n=============\n\nPart of ByStar Digital Ecosystem http://www.by-star.net.\n\nThis module's primary documentation is in\nhttp://www.by-star.net/PLPC/180047\n",
"bugtrack_url": null,
"license": "AGPL",
"summary": "bisos.bpo: BISOS Portable Objects",
"version": "0.46",
"project_urls": null,
"split_keywords": [],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "c4ecc0db8ac9e745fd8c08253e199bea05fcd9e279b5dc67642bfc7f97d72178",
"md5": "28db33661255dd56ac58660e5b0bb0fb",
"sha256": "094dfc6e82578c618c633f4d80ab38445e6d6e92454748fa34399ba1a6d5bd63"
},
"downloads": -1,
"filename": "bisos_bpo-0.46.tar.gz",
"has_sig": false,
"md5_digest": "28db33661255dd56ac58660e5b0bb0fb",
"packagetype": "sdist",
"python_version": "source",
"requires_python": null,
"size": 42602,
"upload_time": "2025-02-18T03:21:30",
"upload_time_iso_8601": "2025-02-18T03:21:30.971505Z",
"url": "https://files.pythonhosted.org/packages/c4/ec/c0db8ac9e745fd8c08253e199bea05fcd9e279b5dc67642bfc7f97d72178/bisos_bpo-0.46.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2025-02-18 03:21:30",
"github": false,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"lcname": "bisos.bpo"
}
