Trinventum

Contents:

• Description
• Screenshots
• Download
• Installing the software
• Compatibility
• Reporting issues
• My projects on SourceForge
• My other software
• Contact information
• Page information

Description

Trinventum (Transaction and Inventory Unified Manager) is a software that helps manage an e-commerce business.

Trinventum allows to:

• register and modify products for sale (description, price, parameters, photo),
• add and modify buyers,
• add and modify sellers,
• add, modify and delete transactions.

What Trinventum is NOT:

• a webshop,
• software for ordering products,
• software for shipping products,
• a teller or cash register software,
• a finance manager (you can use GnuCash for that),
• an electronic payment system.

Trinventum is meant to be a place where you keep records of what products you have, in what quantities, in what statuses, who is buying and selling them and the transactions between the sellers and buyers.

Documentation is also available on the Trinventum wiki.

Screenshots of Trinventum

Screenshots are available on the SourceForge project page.

Download Trinventum

Current version is 1.0.



Download this at SourceForge.

Trinventum release file feed

Installing the software

Initial steps - most are one-time

1. A supported database (currently: PostgreSQL) must be running.
   On a Linux system, you would do one of:
   • login to the system as the database user postgres (you can do su - postgres as root to login to that account on Linux) and run:

     	pg_ctl start

   • login as root and run:

     	systemctl start postgresqlXX (XX being the version)

   • login as root and run:

     	service postgresql start

2. A web (HTTP) server with PHP support (like the Apache HTTP Server with mod_php installed) must be running.
   On a Linux system, you would do one of (as root):

   	systemctl start httpd-prefork

   	service httpd start

3. A database user must be created within the database server.
   On PostgreSQL, you would login to the system as the database user postgres and run:

   	createuser -P trinventum

   It's advised for the user to be the owner of the database that will be created.
   It's easiest to create a user with the same name as the system user name and create the database as the system user.
   You can create other database users later, and give them full or less privileges so that those users can execute all the activities or just the ones they have access to.
   
   
4. A logical database must be created within the database server.
   On PostgreSQL, you would login to the system as the database user postgres and run:

   	createdb -O trinventum trinventum

   (for the specified user to be the database owner)
   
   
