From: thinktankworkspaces@gmail.com
To: khm@sciops.net, 9front@9front.org
Subject: Re: [9front] werc comments egine
Date: Mon, 17 Jan 2022 01:07:17 -0800 (PST) [thread overview]
Message-ID: <86D3B9BCC6BDB198AF0DA88F220F73DB@gmail.com> (raw)
On Sun, Jan 16, 2022 at 06:56:41PM -0800, thinktankworkspaces@gmail.com wrote:
> So I added
>
> conf_enable_comments
> conf_enable_wiki
>
> Also created a user will and added them to members admin. I
> can log in fine but I can't really post anything.
>
> Could not post comment due to internal error, sorry.
>
> I see in the logs its some permission error. Any hints where? what?. I tried to manual creat the folder as that user
>
>
> umask: '/usr/bin' does not exist
> mkdir: can't create sites/cirno/_werc/comments/1642387681: 'sites/cirno/_werc/comments/1642387681' create -- in a non-directory
> ERROR XXX: Could not create comment: mkdir 71270: error
> cirno/ - Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.2 Safari/605.1.15 - POST - md_handler sites/cirno/index.md - lib/default_master.tpl
> Sun Jan 16 18:48:01 PST 2022 :: cirno :: POST / HTTP/1.1 :: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.2 Safari/605.1.15 :: 200 :: http://cirno/
> tee: cannot open /tmp/fltr_cache/923e12ff215b0e44105268bcdd2950bffec9fc41/71285: '/tmp/fltr_cache' does not exist
> mv: can't stat /tmp/fltr_cache/923e12ff215b0e44105268bcdd2950bffec9fc41/71285: '/tmp/fltr_cache' does not exist
> Auth: success
> Sun Jan 16 18:48:01 PST 2022 :: cirno :: GET /pub/style/style.css HTTP/1.1 :: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.2 Safari/605.1.15 :: 200 :: http://cirno/
>
The comments directory needs to be writeable as whatever system user
your web server runs under.
I don't know what that umask error is but I'd work it out before letting
the public access this installation.
khm
Yes this seems kind of silly. I have created a user called www and as that user ran webfs.
I did an hg pull to get werc installed as user www.
I have changed select /rc/bin/rc-httpd/select-handler. I can
log in fine. However as that user It seems I need to run bind -a /bin /usr/bin to get access
to other utilities.
my line 21 is as follows for /usr/www/wer/etc/initrc
path=(. ./bin ./bin/contrib /bin /usr/bin)
Not sure why umask is needed when it doesn't exist in 9front. I'm not sure how to make
everything writable as that user. There is no recursive chmod -R. Instead I manually
went to every directory and every file and typed chmod 777 on everything. Which is dumb
but I'm kind of at a loss. And no this is definitely not public website yet.
next reply other threads:[~2022-01-17 9:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-17 9:07 thinktankworkspaces [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-01-17 2:56 thinktankworkspaces
2022-01-17 7:43 ` Kurt H Maier
2022-01-17 23:47 ` thinktankworkspaces
2022-01-18 0:23 ` Stanley Lieber
2022-01-18 2:21 ` thinktankworkspaces
2022-01-18 3:20 ` thinktankworkspaces
2022-01-18 5:06 ` Stanley Lieber
2022-01-18 8:13 ` thinktankworkspaces
2022-01-18 3:20 ` thinktankworkspaces
2022-01-18 7:27 ` 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=86D3B9BCC6BDB198AF0DA88F220F73DB@gmail.com \
--to=thinktankworkspaces@gmail.com \
--cc=9front@9front.org \
--cc=khm@sciops.net \
/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).