GPX file upload error

[nebulon]

Did not even think of such a use-case, but I have never really worked with .gpx files as such. I will add the watcher directory also then

[nebulon]

So the app already has /app/code/tmp linked to /tmp/dawarich. So the imports/watched can already be used, though this is all in the /tmp mount. Not sure what upstream intends here, is one supposed to upload to a /tmp folder manually and how are things cleaned up there?

[imc67]

Mmm, when I go to Filemanager (of the app) I do see a folder “storage” but not “temp”, should I create it including “imports/watched”?

[imc67]

@nebulon said in GPX file upload error:

is one supposed to upload to a /tmp folder manually and how are things cleaned up there?

I’m not a programmer but my assumption is that the developer means by “temp” a folder that a user or the system can use for files that temporarily exist, either by ingress or whatever. I guess it can be mounted to /app/data/ so a user can get there?

Like in the docs, only the watched folder mapping to app/data?

volumes:
      - dawarich_public:/var/app/public
      - dawarich_watched:/var/app/tmp/imports/watched
      - dawarich_storage:/var/app/storage

[imc67]

I just noticed that “public” also needs to be symlinked, there are editable files but also the “export” folder needs to be writable. I guess as mentioned before all 3 needs to be symlinked to /app/data/?

[nebulon]

do you know what the public folder does?

[imc67]

@nebulon said in GPX file upload error:

do you know what the public folder does?

When I use Terminal of the app and go there I see some html files, images and export folder. I guess it’s all configurable to what you want to show in your browser.

[nebulon]

So we need to first understand what is supposed to be there, since content in /tmp will get regularily (though only after 10 days) purged from disk. Have to play more with the app to see what it expects

[nebulon]

So after reading through the code, it seems public/ is mounted as a volume probably to customize the page, however given that it also contains the code from the release, we should not make that writable, otherwise we have a hard time to update.

[nebulon]

The export also works fine for both .json and .gpx. Looks like the export/ folder is not actually used there.

I also found that the app stores the pid file in /tmp which will not go well when regularly purged, so I think we will move all that to /run instead.

[nebulon]

New package release links the watched folder from /app/data however I was not able to get the app actually consume anything from that folder, not even without the linking. So this may need more debugging in the app itself it seems.