5. A procedural language suitable for the database must be installed in the logical database.
   On PostgreSQL versions earlier than 9.0, you would login to the system as the database user postgres and run:

   	createlang plpgsql trinventum

   (don't worry if it says that the language already exists).
   Later PostgreSQL have the language already built-in by default.
   
   
6. Database access rules must be created within the database server unless you wish to leave the default rules.
   On PostgreSQL, you would do (as the database user postgres or root):

   	cp /var/lib/pgsql/data/pg_hba.conf /var/lib/pgsql/data/pg_hba.conf-backup
   	echo local trinventum trinventum scram-sha-256 >> /var/lib/pgsql/data/pg_hba.conf
   	echo host all all 127.0.0.1/32 scram-sha-256 >> /var/lib/pgsql/data/pg_hba.conf

   (Note the double ">>" - it's CRUCIAL to use double ">>", a single ">" would OVERWRITE the target file).
   On older PostgreSQL versions replace scram-sha-256 with md5.
   If you'll need to access the database from another computer:
   • a line similar to the host all all 127.0.0.1/32 scram-sha-256 should be added to pg_hba.conf, containing the correct IP address
   • firewall rules may need to be adjusted
   • the /etc/hosts.allow file (tcpwrappers) may need to be adjusted
   
   
7. After changing the access rules for the database server, restart it.
   On Linux with PostgreSQL, you would do one of:
   • login to the system as the database user postgres and run:

     	pg_ctl reload

   • login as root and run:

     	systemctl restart postgresqlXX (XX being the version)

   • login as root and run:

     	service postgresql restart

Installation - web application (for manual installation)

1. Copy the contents of the webapp directory (including hidden files) to a chosen location reachable by the web server and adjust the access modes accordingly so that the web server can actually run the files.

   Alternatively, if you have the make program and some common Linux utilities, you can run make install, passing the prefix of the target directory. Trinventum will be installed in $(PREFIX)/trinventum. Examples:

   	make install PREFIX=/srv/www/html SERVERCONF=/etc/httpd/conf/webapps.d
   	make install PREFIX=/var/www/html SERVERCONF=/etc/httpd/conf.d
   	make install PREFIX=$HOME/public_html SERVERCONF=$HOME/tmp

   The SERVERCONF parameter specifies where to put the global web server configuration file. Can be ignored and set to any directory for local installations.

   To install the documentation, you can add a chosen directory as the DOCDIR parameter to make install. Documentation will be installed in $(DOCDIR)/trinventum. Examples:

   	make install PREFIX=/srv/www/html SERVERCONF=/etc/httpd/conf/webapps.d DOCDIR=/usr/share/doc
   	make install PREFIX=/var/www/html DOCDIR=/usr/share/doc
   	make install PREFIX=$HOME/public_html DOCDIR=$HOME/tools/doc

2. The necessary database structures will be created by the application itself upon the first successful login of a user with full access to the database schema (like the schema owner trinventum created earlier).
   There is NO NEED to run any SQL scripts manually.

Installation - web application (for Docker installation)

To install Trinventum as a Docker container for testing, execute one of (as root):

	docker/docker.sh
	docker-compose -p trinventum -f docker/docker-compose.yaml up -d

in the Trinventum source code top directory (not the docker subdirectory).

WARNING: The default configuration has no permanent storage for the database. In order to have a persistent, working setup, you must add permanent storage to the configuration files.

WARNING: The default docker-compose.yaml file has hardcoded simple passwords. If you wish to use this file and have a secure setup, you must change those passwords in the file.

Optional - create roles and other users

Apart from the main database user (the database owner), you can have users with various privileges using the application:

• product management,
• seller management,
• buyer management,
• transaction management,
• any mix of the above.

To create the base roles, run the scripts/create_roles.pgsql file on the database as the database administration user (postgres):

	psql -U postgres -d trinventum -f scripts/create_roles.pgsql

Then, you can use the shell command createuser to create new users - login to the system as the database user postgres and run:

	createuser -P trin_mgr
	createuser -P trin_sell
	createuser -P trin_buy
	createuser -P trin_tx

and grant the selected role(s), found in the scripts/create_roles.pgsql file, to the new user:

	psql -U postgres -d trinventum -c 'grant trinventum_product_manager to trin_mgr'
	psql -U postgres -d trinventum -c 'grant trinventum_seller_manager to trin_sell'
	psql -U postgres -d trinventum -c 'grant trinventum_buyer_manager to trin_buy'
	psql -U postgres -d trinventum -c 'grant trinventum_transaction_manager to trin_tx'

Then, you can log in as the chosen user and have access to just the required functionalities.

Compatibility

Various versions of Trinventum have successfully been used with the following components in the following versions:

• PostgreSQL:
  • 8.x (checked: 8.4)
  • 9.x (checked: 9.0, 9.6.13)
  • 11.x (checked: 11.18)
  • 12.x (checked: 12.13)
  • 13.x (checked: 13.9)
  • 14.x (checked: 14.1)
  • 15.x (checked: 15.1)
  • 16.x (checked: 16.0)
• Apache HTTP Server:
  • 2.2.x (checked: 2.2.22)
  • 2.4.x (checked: 2.4.46, 2.4.52 and 2.4.54)
• PHP:
  • 5.x (checked: 5.3.20)
  • 8.0.x (checked: 8.0.2)
  • 8.1.x (checked: 8.1.3)
  • 8.2.x (checked: 8.2.1)

Other versions may also work.

Reporting issues

Any defects or issues can be reported by e-mail or in the SourceForge project defect manager (in English).

Any improvement suggestions can be reported by e-mail or in the SourceForge project ticket manager (in English).

To report usage problems, include:

1. the PostgreSQL version you're using, e.g. PostgreSQL 14.1,
2. the name and version of the web server you're using, e.g. Apache HTTP Server 2.4.52,
3. the PHP version you're using, e.g. PHP 8.1.3,
4. a description of the problem that the software causes,
5. any error messages that are displayed,
6. any other information that you think could lead to solving the problem.

Help in victory, play a game, send regards, or at least stop using some products

My projects on SourceForge

• WipeFreeSpace - a program for cleaning of free space on filesystems
• LibSecRm - a security wrapper library for C library functions which insecurely delete data
• Trinventum - software that helps manage an e-business
• Meqaris - meeting room and equipment booking system using e-mail invitations
• JYMAG - a program for serial-based (AT-based) mobile phones (like Sagem) and a serial port terminal
• IMYplay - a program for playing iMelody ringtones (IMY files) and an IMY-to-MIDI converter
• LibHideIP - a security wrapper library for C library functions which could lead to revealing your local IP address
• LibNetBlock - a security wrapper library that ensures that no program under its control can access the network
• FMSec - a set of extensions to file managers that enable some security-related operations to be easily performed. The operations include:
  • Secure removal of files using shred,
  • Secure removal of directories,
  • Mounting block devices and regular files using VeraCrypt,
  • Unmounting directories using VeraCrypt,
  • Wiping block devices (without removing them) using shred (the filesystem itself is destroyed too)
  • Wiping free space on filesystems on block devices or inside regular files using WipeFreeSpace,
  • Encrypting and decrypting files using OpenSSL,
  • running programs with LibSecRm preloaded,
  • running programs with LibHideIP preloaded,
  • running programs with LibNetBlock preloaded.
  FMSec consists of projects formerly known as KonqSec/Konq4Sec/Konq5Sec.
• Project Asmosis - a set of tools for assembly language programmers:
  • the Asm::X86 Perl module,
  • AsmDoc - a HTML documentation generator for assembly language,
  • assembly source code converters between NASM, fasm and GNU as,
  • C header to assembly header converters (h2fasm, h2gas, h2nasm),
  • Makefile generator for fasm (make4fasm),
  • Linux 2.6 kernel module helpers for fasm and NASM (symvers-nasm, symvers-fasm),
  • Asm4Doxy - Assembly converter for Doxygen,
  • util-macros.* - some utility macros for fasm and NASM,
  • Autoconf macros that check for existence and command-line options of the various assemblers (ax_prog_nasm.m4, ax_prog_nasm_opt.m4, ax_prog_fasm.m4, ax_prog_fasm_opt.m4, ax_prog_yasm.m4, ax_prog_yasm_opt.m4, ax_prog_tasm.m4, ax_prog_tasm_opt.m4, ax_prog_masm.m4, ax_prog_masm_opt.m4, ax_prog_hla.m4, ax_prog_hla_opt.m4),
  • OS parts - sample pieces of code that may be useful for starting developing a simple operating system.
• KeyParaStocX - is an extension for LibreOffice, Apache OpenOffice and the old OpenOffice.org that searches for keywords in a text, changes their style and builds a Table of Contents for them (formerly: "PozeraczUstaw").
• Fronsetia - a web application that allows testing webservices (formerly: SOAPServiceTester).

The always-up-to-date list of my SourceForge projects is on my profile page on SourceForge.

My other software

• primary site - rudy.mif.pg.gda.pl/~bogdro/soft - down
• first backup site - bogdro.ciki.me/soft - down
• second backup site - bogdro.fulba.com/soft - down
• third backup site (also available over HTTPS)
• fourth backup site (also available over HTTPS)

1. Certificate and key generators
2. E-mail address verifiers
3. LastMod - a script that inserts or updates a META element with the Last-Modified HTTP header
4. Atom2Rss - a script that converts an Atom (RFC 4287) channel XML file to an RSS 2.0 XML file
5. List2Atom - a script that generates an Atom (RFC 4287) channel XML file from a list of files
6. InSyTrack - telemetry software to track program flow (calls) across libraries, threads, programming languages or even different systems on different machines

• primary site with assembly tools - rudy.mif.pg.gda.pl/~bogdro/inne - down
• first backup site with assembly tools - bogdro.ciki.me/inne - down
• second backup site with assembly tools - bogdro.fulba.com/inne - down
• third backup site with assembly tools (also available over HTTPS)
• fourth backup site with assembly tools (also available over HTTPS)

1. Kate/KWrite syntax highlighting for NASM/fasm

Contact information

Contact me: bogdro AT users . sourceforge . net (English accepted, just say '[SOFT]' in the title).

The certificate of the timestamping server which confirms the signature time, can be found on freeTSA.org.

Page information

This page is hosted at SourceForge.net.
This page is written using valid HTML 4.01 , , for all browsers:

This page uses a valid CSS

This page has a content security policy.

This page doesn't use GIF images and doesn't use JPG images.

This page is pure HTML and CSS.

The project icon was created using Inkscape™.

Legal information

LINUX® is a registered trademark of Linus Torvalds.

Postgres® and PostgreSQL® and the Elephant Logo (Slonik) are all registered trademarks of the PostgreSQL Community Association of Canada.

Apache HTTP Server, Apache, and the Apache feather logo are trademarks of The Apache Software Foundation.

All other trademarks, logos and names on this page and all subpages are properties of their respective owners and are given here only as an example.