Lektor Surge Publisher Plugin
Publishes your Lektor site to Surge.
Installation
Add lektor-surge to your project from command line:
lektor plugins add lektor-surge
See the Lektor documentation for more instructions on installing plugins.
Configuration
Configure Surge in your .lektorproject file:
[servers.surge]
target = surge:my-domain.com
To force all traffic to HTTPS, update your .lektorproject file:
[servers.surge]
target = surge+https:my-domain.com
For more information, see the Surge guide to HTTPS.
Deployment
Deploy your site with Lektor from the command line:
lektor deploy surge
Metadata
Release files for lektor-surge 0.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| lektor_surge-0.3-py3-none-any.whl | Python 3 | none | any | Details for lektor_surge-0.3-py3-none-any.whl |
Release files / lektor_surge-0.3-py3-none-any.whl
| Download URL | lektor_surge-0.3-py3-none-any.whl |
|---|---|
| Size | 2.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
07549794d580aaaf54a931939327acd31de2719dd8668be82475de743548563d
|
|
BLAKE2b-256 checksum How to use checksums |
bc5ea078cc5a9c7fa4e18f6fc6f9e1df891828427cfaf05d619be90935b2c576
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for lektor-surge 0.3
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.