9front - general discussion about 9front
 help / color / mirror / Atom feed
From: thinktankworkspaces@gmail.com
To: 9front@9front.org
Subject: Re: [9front] werc noob
Date: Sat, 15 Jan 2022 11:32:39 -0800	[thread overview]
Message-ID: <60D663688BB07C9446BDDE91DC8C3212@gmail.com> (raw)
In-Reply-To: <CEF0BEE0-BE7A-49AA-B862-76D0DD46BE5F@stanleylieber.com>

[-- Attachment #1: Type: text/plain, Size: 1589 bytes --]

Yes sorry. I guess I wanted to write that its a new install with sysupdate, and I create
a new user called www because why not. I can rcpu to that user and I can point 

/rc/bin/rc-httpd/select-handler

if(~ $SERVER_NAME 172.27.0.67){
#	PATH_INFO=$location
#	FS_ROOT=/usr/www/werc/sites/172.27.0.67
#	exec static-or-index
#}
 
The above works fine and I have a simple index.html also an index.md not that it matters
because it doesn't work when I change select-handler to the following

if(~ $SERVER_NAME 172.27.0.67){
	PATH_INFO=$location
	FS_ROOT=/usr/www/werc/sites/werc.cat-v.org
	exec static-or-cgi /usr/www/werc/bin/werc.rc
}
if not
	error 503

I don't exactly understand the purpose of intirc while In plan9 because I'm not running debian. 

/usr/www/werc contains the following:

README	bin/		lib/		sites/
apps/		etc/		pub/		tpl/

/usr/www/werc/etc contains
initrc		/users/
initrc.local

initrc.local has the following line 21 and 22

#path=($plan9port/bin . ./bin ./bin/contrib /bin /usr/bin)
path=(/usr/www/werc/bin . ./bin ./usr/www/werc/bin/contrib /bin /usr/bin)

not sure what plan9port is but I suspect its the werc package I guess

I have both werc-1.5.0.tar.gz and the one from hg pull. 

Makes no difference

at first I was getting an unknown file. But when I'm more explicit I get some data with the following:

mothra http://172.27.0.67/index.md


But this only shows the raw index.md. It does not show anything translated into a web format with actual bullets

I see nothing in logs other than 200 codes

And yes sorry for sending two more messages that were concat. 

[-- Attachment #2: Type: message/rfc822, Size: 3445 bytes --]

From: Stanley Lieber <sl@stanleylieber.com>
To: 9front@9front.org
Subject: Re: [9front] werc noob
Date: Sat, 15 Jan 2022 18:22:42 +0000
Message-ID: <CEF0BEE0-BE7A-49AA-B862-76D0DD46BE5F@stanleylieber.com>

On January 15, 2022 5:18:15 PM UTC, thinktankworkspaces@gmail.com wrote:
>sure I did a sysupdate and mk on everything like two days ago. 
>
>I moved /usr/www/werc/etc/initrc.local then changled line 21 to the following. 

your message was truncated.

sl

  parent reply	other threads:[~2022-01-15 19:37 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-15  9:07 thinktankworkspaces
2022-01-15  9:46 ` Kurt H Maier
2022-01-15 17:01   ` thinktankworkspaces
2022-01-15 18:26     ` Stanley Lieber
2022-01-15 19:40       ` thinktankworkspaces
2022-01-15 19:47         ` Stanley Lieber
2022-01-15 20:02           ` thinktankworkspaces
2022-01-15 17:20   ` thinktankworkspaces
2022-01-15 14:18 ` Stanley Lieber
2022-01-15 17:18   ` thinktankworkspaces
2022-01-15 18:22     ` Stanley Lieber
2022-01-15 19:24       ` thinktankworkspaces
2022-01-15 19:52         ` ori
2022-01-15 19:32       ` thinktankworkspaces [this message]
2022-01-15 20:12 thinktankworkspaces

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=60D663688BB07C9446BDDE91DC8C3212@gmail.com \
    --to=thinktankworkspaces@gmail.com \
    --cc=9front@9front.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).