diff options
| -rw-r--r-- | .gitignore | 1 | ||||
| -rw-r--r-- | python-publ.spec | 326 | ||||
| -rw-r--r-- | sources | 1 |
3 files changed, 328 insertions, 0 deletions
@@ -0,0 +1 @@ +/publ-0.7.22.tar.gz diff --git a/python-publ.spec b/python-publ.spec new file mode 100644 index 0000000..399a8d8 --- /dev/null +++ b/python-publ.spec @@ -0,0 +1,326 @@ +%global _empty_manifest_terminate_build 0 +Name: python-publ +Version: 0.7.22 +Release: 1 +Summary: A flexible web-based publishing framework +License: MIT +URL: https://publ.plaidweb.site/ +Source0: https://mirrors.nju.edu.cn/pypi/web/packages/b3/06/4838bdef8bdd202a8c9f92139bfd1607a6fb3d78f04af354b28cab264358/publ-0.7.22.tar.gz +BuildArch: noarch + +Requires: python3-authl +Requires: python3-misaka +Requires: python3-arrow +Requires: python3-atomicwrites +Requires: python3-awesome-slugify +Requires: python3-Flask +Requires: python3-Flask-Caching +Requires: python3-pony +Requires: python3-Pygments +Requires: python3-watchdog +Requires: python3-Whoosh +Requires: python3-Pillow +Requires: python3-pillow +Requires: python3-flask + +%description +# Publ + +A personal publishing platform. Like a static publishing system, only dynamic. + +## Motivation + +I make a lot of different things — comics, music, art, code, games — and none of +the existing content management systems I found quite satisfied my use cases. +Either they don't allow enough flexibility in the sorts of content that they can +provide, or the complexity in managing the content makes it more complicated than +simply hand-authoring a site. + +I wanted to bring the best of the classic static web to a more dynamic +publishing system; scheduled posts, private posts, category-based templates, and +built-in support for image renditions (including thumbnails, high-DPI support, +and image galleries). And I want to do it all using simple Markdown files +organized in a sensible file hierarchy. + +## Basic tenets + +* Containerized web app that's deployable with little friction (hopefully) +* Do one thing (present heterogeneous content), do it well (hopefully) +* Use external tools for site content editing +* Be CDN-friendly +* High-DPI images and image sets as first-class citizens +* Interoperate with everything that's open for interoperation (especially [IndieWeb](http://indieweb.org)) + +## See it in action + +The main demonstration site is at https://beesbuzz.biz/ — it is of course a +work in progress! The documentation site for Publ itself (which is also a work in progress) lives at https://publ.plaidweb.site/ + +## Operating requirements + +I am designing this to work in any WSGI-capable environment with a supported +version of Python. This means that it will, for example, be deployable on any +shared hosting which has Passenger support (such as Dreamhost), as well as on +Heroku, Google AppEngine, S3, or any other simple containerized deployment +target. + +The file system is the ground truth for all site data, and while it does use a +database as a content index, the actual choice of database doesn't matter all +that much. A typical deployment will use SQLite, but MySQL, Postgres, Oracle, +and Cockroach are also supported. + +## Developing Publ + +In order to develop Publ itself, you'll need to install its dependencies; see +the [getting started +guide](http://publ.plaidweb.site/manual/328-Getting-started) for more +information. In particular, make sure you have compatible versions of +[Python](https://python.org/) and [Poetry](https://python-poetry.org/) +installed, and, if on Windows, you'll probably need to install the [Visual C++ +build tools](https://visualstudio.microsoft.com/downloads/). + +As far as developing Publ itself goes, cloning this repository and running +`./runTests.sh` (Linux/macOS/etc.) or `wintests.cmd` (Windows) should get you up +and running. The runtime manual test suite site lives in `tests/` (with the +actual site content in `content/`, `templates/` and `static/`). + +For developing CLI functionality, you'll have to override the `FLASK_APP` +environment variable to be `test_app.py`. + +## Additional resources + +The [Publ-site](https://github.com/PlaidWeb/Publ-site) repository stores all of +the templates, site content, and configuration for the [Publ +site](https://publ.plaidweb.site). + +The +[Publ-templates-beesbuzz.biz](https://github.com/PlaidWeb/Publ-templates-beesbuzz.biz) +repository provides a stripped-down sample site based on [my personal +homepage](https://beesbuzz.biz). + +## Authors + +In order of first contribution: + +* [fluffy](https://github.com/fluffy-critter) +* [karinassuni](https://github.com/karinassuni) + + +%package -n python3-publ +Summary: A flexible web-based publishing framework +Provides: python-publ +BuildRequires: python3-devel +BuildRequires: python3-setuptools +BuildRequires: python3-pip +%description -n python3-publ +# Publ + +A personal publishing platform. Like a static publishing system, only dynamic. + +## Motivation + +I make a lot of different things — comics, music, art, code, games — and none of +the existing content management systems I found quite satisfied my use cases. +Either they don't allow enough flexibility in the sorts of content that they can +provide, or the complexity in managing the content makes it more complicated than +simply hand-authoring a site. + +I wanted to bring the best of the classic static web to a more dynamic +publishing system; scheduled posts, private posts, category-based templates, and +built-in support for image renditions (including thumbnails, high-DPI support, +and image galleries). And I want to do it all using simple Markdown files +organized in a sensible file hierarchy. + +## Basic tenets + +* Containerized web app that's deployable with little friction (hopefully) +* Do one thing (present heterogeneous content), do it well (hopefully) +* Use external tools for site content editing +* Be CDN-friendly +* High-DPI images and image sets as first-class citizens +* Interoperate with everything that's open for interoperation (especially [IndieWeb](http://indieweb.org)) + +## See it in action + +The main demonstration site is at https://beesbuzz.biz/ — it is of course a +work in progress! The documentation site for Publ itself (which is also a work in progress) lives at https://publ.plaidweb.site/ + +## Operating requirements + +I am designing this to work in any WSGI-capable environment with a supported +version of Python. This means that it will, for example, be deployable on any +shared hosting which has Passenger support (such as Dreamhost), as well as on +Heroku, Google AppEngine, S3, or any other simple containerized deployment +target. + +The file system is the ground truth for all site data, and while it does use a +database as a content index, the actual choice of database doesn't matter all +that much. A typical deployment will use SQLite, but MySQL, Postgres, Oracle, +and Cockroach are also supported. + +## Developing Publ + +In order to develop Publ itself, you'll need to install its dependencies; see +the [getting started +guide](http://publ.plaidweb.site/manual/328-Getting-started) for more +information. In particular, make sure you have compatible versions of +[Python](https://python.org/) and [Poetry](https://python-poetry.org/) +installed, and, if on Windows, you'll probably need to install the [Visual C++ +build tools](https://visualstudio.microsoft.com/downloads/). + +As far as developing Publ itself goes, cloning this repository and running +`./runTests.sh` (Linux/macOS/etc.) or `wintests.cmd` (Windows) should get you up +and running. The runtime manual test suite site lives in `tests/` (with the +actual site content in `content/`, `templates/` and `static/`). + +For developing CLI functionality, you'll have to override the `FLASK_APP` +environment variable to be `test_app.py`. + +## Additional resources + +The [Publ-site](https://github.com/PlaidWeb/Publ-site) repository stores all of +the templates, site content, and configuration for the [Publ +site](https://publ.plaidweb.site). + +The +[Publ-templates-beesbuzz.biz](https://github.com/PlaidWeb/Publ-templates-beesbuzz.biz) +repository provides a stripped-down sample site based on [my personal +homepage](https://beesbuzz.biz). + +## Authors + +In order of first contribution: + +* [fluffy](https://github.com/fluffy-critter) +* [karinassuni](https://github.com/karinassuni) + + +%package help +Summary: Development documents and examples for publ +Provides: python3-publ-doc +%description help +# Publ + +A personal publishing platform. Like a static publishing system, only dynamic. + +## Motivation + +I make a lot of different things — comics, music, art, code, games — and none of +the existing content management systems I found quite satisfied my use cases. +Either they don't allow enough flexibility in the sorts of content that they can +provide, or the complexity in managing the content makes it more complicated than +simply hand-authoring a site. + +I wanted to bring the best of the classic static web to a more dynamic +publishing system; scheduled posts, private posts, category-based templates, and +built-in support for image renditions (including thumbnails, high-DPI support, +and image galleries). And I want to do it all using simple Markdown files +organized in a sensible file hierarchy. + +## Basic tenets + +* Containerized web app that's deployable with little friction (hopefully) +* Do one thing (present heterogeneous content), do it well (hopefully) +* Use external tools for site content editing +* Be CDN-friendly +* High-DPI images and image sets as first-class citizens +* Interoperate with everything that's open for interoperation (especially [IndieWeb](http://indieweb.org)) + +## See it in action + +The main demonstration site is at https://beesbuzz.biz/ — it is of course a +work in progress! The documentation site for Publ itself (which is also a work in progress) lives at https://publ.plaidweb.site/ + +## Operating requirements + +I am designing this to work in any WSGI-capable environment with a supported +version of Python. This means that it will, for example, be deployable on any +shared hosting which has Passenger support (such as Dreamhost), as well as on +Heroku, Google AppEngine, S3, or any other simple containerized deployment +target. + +The file system is the ground truth for all site data, and while it does use a +database as a content index, the actual choice of database doesn't matter all +that much. A typical deployment will use SQLite, but MySQL, Postgres, Oracle, +and Cockroach are also supported. + +## Developing Publ + +In order to develop Publ itself, you'll need to install its dependencies; see +the [getting started +guide](http://publ.plaidweb.site/manual/328-Getting-started) for more +information. In particular, make sure you have compatible versions of +[Python](https://python.org/) and [Poetry](https://python-poetry.org/) +installed, and, if on Windows, you'll probably need to install the [Visual C++ +build tools](https://visualstudio.microsoft.com/downloads/). + +As far as developing Publ itself goes, cloning this repository and running +`./runTests.sh` (Linux/macOS/etc.) or `wintests.cmd` (Windows) should get you up +and running. The runtime manual test suite site lives in `tests/` (with the +actual site content in `content/`, `templates/` and `static/`). + +For developing CLI functionality, you'll have to override the `FLASK_APP` +environment variable to be `test_app.py`. + +## Additional resources + +The [Publ-site](https://github.com/PlaidWeb/Publ-site) repository stores all of +the templates, site content, and configuration for the [Publ +site](https://publ.plaidweb.site). + +The +[Publ-templates-beesbuzz.biz](https://github.com/PlaidWeb/Publ-templates-beesbuzz.biz) +repository provides a stripped-down sample site based on [my personal +homepage](https://beesbuzz.biz). + +## Authors + +In order of first contribution: + +* [fluffy](https://github.com/fluffy-critter) +* [karinassuni](https://github.com/karinassuni) + + +%prep +%autosetup -n publ-0.7.22 + +%build +%py3_build + +%install +%py3_install +install -d -m755 %{buildroot}/%{_pkgdocdir} +if [ -d doc ]; then cp -arf doc %{buildroot}/%{_pkgdocdir}; fi +if [ -d docs ]; then cp -arf docs %{buildroot}/%{_pkgdocdir}; fi +if [ -d example ]; then cp -arf example %{buildroot}/%{_pkgdocdir}; fi +if [ -d examples ]; then cp -arf examples %{buildroot}/%{_pkgdocdir}; fi +pushd %{buildroot} +if [ -d usr/lib ]; then + find usr/lib -type f -printf "/%h/%f\n" >> filelist.lst +fi +if [ -d usr/lib64 ]; then + find usr/lib64 -type f -printf "/%h/%f\n" >> filelist.lst +fi +if [ -d usr/bin ]; then + find usr/bin -type f -printf "/%h/%f\n" >> filelist.lst +fi +if [ -d usr/sbin ]; then + find usr/sbin -type f -printf "/%h/%f\n" >> filelist.lst +fi +touch doclist.lst +if [ -d usr/share/man ]; then + find usr/share/man -type f -printf "/%h/%f.gz\n" >> doclist.lst +fi +popd +mv %{buildroot}/filelist.lst . +mv %{buildroot}/doclist.lst . + +%files -n python3-publ -f filelist.lst +%dir %{python3_sitelib}/* + +%files help -f doclist.lst +%{_docdir}/* + +%changelog +* Fri May 05 2023 Python_Bot <Python_Bot@openeuler.org> - 0.7.22-1 +- Package Spec generated @@ -0,0 +1 @@ +15bcde01026355d999494af6085226f0 publ-0.7.22.tar.gz |