Reverse proxy subdirectory / ROOT_URL not considered by Iron:Router when handling routes / Meteor Iron:Router library unmaintained

[deliciouslytyped]

I'm trying to set up Sandstorm with a reverse proxy, having it set up under a subdirectory (terminology?) of the base url.

Checking with the frontend on the dev console shows that setting BASE_URL in sandstorm.conf to something like "http://local.sandstorm.io:9999/sandstorm" correctly results in the setting propagating to meteor:

__meteor_runtime_config__.ROOT_URL
"https://local.sandstorm.io:9999/sandstorm" 

However the frontend continues to use the base url without the /sandstorm prefix.
It seems like the meteor Iron:Router library is unmaintained, and two of it's open issues and PRs are about adding this functionality.

This comment on a 3rd party project describes some of this; 4minitz/4minitz#152 (comment) , and apparently the Meteor docs recommend Flow Router now. (It seems like the Iron ecosystem was selected because it's for command line stuff?)

xref iron-meteor/iron-router#154 (comment)
iron-meteor/iron-url#17 (comment)

[xet7]

@deliciouslytyped

No, Iron Router is not unmaintained. If Sandstorm is ported from Meteor 2 to Meteor 3, it is possible to use newer Iron Router https://forums.meteor.com/t/iron-router-works-with-meteor-3/62218

Current Sandstorm does not work with subdomain or sub-url. Only this config works for me:

https://github.com/wekan/wekan/wiki/Sandstorm

[deliciouslytyped]

@ocdtrekkie pointed out that wanting to run in a subdirectory like this will probably be unsupported regardless of the technical means to do it, because that puts multiple applications in the same same-origin-policy security domain, and that's probably unwanted.

[deliciouslytyped]

I don't know whats up with the Meteor ecosystem, I'm not familiar with it, but it seems like the iron:router meteor package now points here: https://atmospherejs.com/iron/router -> https://github.com/meteor-compat/iron-router/

[xet7]

@deliciouslytyped

That repo is 4 years old. Newest forked Meteor 3 compatible repos are listed at beginning of this page:

https://forums.meteor.com/t/iron-router-works-with-meteor-3/62218

In Meteor ecosystem, there has been huge amount of updates. Meteor 3 uses Node.js 22.13.0 and MongoDB 7: https://docs.meteor.com/history . For multitasking, fibers have been changed to Async Await. Many speed optimizations have been done, and some more being developed. Some old dependencies are not needed anymore, those did not need porting. Some dependecies have different name in Meteor 3 compatible forks.

Many apps are still in progress of upgrading to Meteor 3. Some have already upgraded, like RocketChat. There are many Meteor 3 apps at production. Some dependencies are still being ported to Meteor 3. There are some new packages for Meteor 3 only, that did not exist before, like jam:offline for offline usage.

[ocdtrekkie]

I am going to throw wontfix on this just because I do not want people later to view this as "hosting at a subdirectory is supported". But I mean, if you get it to work with your patching you were doing, more power to you. ;)