Re: httpd & pixelfed

2024-05-29 Thread Kirill A . Korinsky
Greetings, On Wed, 29 May 2024 00:01:07 +0100, Am Jam wrote: > > For posterity's sake, my working /etc/httpd.conf is below: > Maybe it is worth making a port for pixelfed to allow others to install it as easily as pkg_add pixelfed with some polish documented in the description? -- wbr, Kirill

Re: httpd & pixelfed

2024-05-28 Thread Am Jam
Rubén, Crystal, & Stuart-- Your responses helped me figure it out. In particular, Stuart, you were right. My problem was having an absolute symlink from /var/www/pixelfed/public/storage -> /var/www/pixelfed/storage/app/public. Making this a relative symlink (i.e., cd /var/www/pixelfed/public && ln

Re: httpd & pixelfed

2024-05-27 Thread Stuart Henderson
On 2024-05-27, Am Jam wrote: > > Most of what makes pixelfed work is located in /var/www/pixelfed/public, > and hence pixelfed requires that the root directory be > /var/www/pixelfed/public. > So in /etc/httpd.conf I have the following lines: > - root "/pixelfed/public" > - directory index "in

Re: httpd & pixelfed

2024-05-27 Thread Rubén Llorente
Wild guess: When a request is made against a picture in /storage/, it triggers the location not found * rule. The rewritten request does never hit the location "/storage/*" rule because it now requests /index.php$something instead of any object within /storage. Try placing a matching /stor

httpd & pixelfed

2024-05-27 Thread Am Jam
Hi Everyone, I am trying to install and run pixelfed (think of it as a self-hosted instagram alternative) on OpenBSD 7.5, but I am having a problem with my /etc/httpd.conf. Unfortunately, pixelfed's installation instructions only provide an nginx example. For those of you familiar with nextcloud,