Continuing a discussion from the private@ thread that doesn't need to be private.
I find that working on web pages requires tons of minor tweaks and experimentation with styles and things, which will take way more time if I need to commit and push it all. Additionally, I'd rather not flood the commits mailing list with all of this unnecessary noise when I should be able to do my debugging locally. Not to mention that I'll need to figure out things like Pelican's way of collecting blog posts to display in chronological order (including generating RSS feeds automatically) — which I think is safe to predict won't work on my first few tries. To be clear, if I can't test locally, I'm a strong -1 on using Pelican. If Pelican isn't easy to set up and use locally, we can find a better static site generator. -- Josh Tynjala Bowler Hat LLC <https://bowlerhat.dev> Context: Andrew Wetmore wrote: Why do you need to build it? It builds automatically when you update content. Of course building locally helps avoid collisions with multiple contributors, and makes it easy to analyze for errors. I will be trying to figure out what's up, and to adjust both the docs and the template itself accordingly. Josh Tynjala wrote: I tried building the new royale-pelican-website repo, but still no luck. First, I tried following the "local build instructions", but I got the same errors as before. So I tried Docker next (which, if you don't mind a micro-rant, really seems like overkill for something like this). This is what I get when I try to run the Docker instructions that Dave linked earlier in the thread. > docker run -it -p8000:8000 -v $PWD:/site pelican-asf TOOLS: /tmp/pelican-asf/bin Building web site with: ('/bin/bash', '-c', '(pelican content --settings ./ pelican.auto.py --o site-generated -r -l -b 0.0.0.0)') Traceback (most recent call last): File "/usr/local/bin/pelican", line 5, in <module> from pelican.__main__ import main File "/usr/local/lib/python3.9/site-packages/pelican/__init__.py", line 19, in <module> from pelican.generators import (ArticlesGenerator, # noqa: I100 File "/usr/local/lib/python3.9/site-packages/pelican/generators.py", line 14, in <module> from pelican.cache import FileStampDataCacher File "/usr/local/lib/python3.9/site-packages/pelican/cache.py", line 6, in <module> from pelican.utils import mkdir_p File "/usr/local/lib/python3.9/site-packages/pelican/utils.py", line 21, in <module> from jinja2 import Markup ImportError: cannot import name 'Markup' from 'jinja2' (/usr/local/lib/python3.9/site-packages/jinja2/__init__.py) Traceback (most recent call last): File "/tmp/pelican-asf/bin/buildsite.py", line 409, in <module> main() File "/tmp/pelican-asf/bin/buildsite.py", line 405, in main args.func(args) File "/tmp/pelican-asf/bin/buildsite.py", line 256, in build_dir subprocess.run(buildcmd, cwd=auto_dir, check=True, env=env) File "/usr/local/lib/python3.9/subprocess.py", line 528, in run raise CalledProcessError(retcode, process.args, subprocess.CalledProcessError: Command '('/bin/bash', '-c', '(pelican content --settings ./pelican.auto.py --o site-generated -r -l -b 0.0.0.0)')' returned non-zero exit status 1. The terminal process "/bin/zsh '-c', 'docker run -it -p8000:8000 -v $PWD:/site pelican-asf'" terminated with exit code: 1. On Thu, Jun 23, 2022 at 9:10 AM Josh Tynjala <joshtynj...@bowlerhat.dev> wrote: > This is a thread to discuss the conversion of the current site away from > the WordPress setup we've been using to Pelican, a static site generator > recommended by Infra. > > -- > Josh Tynjala > Bowler Hat LLC <https://bowlerhat.dev> >
