emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Tim Cross <theophilusx@gmail.com>
To: Max Nikulin <manikulin@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Serving .org files for worg (was: Re: Library of babel help)
Date: Sat, 30 Jul 2022 13:29:02 +1000	[thread overview]
Message-ID: <867d3v45xy.fsf@gmail.com> (raw)
In-Reply-To: <tc0m7o$omq$1@ciao.gmane.io>

Max Nikulin <manikulin@gmail.com> writes:

> On 01/07/2022 04:48, Tim Cross wrote:
>> 1. Just using the .org as the suffix of the url instead of the .html did
>> not work for me using two different browser. However, it did work for
>> ihor, so either I did something wrong or there is something in my setup
>> which is preventing that from working. Need to investigate further.
>> However, that is not my main issue.
> Tim, have you managed to achieve any progress with either nginx or with settings of your
> browsers?
> I have tried some variants of desktop environments with almost default setting without
> issues similar to yours.
> Org files are fetched to the Downloads folder without additional user actions (besides
> Firefox-91). It is not always obvious at first glance. With default settings:
> - Chromium displays a bar at the bottom of the window.
> - Firefox-102 (Ubuntu and Gnome, Arch and KDE) opens transient popup window. In
>   Ububntu-22.04 firefox and chromium are installed as snap packages.
> - Firefox-91 (Debian, Xfce) displays more traditional popup window to confirm download
>   (somehow it guesses that it is an org-mode file even for application/octet-stream
>  MIME-type).
> If I change MIME type then Chromium displays internally both text/plain and text/x-org,
> Firefox asks for an external application for text/x-org while text/plain is displayed in
> the browser tab.
> The following snippet should be added to nginx configuration to assign MIME type for .org
> files:
> types {
>         # Chromium opens text/x-org in the browser tab,
>         # Firefox downloads files and offers to open in some other application.
>         # text/x-org      org;
>         text/plain      org;
> }
> See http://nginx.org/en/docs/http/ngx_http_core_module.html#types
> It is assumed that default mime.types is included somewhere.

Yes, I do have it working in my local dev environment. I have also made
some progress with improvements with both the nginx and worg layout, but
it isn't ready for 'prime time' yet. My testing with different browsers
did show variation across browsers and this is something I would like to
avoid. I also have come to a similar conclusion to you and think it is
about setting a mime handler for org files in nginx.  

Unfortunately, during this whole process, I had a major hardware failure
and have had to re-build my whole system. One of the things I did have
on my TODO list was to migrate from using Ubuntu to Fedora and while I
was going to do that later, given that I had to restore from backups
onto a new system, I decided to make the switch now.

While immensely happy with Fedora and pleased to be free of some of the
stuff I didn't like with current Ubuntu, it has been 20 years since I've
run a RH based distro, so there has been some learning curve to deal
with which has slowed down my progress with worg (especially getting up
to speed with SELinux, dnf and flatpak). However, it is progressing and
I hope to have something for everyone to look at sooner rather than

I have now become a member of the SourceHut community and I think it
should be possible to deploy a dev/uat version of the new worg site to
their pages site. This should provide a relatively easy way for everyone
who is interested to have a look at the changes I'm making. I'm also
hoping this will also provide a workable 'dev' site for the main worg
repository so that anyone with the correct permissions can make changes,
deploy to the dev site to verify nothing is broken and then push it to
the production site. My hope is this will make people more relaxed and
confident in contributing while also ensuring a good user experience for
worg users. I still have a bit of work to do getting to grips wiht the
sh tools and understanding how they can help. There is definitely some
good stuff here, but there are still some rough edges you have to work
with and some different concepts/approaches I'm not yet familiar with. 

The good news is that I think all the necessary prerequisite stuff is
now working well and I can focus on the specifics of worg and the
various moving parts which make up orgmode.org!

  reply	other threads:[~2022-07-30  3:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-16  8:15 Library of babel help Tim Cross
2022-06-16  9:30 ` Tim Cross
2022-06-30  7:23 ` Ihor Radchenko
2022-06-30  9:06   ` Tim Cross
2022-06-30 13:25     ` Ihor Radchenko
2022-06-30 15:45     ` Serving .org files for worg (was: Re: Library of babel help) Max Nikulin
2022-06-30 17:04       ` Max Nikulin
2022-06-30 21:48       ` Tim Cross
2022-07-01  5:42         ` Max Nikulin
2022-07-29 13:10         ` Max Nikulin
2022-07-30  3:29           ` Tim Cross [this message]
2022-09-28  5:59           ` Serving .org files for worg Bastien

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:

  List information: https://www.orgmode.org/

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

  git send-email \
    --in-reply-to=867d3v45xy.fsf@gmail.com \
    --to=theophilusx@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=manikulin@gmail.com \


* 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.
Code repositories for project(s) associated with this public inbox


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 read-only IMAP folder(s) and NNTP newsgroup(s).