Feature request: Define unpacking location of AppImage by setting TMPDIR environment variable

Aperta
#205 2 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
30/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Ferma
Stack tecnologico
php
Ambito
backend

Direzione di ricerca

Start by reading proxy.php, which the issue identifies as the place where TMPDIR could be set, and trace how the app's admin settings are stored and made available there. The requested outcome is a configurable extraction path that is used as TMPDIR when launching the AppImage; verify that the setting works and does not break the app's integrity checks.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

This might be somewhat of an edge case, but it'd be great if it was possible to define the path in which the AppImage extracts itself in case FUSE is unavailable.

Scenario: I'm running Nextcloud on a shared hosting provider's server which uses cPanel as management platform. By default, the AppImage extracts its contents into /tmp, which is mounted with noexec - apparently that's quite the default setup with cPanel. Obviously, the AppImage gets extracted, but the binaries inside can't be run which results in permission errors and of course the whole app not working.

On the other hand, binaries residing inside the "jail" of my hosting account (e.g. /home/myaccount/mybinarycollection/) can be run without any issues.

It is possible to achieve that by setting the environment variable TMPDIR in the context where the AppImage is executed. Problem is: In such a more or less restrictive environment, setting environment variables for the PHP processes as well as the exec()'d AppImage command is virtually impossible. I can't set environment variables for PHP in cPanel; I can't directly edit the php.ini; bash -c is non-login non-interactive, thus ignores .bashrc and .profile; /etc/environment is obviously read-only for me; etc.

So, as far as I'm concerned, the only way to reliably get this done is to set TMPDIR within proxy.php, either by putenv('TMPDIR=/home/myaccount/mybinarycollection')or by weaving it into $launchCmd. I successfully tried the putenv() method, but of course it breaks Nextcloud's code integrity check and will be overwritten with every update. Incorporating it into $launchCmd might be a safer call though, since putenv() might be disabled by hosting providers.

So my request would be to make the desired extraction path configurable in the app's admin backend and, if configured, have proxy.php set it as content of TMPDIR; of course given that you, dear developers, consider this an issue worth addressing.

Lingua principale
PHP
Stelle
156
Fork
37
Merge medio
23h 51m
PR unite (30g)
2

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di CollaboraOnline/richdocumentscode

Tutte le issue di CollaboraOnline/richdocumentscode

Issue simili

Altre issue su PHP

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.