> I hope to see more pods
What's preventing you from getting more pods?
> I hope to see more pods
What's preventing you from getting more pods?
package.json or requirements.txt or something similar.
404 page not found, what's the deal?
mkws websites is to bundle them as static binaries so you don't have to run any package manager on the server side either. So, if your website uses smu, distribute a statically compiled smu in your website's ./bin directory. The recommended way of doing this is to do a make install PREFIX=/path/to/mkws/website/root. Make sure the -static flag is set. That way you will also get the man pages installed in the ./share/man directory.
shellcheck your pp templates via pp -d docs.upphtml | shellcheck -s sh -.
awk script is a thing of beauty. 😁
mkws would handle 217 articles. 😀
Markdown?
mkws the site's name is mkws.sh.
> I hope to convert it over to something like mkws.sh
And what's preventing you?
meta file and maybe use my first paragraph as description suggestion?
https://www.bbc.com/news/world-asia-56245404
Wasn't aware this was a thing.
updated field with lmt https://mkws.sh/lts.html wherever it's a good idea to have. (sitemap, atom feed)
<h1>Blog</h1>
<h2>News and a collection of tips and tricks for <code>mkws</code></h2>
<ol id=i>
#!
find p -mindepth 1 | sort -r | while read -r f
do
test "${f##*.}" == "html" && continue;
t=$(echo "${f##*/}" | cut -c21-)
#!
<li>
<h2><a href=p/$(echo "$t" | pe).html>$t</a></h2>
<time>$(echo "${f##*/}" | cut -c1-10 )</time>
</li>
#!
done
#!
</ol>
I have yet to come up with a solution for the
description meta but I might formulate the first paragraph to be a good description, I'd rather not use any front matter.\n<h1>Blog</h1>\n<h2>News and a collection of tips and tricks for <code>mkws</code></h2>\n<ol id=i>\n#!\nfind p -mindepth 1 | sort -r | while read -r f\ndo\ntest "${f##*.}" == "html" && continue;\nt=$(echo "${f##*/}" | cut -c21-)\n#!\n<li>\n<h2><a href=p/$(echo "$t" | pe).html>$t</a></h2>\n<time>$(echo "${f##*/}" | cut -c1-10 )</time>\n</li>\n#!\ndone\n#!\n</ol>\ndescription meta but I might formulate the first paragraph to be a good description, I'd rather not use any front matter.
$ ls -1
2021-02-28 15:34:42 Welcome
2021-02-28 15:35:21 How to add a navigation menu
2021-02-28 15:35:39 How to add custom titles
\n$ ls -1\n2021-02-28 15:34:42 Welcome\n2021-02-28 15:35:21 How to add a navigation menu\n2021-02-28 15:35:39 How to add custom titles\npe.c https://clbin.com/X1GkA (percent encode) and pd.c https://clbin.com/8Ewrn (percent decode) https://tools.ietf.org/html/rfc3986#section-2.1. I'll have to publish them somewhere sometime.
~/src and ~/bin directories.
Markdown, @eldersnake wrote about that here https://www.thelinuxrain.org/articles/mkws-static-site-generation-with-the-shell and how to get a development server going and live reload.
> A container built from an OCI image might behave the same as an OS using the same underlying root file system they do not operate the same at all
Uhmm...
ulinux vm.
ulinux?
ulinux?
qemu more convenient.
docker run -i -t prologic/ulinux persistent?
> The initial-scale property controls the zoom level when the page is first loaded.
I'd rather not reset the initial zoom level? Do mobile browsers have weird initial zoom levels?
initial-scale? Tbh, I'd rather not reset the zoom.
\n<meta name=viewport content='width=device-width, initial-scale=1, maximum-scale=1'>\n\n<meta name=viewport content='width=device-width'>\n
<meta name=viewport content='width=device-width, initial-scale=1, maximum-scale=1'>
I'm not sure, but for me this works
<meta name=viewport content='width=device-width'>
Isn't this enough?
*$ is more appropriate?
> A tool for adding new lines to files, skipping duplicates
pp version:
#!/usr/local/bin/pp
#!
t="$*"
#!
<!DOCTYPE html>
<meta charset=utf-8>
<title>${t:=$(basename "$PWD")}</title>
<style>*{font-family:sans-serif}</style>
<h1>$t</h1>
#!
for img in ??.jpg
do
#!
<a href=$img style=cursor:zoom-in><img src=$(basename "$img" .jpg)-vorschau.jpg alt='$t'></a>
#!
done
#!
pp version:\n\n\n#!/usr/local/bin/pp\n#!\nt="$*"\n#!\n<!DOCTYPE html>\n<meta charset=utf-8 />\n<title>${t:=$(basename "$PWD")}</title>\n<style>*{font-family:sans-serif}</style>\n<h1>$t</h1>\n#!\nfor img in ??.jpg; do\n#!\n<a href=$img style=cursor:zoom-in><img src=$(basename "$img" .jpg)-vorschau.jpg alt='$t' /></a>\n#!\ndone\n#!\npp version:\n\n\n#!/usr/local/bin/pp\n#!\nt="$*"\n#!\n<!DOCTYPE html>\n<meta charset=utf-8>\n<title>${t:=$(basename "$PWD")}</title>\n<style>*{font-family:sans-serif}</style>\n<h1>$t</h1>\n#!\nfor img in ??.jpg\ndo\n#!\n<a href=$img style=cursor:zoom-in><img src=$(basename "$img" .jpg)-vorschau.jpg alt='$t'></a>\n#!\ndone\n#!\npp version:\n\n\n#!/usr/local/bin/pp\n#!\nt="$*"\n#!\n<!DOCTYPE html>\n<meta charset=utf-8>\n<title>${t:=$(basename "$PWD")}</title>\n<style>*{font-family:sans-serif}</style>\n<h1>$t</h1>\n#!\nfor img in ??.jpg; do\n#!\n<a href=$img style=cursor:zoom-in><img src=$(basename "$img" .jpg)-vorschau.jpg alt='$t'></a>\n#!\ndone\n#!\ndocker command to run ulinux?