Dear Maintainer, lektor has an administration UI that allows users to edit pages using a CMS like interface. This is typically accessed by running 'lektor serve', then visiting http://127.0.0.1:5000/ and clicking on the edit button on the top right corner of the static page. Currently, lektor's Debian package does not build the administration interface present in the directory lektor/admin/. This results in 404 errors generated by visiting the administrator interface of lektor. Administration interface is usually built by running 'make build-js' in the root directory. This in-turn uses 'npm' and several node modules. Most of these node modules seem to be already packaged for Debian. Please consider building and packaging the administration UI for lektor as part of the lektor's Debian package. Lektor being used by the FreedomBox project and we are considering making it available for users as a FreedomBox app. Thank you for packaging lektor.
In version 3.1.3-1 of the debian package the administration UI for lektor seems to be part of the package, at least there are many files in lektor/admin/. But when I run 'lektor serve' and than point my brwoser to http://127.0.0.1:5000/ there appears only a never ending "Loading Interface ..." instead of the admin gui. Using a local version of lektor installed directly from the website all goes fine. The only error message I get in the terminal running the debian version is: "/usr/lib/python3/dist-packages/watchdog/utils/bricks.py:175: DeprecationWarning: Using or importing the ABCs from 'collections' instead of from 'collections.abc' is deprecated since Python 3.3,and in 3.9 it will stop working." Would be nice to have a working debian package ;-) Klaumi----------- Klaus-Michael Klingsporn mail: klaumikli@gmx.de web: www.klaumikli.de
As documented in the package description and NEWS, we're currently unable to ship the Lektor frontend interface due to missing javascript build dependencies to compile the frontend. The upcoming Lektor 3.4 branch appears to be simplifying the build process for the frontend, so I'm keeping this bug open so we revisit this next upstream release. Thanks,