-
Notifications
You must be signed in to change notification settings - Fork 422
fossology gold the master database schema
fossology-gold is accessible through fossology.org and is the fossology database from which the master schema, the one used in releases, is derived. So any database changes going into a released version need to be reflected here. Once the changes have been made to this database, it needs to be written to src/www/ui/core-schema.dat and checked in. This is because core-schema.dat is what is actually used in releases.
To change the master schema:
-
Test your changes on your development machine
-
Update fossology-gold. Typically this is done via phppgadmin. Don't export your development schema and check it in since it may contain unwanted changes!
-
Login to fossology.org (with ssh). You need a new account on the server that is in group fossy. Login is only possible with ssh-keys.
-
Export the gold schema:
-
schema-export -c /etc/fossology -f core-schema.dat.new
-
-
Test the output file on a development machine:
-
/usr/local/lib/fossology/fossinit.php -c /etc/fossology -f core-schema.dat.new
- Copy core-schema.dat.new to core-schema.dat in your src/www/ui/ and check it in.
If you don't have a fossology.org account or don't know the phppgadmin url and db user/pass, contact another developer who does.
- Nomos
- Monk
- MonkBulk
- ReSo-(REUSE.Software)
- Reuse clearing with reuser
- ScanCode agent
- Copyright
- ECC
- Package Agent
- Maintenance Agent
- Mimetype Agent
- Buckets
- Spasht Agent
- Email notification configuration
- Migration to UTF 8 DB
- External authentication configuration
- OpenID Connect authentication configuration
- Access Control