Editable File Types

Editable File Types is an Unraid plugin that lets you choose which file extensions the File Manager opens in its text editor, from a settings page instead of…

  • Plugins
  • Tools & Utilities
Editable File Types is an Unraid plugin that lets you choose which file extensions the File Manager opens in its text editor, from a settings page instead of editing /boot/config/editor.cfg by hand. Tick common text formats (json, yaml, toml, md, env, log and more) or add your own, undo the last change, or restore the file exactly as it was before the plugin touched it. A backup is written before every save. It only reads and writes that one file, runs nothing in the background and makes no network connections.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

39/100 Low

Maintained
70last commit 57 days ago
Popular
00 GitHub stars
Easy to install
251 install platform, install notes
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today

GitHub stars
0
Open issues
0
Last commit
2026-09-25
Latest release
2026.09.25
License
MIT
Activity
stale

Checked yesterday - source: GitHub (joshmans/unraid-text-editor-extensions)

Resources & Compatibility

Requirements not published yet.

First-install notes

  • Set up the project and .env file Clone the repo, run `npm install` to get the code libraries it needs, then run `cp .env.example .env` and fill in the settings. Without that .env file, Editable can start without database or login settings and your site may not save content. source
  • Install Litestream backup tool Run `npm run litestream:install` to add Litestream, which keeps a running copy of your SQLite database (a single-file database) for backup safety. If its version does not match the server version, syncing or backups can fail and you may lose recent edits. source
  • Keep the database files safe Your documents, settings, sessions, and asset links live in the SQLite database files. If you delete or overwrite them, your editable content disappears, so back them up before moving storage or servers. source
  • Find it in Settings After installing, open the Unraid web UI and go to Settings → Utilities → Editable File Types to tick the extensions you want the File Manager to open in its text editor. A backup of editor.cfg is written before every save, so you can undo the last change or restore the original file at any time. source
  • Install and open the settings page Install the Editable File Types plugin from the Unraid App store; after installation it appears under Settings -> Utilities -> Editable File Types in the web UI. source

Fetched yesterday - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How do I install Editable File Types in Unraid?

Open Plugins and choose Install Plugin, then paste the provided plugin URL. After installation, use Settings, Utilities, Editable File Types to save your choices.

What format does editor.cfg use?

It lists one extension per line, without the dot. As a safety net, a file that has commas and no newlines at all is treated as comma-separated and written back the same way.

How can I undo a change or restore the original file?

Undo Last Change restores editor.cfg.bak. Restore Original restores editor.cfg.orig, the untouched copy saved the first time the page sees the file.

Will extensions I added by hand be removed?

No. The page keeps extensions you added by hand, and the additional extensions box accepts comma- or newline-separated values without dots.

What happens if I uninstall the plugin?

Removing the plugin deletes only its own page. /boot/config/editor.cfg is left as is, and the .bak and .orig backups stay next to it.

Answers sourced from github.com

Community

Collected 48 days ago - public community threads