A common problem with complicated web apps built on top of TiddlySpace
is that it is hard to do live development on a test or dev instance.
While the desired experience is to be able to edit tiddlers on the file
system and see those changes in the instance instantly, the current
habit is to make the changes, update the package, update the instance
then see the changes.
This store aims to fix that by providing a wrapper store that on
tiddler_get first looks in a configured dir for an appropriate file
to satisfy the request.
Configuration is as follows:
config = {
'server_store': ['tiddlywebplugins.devstore2', {'devstore_root':
'./src'}],
'wrapped_devstore': ['text', {'store_root': 'store'}],
'log_level': 'DEBUG',
}
Where devstore_root is either an absolute path or relative to whatever
the PWD is in the process using the config.
devstore uses tiddlywebplugins.twimport's url_to_tiddler and thus will
read files ending in .tid as a tiddler, .js as a javascript file or treat
other extensions as binary or pseuod-binary tiddlers.
Metadata
Release files for tiddlywebplugins.devstore2 0.5.1
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 |
|---|---|---|---|---|
| tiddlywebplugins.devstore2-0.5.1.tar.gz | 5.5 kB | Without provenance | Details for tiddlywebplugins.devstore2-0.5.1.tar.gz |
Release files / tiddlywebplugins.devstore2-0.5.1.tar.gz
| Download URL | tiddlywebplugins.devstore2-0.5.1.tar.gz |
|---|---|
| Size | 5.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1363a01c2934636569dd8700efcaf099d871b25a29fa6290bc271faa2cf67bcd
|
|
BLAKE2b-256 checksum How to use checksums |
d6701a778ee584816a26a2fe2371b960fa3d3f3b8c719f42842ba11badf0bfd4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for tiddlywebplugins.devstore2 0.5.1
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.