allow definition of a separate tmp folder - system requirements

未关闭
#27 0 条评论 5 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
30/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
停滞
技术栈
linux

调研方向

Start by locating where the app uses the system /tmp directory and how temporary files are created; the issue names no source files or tests. Compare the requested options—restricting work to the opened file or allowing a separate temporary directory—and clarify which behavior is expected. Done means the chosen behavior is configurable or otherwise defined, with temporary-file use no longer relying on an unsuitable /tmp mount.

由索引模型根据 Issue 内容生成。

描述

documentation enhancement

I just installed NC19 and found this app. It works for me fine, but ...

The App uses system /tmp for temporary files. This is fine if it is big enough. However on my NC server I have a 256MB tmpfs mount for /tmp to speed things up. Opening a simple file creates ~200MB on /tmp for different tasks. If other programs are also using /tmp the system could crash due to out of space errors.

The reason seams to be that other documents available in NC are also loaded in the background. I for example found data of a pdf file in the systemd-private--apache2.service- folder below /tmp.

Would it be possible to restrict the tool to the opened file? Or, as I have enough hard disk space, it would be no problem to provide 1GB or so for temporary files. Is there a possibility to set this as an option? A possible path would be /var/tmp/

Thanks for the nice work!

主要语言
PHP
星标
156
派生
37
平均合并
23 小时 51 分钟
30 天内合并 PR
2

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

CollaboraOnline/richdocumentscode 的其他 Issue

查看 CollaboraOnline/richdocumentscode 的全部 Issue

相似的 Issue

更多 PHP Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。