forked from getpelican/pelican
-
Notifications
You must be signed in to change notification settings - Fork 0
Setup Development Environment
Egbert edited this page Jul 1, 2024
·
1 revision
In a dual-console development, one terminal is always doing make serve
and is minimized.
Other console is for your rapid prototype; your edit/make-html/edit/make-html, you then view your handiwork using a web browser using a Refresh button, Ctrl-F5 (Firefox) for cache-busting refresh of your targeted page view.
In the three-console development, the consoles are used for:
-
make serve
, like always; no need to restart them -
vi my_plugin.py
always, never exited, occasionally saving -
auto-execute-pelican.sh
, my very own personal script
This auto-execute-pelican.sh
script will always fire a Pelican session after your editor saves the file, (it is never too soon to execute Pelican, fire away!)
#!/bin/sh
while inotifywait -mre create,delete,modify /home;do
./penguin -v -v -v -v -d
done
TIP: Your Firefox web browser could be automatically set to refresh the same page in the same tab using this 'Auto-Refresh' Add-On.