Contains fassembler projects for building components of an OpenCore stack.
Changes
0.5
Use pip for frontend project.
0.4
Add “frontend” templates directly into source distribution, rather than pulling them from a separate SVN repository.
0.3
The frontend project now looks for the num_extra_zopes setting in build.ini [general] section.
This setting is now used to determine the default value of opencore_remote_uri if that parameter is not set.
If num_extra_zopes is set, the default value of opencore_remote_uri will now be a space-separated list of URLs for all the Zope instances built (assumed to be on their default ports, e.g. 10001, 10011, 10021 etc)
0.2
Added support for Twirlip in the frontend project.
If Twirlip is used (which is the default), the frontend will host Twirlip at the path /notifications and will also filter the entire application with Transcluder, since the UI for Twirlip is transcluded into pages.
To disable Twirlip support, build the frontend project with the setting use_twirlip=0.
Also included in this release is an experimental zine project; this is incomplete and should not be used in production builds.
Metadata
Release files for opencore-fassembler_projects 0.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| opencore-fassembler_projects-0.5.tar.gz | 4.3 kB | Without provenance | Details for opencore-fassembler_projects-0.5.tar.gz |
Release files / opencore-fassembler_projects-0.5.tar.gz
| Download URL | opencore-fassembler_projects-0.5.tar.gz |
|---|---|
| Size | 4.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
92b5621b2266e5cfe5bfae22932b2a260f3ad2771a150f4a8b1d9119441a5140
|
|
BLAKE2b-256 checksum How to use checksums |
78ae0e74905f85b86ad2764aa478e3e298d40d2594b2159b183545ac17f05e13
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for opencore-fassembler_projects 0.5
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.