Published passenger app doesn't appear in dropdown menus

Get Help
1

Hi all,

I’m trying to publish a passenger app at our site for the first time, but it is not appearing on the dropdown on the top menu bar as I expect. Any tips on debugging this?

I’m following the Python tutorial, and the app works in my sandbox. After manually deploying it, I have this in /var/www/ood/apps/sys/quota/manifest.yaml

name: Quota
description: Display quotas
icon: fa://hdd-o
category: Files
subcategory: Utilities

and after initializing, here is /var/lib/ondemand-nginx/config/apps/sys/quota.conf

location ~ ^/pun/sys/quota(/.*|$) {
  error_page 404 @error_404;
  alias /var/www/ood/apps/sys/quota/public$1;
  passenger_base_uri /pun/sys/quota;
  passenger_app_root /var/www/ood/apps/sys/quota;
  passenger_document_root /var/www/ood/apps/sys/quota/public;
  passenger_enabled on;

  passenger_app_env production;

  # Give apps the ability to download files from filesystem
  passenger_env_var HTTP_X_SENDFILE_TYPE X-Accel-Redirect;
  passenger_env_var HTTP_X_ACCEL_MAPPING "/=/sendfile";
  passenger_set_header X-Sendfile-Type "X-Accel-Redirect";
  passenger_set_header X-Accel-Mapping "/=/sendfile";
}

I can go directly to https://our-ood-domain.edu/pun/sys/quota/ and see the app correctly. However, I can’t see it in the “Files” dropdown.

Many thanks,
Ron

Ron Rahaman : Senior Research Scientist : Partnership for an Advanced Computing Environment : Georgia Institute of Technology

2

That could be a bug/behavior where we treat that category special. As in, I guess we never anticipated someone adding apps to it?

If you look at this if/else block we appear to treat the shell category the same. You may be able to do something with custom navbar configuration to override it, but I call it a bug because we should allow for this use case.

3

Gotcha. I’d actually like to use a new dashboard category for my passenger app (I was using Files because the tutorial showed it). But when I use a new category, I can’t see the passenger app in the nav bar, either.

Here’s my manifest in /var/www/ood/apps/sys/quota/manifest.yaml, using a new “Quotas” category:

---
name: Storage Quota
category: Quotas
description: This is the Storage Quota app

And here’s where I set the categories that appear in the nav bar /etc/ood/config/ondemand.d/ondemand.yml.

nav_bar:
  - interactive apps
  - files
  - jobs
  - clusters
  - quotas
  - my interactive sessions

All the categories appear in the nav bar except for Quotas.

4

We are on OnDemand v4.1.4

5

Reading the documentation, that should work. I’ll look into it a bit.

6

OK odd, I was able to test with 4.1 and it worked for me. I wonder if the sub-category is somehow throwing this off - I tested with an app in a special category but no sub-category.

Beyond that, I’d maybe try a permission issue?

Manifest seeks OK - though maybe you need a role? The app I tested with has one. I believe only batch_connect role is meaningful, but maybe an empty role is somehow buggy?

7

Oh gosh, I figured it out. My manifest was named manifest.yaml, not manifest.yml. Changing its name to the latter fixed everything.