User:)biyibiyibiyi(/Prototyping 04: Difference between revisions
No edit summary |
|||
(34 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
http://pzwiki.wdka.nl/mediadesign/Prototyping_2 | |||
==bootleg library session with Michael and Simon== | ==bootleg library session with Michael and Simon== | ||
pad! | pad! | ||
Line 12: | Line 13: | ||
====channel channel==== | ====channel channel==== | ||
http://channelchannel.site/ | http://channelchannel.site/ | ||
I am having lots of troubles maintaining the website. one problem that I encountered is, for example I want to post an article, and I need to insert the article in plain html and save the file. It became very troublesome for me to maintain texts. I want to use a proper cms to do it. | |||
Today I am trying out possibilities, however, I am running to several problems. | |||
* my server kept crashing. I don't know if it's a problem that's caused by port mapping. I have now 3 pis installed with my router, and I've mapped the two others' http and ssh ports accordingly. The main one (which ports were from default) never crashed, and the other two kept crashing. I couldn't ssh and couldn't connect on cyberduck. Not only I wasn't able to connect but the OS was corrupted, I have to install again the OS. | |||
* I couldn't install nginx or apache on the servers, after I flash a new system. The problem just occurred today. The error was some files could not be fetched from this archive http://raspbian.raspberrypi.org/raspbian/pool/main/n/nginx/ I was planning on trying out a cms named Kirby on the server, but I couldn't install the server so I couldn't proceed. | |||
*pay wall. Since I saw many sites are built with wordpress as cms, I wanted to try it too. But then I gave up after Wordpress asked for a fee to use the cms annually. Kirby is also not free. | |||
*Now I am going to try pelican according to this documentation - https://garyhall.org.uk/fast-blog-for-raspberry-pi.html . This person identified similar problems with me, that html took ages to write and need a easy to maintain manager. Lighttpd, if I am understanding correctly, is the web server, that's to substitute nginx and apache? Then I will try to first install it on the pi and see if it has similar error with nginx and apache. <and as I expected I also had similar error trying to install lighttpd of not fetching the right files. >if it has similar errors, I can try on my laptop, but I don't know how the server aspect works if I am trying out locally on my laptop. | |||
error: frequent broken pipe. SSH crashed my house, and in PZI it also crashed, after I tried to curl a file. | |||
[[File:Working normal diet pi.png|thumbnail]] | |||
[[File:Broken pipe diet pi.png|thumbnail]] | |||
I don't know if I try out these instructions it will be helpful for my ssh? | |||
https://homebrewserver.club/demystifying-ssh.html | |||
* I also would like to know, if it's possible to buy a server? on Varia's website they mentioned a server that various other self hosted devices are connected. I always found myself frustrated using the pi as server (crashing, slow, don't know how to manage things..) I don't know if that's a good idea. | |||
=====trying out pelican===== | |||
<source lang=text> | |||
├── Makefile | |||
├── __pycache__ | |||
│ └── pelicanconf.cpython-37.pyc | |||
├── content | |||
│ ├── article2.md | |||
│ ├── category | |||
│ │ ├── article1.rst | |||
│ │ └── displaytest.rst | |||
│ ├── hellohellohello.md | |||
│ ├── images | |||
│ │ └── kaixin.png | |||
│ ├── pages | |||
│ │ ├── about.md | |||
│ │ └── test.md | |||
│ └── pdfs | |||
├── output | |||
│ ├── archives.html | |||
│ ├── article3md.html | |||
│ ├── author | |||
│ │ └── biyi.html | |||
│ ├── authors.html | |||
│ ├── categories.html | |||
│ ├── category | |||
│ │ ├── category.html | |||
│ │ ├── misc.html | |||
│ │ └── review.html | |||
│ ├── images | |||
│ │ └── kaixin.png | |||
│ ├── index.html | |||
│ ├── my-first-review.html | |||
│ ├── pages | |||
│ │ ├── aboutmd.html | |||
│ │ └── testmd.html | |||
│ ├── tags.html | |||
│ ├── the-first-article.html | |||
│ ├── the-second-article.html | |||
│ ├── theme | |||
│ │ ├── css | |||
│ │ │ ├── fonts.css | |||
│ │ │ ├── main.css | |||
│ │ │ ├── pygment.css | |||
│ │ │ ├── reset.css | |||
│ │ │ ├── typogrify.css | |||
│ │ │ └── wide.css | |||
│ │ ├── fonts | |||
│ │ │ ├── Yanone_Kaffeesatz_400.eot | |||
│ │ │ ├── Yanone_Kaffeesatz_400.svg | |||
│ │ │ ├── Yanone_Kaffeesatz_400.ttf | |||
│ │ │ ├── Yanone_Kaffeesatz_400.woff | |||
│ │ │ ├── Yanone_Kaffeesatz_400.woff2 | |||
│ │ │ └── font.css | |||
│ │ └── images | |||
│ │ └── icons | |||
│ │ ├── aboutme.png | |||
│ │ ├── bitbucket.png | |||
│ │ ├── delicious.png | |||
│ │ ├── facebook.png | |||
│ │ ├── github.png | |||
│ │ ├── gitorious.png | |||
│ │ ├── gittip.png | |||
│ │ ├── google-groups.png | |||
│ │ ├── google-plus.png | |||
│ │ ├── hackernews.png | |||
│ │ ├── lastfm.png | |||
│ │ ├── linkedin.png | |||
│ │ ├── reddit.png | |||
│ │ ├── rss.png | |||
│ │ ├── slideshare.png | |||
│ │ ├── speakerdeck.png | |||
│ │ ├── stackoverflow.png | |||
│ │ ├── twitter.png | |||
│ │ ├── vimeo.png | |||
│ │ └── youtube.png | |||
│ ├── this-is-a-test.html | |||
│ └── try-to-see-if-this-shows.html | |||
├── pelicanconf.py | |||
├── publishconf.py | |||
└── tasks.py | |||
</source> | |||
[[File:Chronological order articles.png | 600px]] | |||
pelican differentiates pages and articles. pages are static, like about page. whereas articles are published under same categories under chronological order. | |||
=====possibility of familarizing how jinja works with pelican?===== | |||
about Jinja | |||
http://pzwiki.wdka.nl/mediadesign/Jinja | |||
===== about blogging culture ===== | |||
reading this sentence from pelican documentation I start to thinking of blogging culture, for me it was popular since 2000s, would be nice to examine the culture and labor of blogging? | |||
The questioned being asked in FAQ is - Is Pelican only suitable for blogs? | |||
No. Pelican can be easily configured to create and maintain any type of static site. | |||
====a4 publishing==== | ====a4 publishing==== | ||
still in speculation! a4 means ordinary. | still in speculation! a4 means ordinary. | ||
===work archive site=== | |||
====fancyindex==== | |||
trying the fancyindex module in nginx because saw it's employed in quite some sites. | |||
[[fancyindex]] working on this manual while tinkering. | |||
===troubles=== | ===troubles=== | ||
managing multiple website on one router and several raspberry pi | managing multiple website on one router and several raspberry pi | ||
look for help here: | |||
http://pzwiki.wdka.nl/mediadesign/Homebrewserver_infrastructour | |||
===relevancies=== | |||
===publishing in Dat=== | |||
dat://14e576a5cc61e7a0d6c43cd64cf292ec98c286920a0b4fff78e7058663901cd2/ | |||
== why are domain names not free == | |||
==load bunch of text (without formatting) to webpage== | |||
is php solution? | |||
==protocols== | |||
look into ipfs, an file transfer system comparable to http | |||
== | ==session 23_09== | ||
hackpact | |||
play with wiki, pelican, as publishing tools | |||
diy networks | |||
look into pervasive labor union | |||
===hackpact!=== | |||
[[My Hackpact entries here |http://pzwiki.wdka.nl/mediadesign/User:)biyibiyibiyi(/hackpact]] |
Latest revision as of 18:27, 23 September 2019
http://pzwiki.wdka.nl/mediadesign/Prototyping_2
bootleg library session with Michael and Simon
pad! https://pad.xpub.nl/p/09_10_19
project websites
in the process of publishing few project sites, as a ongoing archive and working framework.
the sites
contextual electronics
channel channel
I am having lots of troubles maintaining the website. one problem that I encountered is, for example I want to post an article, and I need to insert the article in plain html and save the file. It became very troublesome for me to maintain texts. I want to use a proper cms to do it.
Today I am trying out possibilities, however, I am running to several problems.
- my server kept crashing. I don't know if it's a problem that's caused by port mapping. I have now 3 pis installed with my router, and I've mapped the two others' http and ssh ports accordingly. The main one (which ports were from default) never crashed, and the other two kept crashing. I couldn't ssh and couldn't connect on cyberduck. Not only I wasn't able to connect but the OS was corrupted, I have to install again the OS.
- I couldn't install nginx or apache on the servers, after I flash a new system. The problem just occurred today. The error was some files could not be fetched from this archive http://raspbian.raspberrypi.org/raspbian/pool/main/n/nginx/ I was planning on trying out a cms named Kirby on the server, but I couldn't install the server so I couldn't proceed.
- pay wall. Since I saw many sites are built with wordpress as cms, I wanted to try it too. But then I gave up after Wordpress asked for a fee to use the cms annually. Kirby is also not free.
- Now I am going to try pelican according to this documentation - https://garyhall.org.uk/fast-blog-for-raspberry-pi.html . This person identified similar problems with me, that html took ages to write and need a easy to maintain manager. Lighttpd, if I am understanding correctly, is the web server, that's to substitute nginx and apache? Then I will try to first install it on the pi and see if it has similar error with nginx and apache. <and as I expected I also had similar error trying to install lighttpd of not fetching the right files. >if it has similar errors, I can try on my laptop, but I don't know how the server aspect works if I am trying out locally on my laptop.
error: frequent broken pipe. SSH crashed my house, and in PZI it also crashed, after I tried to curl a file.
I don't know if I try out these instructions it will be helpful for my ssh? https://homebrewserver.club/demystifying-ssh.html
- I also would like to know, if it's possible to buy a server? on Varia's website they mentioned a server that various other self hosted devices are connected. I always found myself frustrated using the pi as server (crashing, slow, don't know how to manage things..) I don't know if that's a good idea.
trying out pelican
├── Makefile
├── __pycache__
│ └── pelicanconf.cpython-37.pyc
├── content
│ ├── article2.md
│ ├── category
│ │ ├── article1.rst
│ │ └── displaytest.rst
│ ├── hellohellohello.md
│ ├── images
│ │ └── kaixin.png
│ ├── pages
│ │ ├── about.md
│ │ └── test.md
│ └── pdfs
├── output
│ ├── archives.html
│ ├── article3md.html
│ ├── author
│ │ └── biyi.html
│ ├── authors.html
│ ├── categories.html
│ ├── category
│ │ ├── category.html
│ │ ├── misc.html
│ │ └── review.html
│ ├── images
│ │ └── kaixin.png
│ ├── index.html
│ ├── my-first-review.html
│ ├── pages
│ │ ├── aboutmd.html
│ │ └── testmd.html
│ ├── tags.html
│ ├── the-first-article.html
│ ├── the-second-article.html
│ ├── theme
│ │ ├── css
│ │ │ ├── fonts.css
│ │ │ ├── main.css
│ │ │ ├── pygment.css
│ │ │ ├── reset.css
│ │ │ ├── typogrify.css
│ │ │ └── wide.css
│ │ ├── fonts
│ │ │ ├── Yanone_Kaffeesatz_400.eot
│ │ │ ├── Yanone_Kaffeesatz_400.svg
│ │ │ ├── Yanone_Kaffeesatz_400.ttf
│ │ │ ├── Yanone_Kaffeesatz_400.woff
│ │ │ ├── Yanone_Kaffeesatz_400.woff2
│ │ │ └── font.css
│ │ └── images
│ │ └── icons
│ │ ├── aboutme.png
│ │ ├── bitbucket.png
│ │ ├── delicious.png
│ │ ├── facebook.png
│ │ ├── github.png
│ │ ├── gitorious.png
│ │ ├── gittip.png
│ │ ├── google-groups.png
│ │ ├── google-plus.png
│ │ ├── hackernews.png
│ │ ├── lastfm.png
│ │ ├── linkedin.png
│ │ ├── reddit.png
│ │ ├── rss.png
│ │ ├── slideshare.png
│ │ ├── speakerdeck.png
│ │ ├── stackoverflow.png
│ │ ├── twitter.png
│ │ ├── vimeo.png
│ │ └── youtube.png
│ ├── this-is-a-test.html
│ └── try-to-see-if-this-shows.html
├── pelicanconf.py
├── publishconf.py
└── tasks.py
pelican differentiates pages and articles. pages are static, like about page. whereas articles are published under same categories under chronological order.
possibility of familarizing how jinja works with pelican?
about Jinja http://pzwiki.wdka.nl/mediadesign/Jinja
about blogging culture
reading this sentence from pelican documentation I start to thinking of blogging culture, for me it was popular since 2000s, would be nice to examine the culture and labor of blogging?
The questioned being asked in FAQ is - Is Pelican only suitable for blogs?
No. Pelican can be easily configured to create and maintain any type of static site.
a4 publishing
still in speculation! a4 means ordinary.
work archive site
fancyindex
trying the fancyindex module in nginx because saw it's employed in quite some sites.
fancyindex working on this manual while tinkering.
troubles
managing multiple website on one router and several raspberry pi look for help here:
http://pzwiki.wdka.nl/mediadesign/Homebrewserver_infrastructour
relevancies
publishing in Dat
dat://14e576a5cc61e7a0d6c43cd64cf292ec98c286920a0b4fff78e7058663901cd2/
why are domain names not free
load bunch of text (without formatting) to webpage
is php solution?
protocols
look into ipfs, an file transfer system comparable to http
session 23_09
hackpact play with wiki, pelican, as publishing tools diy networks look into pervasive labor union
hackpact!
http://pzwiki.wdka.nl/mediadesign/User:)biyibiyibiyi(/hackpact