"Basi di dati" final exam assignment.
Deployed (automatically) at superunimia.favo02.dev.
In italian:
- Manuale utente (installation manual)
- Documentazione tecnica (technical documentation)
Commit convention
No branches, all on main.
Commit convention
Each commit message consists of a header, a body, and a footer.
<header>
<BLANK LINE>
<body>
<BLANK LINE>
<footer>
<project part>(<scope>): <short summary>
│ │ │
│ │ └─⫸ Summary in present tense. Not capitalized. No period at the end.
│ │
│ └─⫸ Commit Scope: segretario|docente|studente|tables|procedures|functions|triggers|dump|scripts|css
│
└─⫸ Commit project part: repo|docs|db|web
Must be one of the following:
- repo: changes to the repository (ci, readme, gitignore, ...)
- docs: changes to documentation
- db: database
- web: webapp
The scope is the part of the codebase where the changes happened and it can be one of the following:
- segretario: webapp segretario user pages
- docente: webapp docente user pages
- studente: webapp studente user pages
- tables: database tables
- procedures: database procedures
- functions: database functions
- triggers: database triggers
- dump: database dump
- scripts: webapp scripts
- css: webapp css
- If a commit changes multiple parts of the codebase then an
*sign can be used as the scope specifier.
-
Use imperative, present tense: “change” not “changed” nor “changes”.
-
Include motivation for the change and contrasts with previous behavior.
All breaking changes have to be mentioned in footer with the description of the change, justification and migration notes (e.g. BREAKING CHANGE: desc...).
- If a commit targets a specific issue, the issue_id must be specified in the footer e.g.
Closes #123, in case of multiple issuesCloses #123, #124, #125.
Issues: bugs report, feature ideas
Issues can be opened for everything that has to do with the program, from asking questions to requesting new fetures or bug-fixes.
Issues should describe and include each of the following components:
- A
prioritylabelpriority: 0← Highestpriority: 1priority: 2priority: 3priority: 4← Lowest
- A
typelabelfeature: new feature to be implementedbug: bug to be fixedidea: an idea for a future update (not strictly required as a feature)
Versioning and deploying
No versioning (fuck vanilla PHP).
Every time a new version is bumped, the serve workflow will be triggered, generating a new Docker image for the application and serving it at superunimia.favo02.dev.