📂 Web File Browser

Preview

Build Go Report Card Documentation Version Chat IRC

filebrowser provides a file managing interface within a specified directory and it can be used to upload, delete, preview, rename and edit your files. It allows the creation of multiple users and each user can have its own directory. It can be used as a standalone app or as a middleware.

Features

Please refer to our docs at https://filebrowser.org/features

Install

For installation instructions please refer to our docs at https://filebrowser.org/installation.

Configuration

Authentication Method - You can change the way the user authenticates with the filebrowser server

Command Runner - The command runner is a feature that enables you to execute any shell command you want before or after a certain event.

Custom Branding - You can customize your File Browser installation by change its name to any other you want, by adding a global custom style sheet and by using your own logotype if you want.

Contributing

If you're interested in contributing to this project, our docs are best places to start https://filebrowser.org/contributing.

Comments
  • drop package.json, use yarn instad of npm, add build_in_docker.sh

    drop package.json, use yarn instad of npm, add build_in_docker.sh

    I found no info about how one should proceed to modify the frontend and rebuild filebrowser. It seems that package.json is used, which requires to push resources either to the npm or to a git repo. Moreover, because node_modules is removed in build.sh, any local changes are deleted.

    This PR follows a different approach. frontend is expected to be a subdir of this repo, but ignored through .gitignore. When build.sh is executed, the frontend is cloned if not present. dist is always cleared. Then, dependencies of the frontend are downloaded/updated and the frontend is built. Last, because the path to the rice box is changed in filebrowser.go, the content of dist can be packed directly.

    For those users that don't want to install nodejs and npm/yarn locally, build_in_docker.sh is provided. It runs a golang:alpine container, installs the required dependencies and executes build.sh. Indeed, an image name hacdias/filebrowser:dev can be provided, in order to avoid installing the tools each time.

  • X-Content-Type header not defined

    X-Content-Type header not defined

    Whenever I try to do any action through the admin interface that would require a POST request, I get a Something went wrong error in the GUI. When I looked in the error log, it showed X-Content-Type header not defined. Is there some configuration that I missed? I am using caddy/hugo out of the box.

    Error log:

    28/Feb/2016:10:24:29 -0500 [ERROR 400 /admin/edit/content/index.md] X-Content-Type header not defined
    28/Feb/2016:10:25:00 -0500 [ERROR 400 /admin/edit/config.toml] X-Content-Type header not defined
    28/Feb/2016:10:25:05 -0500 [ERROR 400 /admin/edit/config.toml] X-Content-Type header not defined
    28/Feb/2016:10:25:09 -0500 [ERROR 400 /admin/edit/config.toml] X-Content-Type header not defined
    28/Feb/2016:10:27:14 -0500 [ERROR 400 /admin/edit/content/index.html] X-Content-Type header not defined
    28/Feb/2016:10:27:20 -0500 [ERROR 400 /admin/edit/content/index.html] X-Content-Type header not defined
    28/Feb/2016:10:28:37 -0500 [ERROR 400 /admin/edit/content/index.html] X-Content-Type header not defined
    28/Feb/2016:10:30:59 -0500 [ERROR 406 /admin/edit/content/home] File format not supported.
    28/Feb/2016:10:30:59 -0500 [ERROR 406 /admin/edit/content/home] File format not supported.
    28/Feb/2016:10:31:21 -0500 [ERROR 400 /admin/edit/content/home.md] X-Content-Type header not defined
    28/Feb/2016:11:03:57 -0500 [ERROR 400 /admin/edit/content/home.md] X-Content-Type header not defined
    28/Feb/2016:11:04:27 -0500 [ERROR 400 /admin/edit/config.toml] X-Content-Type header not defined
    28/Feb/2016:11:05:01 -0500 [ERROR 400 /admin/edit/config.toml] X-Content-Type header not defined
    28/Feb/2016:11:05:17 -0500 [ERROR 400 /admin/edit/config.toml] X-Content-Type header not defined
    28/Feb/2016:11:14:51 -0500 [ERROR 400 /admin/edit/content/home.md] X-Content-Type header not defined
    28/Feb/2016:11:14:55 -0500 [ERROR 400 /admin/edit/content/home.md] X-Content-Type header not defined
    
  • Version 2.0

    Version 2.0

    TODO

    • [x] merge: https://github.com/filebrowser/filebrowser/pull/575
    • [x] finish docs: https://docs.filebrowser.xyz/
    • [x] cleanup https://filebrowser.xyz/
    • [x] check if docker image is OK

    After Release

    • Caddy plugin release will be tied with next Caddy release which might take a while yet.

    Hi everyone!

    I was looking and the repo and noticed we have already more than 3800 stars and it makes me sad to know that the project is no longer active or even working on master...

    In one/two months I'll have a break between uni semesters and I was thinking about giving this a clean up (and to the front-end too: it has a lot of old deps, and I'd like to move it to React).

    With that revamp we'd remove the integration with Caddy, at least directly to the code. We could create a plugin that uses or even that downloads the binary. The integration with Caddy is more troublesome that it seems to be and it has always put some constrains on how we structure the code and the development.

    In other news, the BoltDB DB is no longer active and I thought we could move to something more straightforward, with more background and with more tooling available such as SQLite.

    The point would be to clean-up this repo and frontend, use go.mod and remove Caddy direct integrations (it can always be proxied by Caddy).

    Also, with this rewrite, take in account the storage "issues" (#371).

    I'm waiting to hear your feedback: @1138-4EB @Equim-chan

  • Something really went wrong

    Something really went wrong

    I just download the binary package from the site and ran with a new created account, which has administrator permission, and results with the error.

    image

    image

    Testing procedure:

    1. login with admin
    2. create a new account with administrator permission, and assign a accessable path as scope
    3. login with the new account, give me the error
    4. logout and login back with admin account, give me the error
    5. delete the filemanager.db, and login with admin account, the error gone
    6. remove the filemanager.db, create a filemanager.yaml with specified port and baseURL, login with admin, give me the error

    My system info: Linuxmint 18.3/Centos 7

  • 🆘 Need Maintainers

    🆘 Need Maintainers

    This project is not under active development, i.e., new features won't be created and deep bugs might be hard to be fixed. A small set of developers is taking care of keeping it building and fixing small issues.

    If you're interested in becoming a maintainer of this project, please let us know through this issue and start contributing. It would be awesome for the more than 3000 people that starred this project!

  • New Dockerfile

    New Dockerfile

    Continuation of https://github.com/filebrowser/filebrowser/pull/575#issuecomment-451699904

    @1138-4EB I added the entry point so the user wouldn't need to set the --port 80 flag if they wan't to add more flags to the command. I saw that in postgres Docker image.

    We could remove it, but then the user would put the --port 80 if they add anything else to the command.

    FROM scratch
    
    COPY --from=filebrowser/dev /etc/ssl/certs/ca-certificates.crt /etc/ssl/certs/ca-certificates.crt
    
    VOLUME /tmp
    VOLUME /srv
    EXPOSE 80
    
    COPY filebrowser /filebrowser
    
    ENTRYPOINT [ "/filebrowser" ]
    CMD [ "--port=80" ]
    

    If you don't add anything after the image name, it will run filebrowser --port 80. If you add x, it will run filebrowser x and remove the --port 80. This is because we can't have the flag always there. Some commands would fail.

    But yes, we can remove the entrypoint. There is a quick setup when the DB doesn't exist and the user doesn't call filebrowser init.

  • [WIP] feat(BREAKING CH.): coding cleanup and v2.0.0

    [WIP] feat(BREAKING CH.): coding cleanup and v2.0.0

    Breaking changes

    • Previous configuration database and configuration files are not compatible.
    • Old share links ARE NOT compatible with the new configuration hence not imported.
    • DOES NOT have direct integration with Hugo nor Jekyll.
    • DOES NOT have user-specific CSS. The admin can customize for the whole installation.
    • Command runner ROOT variable is now SCOPE.
    • Command runner FILE variable is now an absolute path and not relative to SCOPE.

    TODOS

    • [ ] fix: files header not scrolling
    • [x] add user/global rules via CLI
    • [x] Merge https://github.com/filebrowser/frontend/pull/46
    • [x] Merge and archive https://github.com/filebrowser/community/pull/7
    • [x] Command to import old DB and Config files.
    • [x] Re-build Share Page
    • [x] Cleanup README.
    • [x] close #572: symlink should not be treated as file
    • [x] fix #402: disallow rules are now respected
    • [x] fix: folder downloads are empty
    • [x] PERF: got slower with the new FS. Maybe don't use the userFs and create MatchRules that can take many rules as arg (variadic).
    • [x] close #424: global allow/disallow rules
    • [x] FIx #594
    • [x] fix #593
    • [x] Add branding to settings
    • [x] Re-build Command Web Socket
    • [x] Make it work with just filebrowser -s /path.
    • [x] Re-build Search Web Socket
    • [x] close #583: dirs cannot be opened by click
    • [x] Pick new code editor
    • [x] rebuild settings
    • [x] close #326: add default sort mode
    • [x] close #420: custom branding
    • [x] Built-in HTTPS support
    • [x] Re-add Travis
    • [x] close #576: add IP on logging
    • [x] close #469: go.mod
    • [x] close #358: edit every text file
    • [x] close #314: "
    • [x] close #568: limit the size of text files to open
    • [x] close #562: closed via CLI tooling
    • [x] close #381: "
    • [x] close #257: "
    • [x] close #435: "
    • [x] close #401: "
    • [x] close #246: "
    • [x] close #371: CLI tooling + unique DB + no config file
    • [x] close #502: more permissions (not by folder though, still by user)
    • [x] close #350: " (download perm)
    • [x] close #567: archiver 3 implemented
    • [x] addresses #301: Auther interface
    • [x] close #577
    • [x] close #77: no Hugo integration
    • [x] close #523: "
    • [x] close #555: "
    • [x] close #507: no per-user CSS, only global
    • [x] close #439: "signup" is a global setting
    • [x] close #489: database rework
  • Change admin login

    Change admin login

    I installed filemanager using the docker latest image. More an enhancement proposal than an issue but I would like to change the "admin" login to another name, but when I try to edit the admin user I am redirected to the "new user" form. Maybe I just did not find the way to do it, but I feel like it is not a good practice to force the admin login to be "admin".

  • Saving posts / video from testing

    Saving posts / video from testing

    Hi, Matt encouraged me on Hugo forum to sent You some comments from my test. I could not write .md file. Here you have my experiences:

    https://www.icloud.com/sharedalbum/#B0WJtdOXm0casHF

    Maybe this is connected to OS user rights?

    I'll be happy to spreading also some suggestions regarding functionalities if You are interested.

    Best Regards,

  • Some txt file can be preview and edit, but some can not.

    Some txt file can be preview and edit, but some can not.

    Description Some txt file can be preview and edit, but some can not.

    Expected behaviour All txt file can be preview? Otherwise why preview and edit function?

    What is happening instead? Some txt file can be preview and edit, but some can not. Like I have a file.txt in ./files, it just can be download, it can not being preview and edit. But test.txt in ./files/test can being preview and edit, and of course download too.

    Additional context I am using filebrowser in ubuntu 18.04 lts x86_64, launch it by a custom server:

    #/etc/systemd/system/filebrowser.service
    
    [Unit]
    Description=File Browser v2 Service
    After=network.target
    Wants=network.target
    
    [Service]
    Type=simple
    PIDFile=/var/run/filebrowser.pid
    ExecStart=/usr/local/bin/filebrowser -c=/home/filebrowser/config.json -d=/home/filebrowser/filebrowser.db -r=/home/filebrowser
    RemainAfterExit=no
    Restart=on-failure
    RestartPreventExitStatus=23
    
    [Install]
    WantedBy=multi-user.target
    

    file /home/filebrowser/config.json (seem does not have effect at all):

    {
      "settings": {
        "signup": false,
        "defaults": {
          "scope": "./files",
          "locale": "zh-tw",
          "viewMode": "list",
          "sorting": {
            "by": "name",
            "asc": false
          },
          "perm": {
            "admin": false,
            "execute": false,
            "create": false,
            "rename": false,
            "modify": true,
            "delete": false,
            "share": false,
            "download": true
          },
          "commands": []
        },
        "authMethod": "json",
        "branding": {
          "name": "Magical Space J1",
          "disableExternal": false,
          "files": "/home/filebrowser"
        },
        "commands": {
          "after_copy": [],
          "after_delete": [],
          "after_rename": [],
          "after_save": [],
          "after_upload": [],
          "before_copy": [],
          "before_delete": [],
          "before_rename": [],
          "before_save": [],
          "before_upload": []
        },
        "shell": [],
        "rules": []
      },
      "server": {
        "root": ".",
        "baseURL": "",
        "tlsKey": "",
        "tlsCert": "",
        "port": "8080",
        "address": "127.0.0.1",
        "log": "stdout"
      },
      "auther": {
        "recaptcha": null
      }
    }
    

    How to reproduce? I don't know yet. There's no specific pattern.

  • Custom styles not loading

    Custom styles not loading

    From @bronzehedwick on August 1, 2016 21:33

    Hello, thanks for the great plugin!

    I am using filemanager in conjunction with the hugo plugin, and wanted to extend the CSS via the styles directive. However, my custom styles are not loaded when I restart Caddy.

    Any help would be greatly appreciated!

    I'm on OS X 10.10.5 using Caddy 0.9.0.

    My Caddyfile looks like this:

    localhost:2020
    gzip
    log log/caddy-access.log
    root public
    hugo
    basicauth /admin "admin" "password"
    filemanager  {
      show content
      on admin
      styles ./assets/css/filemanager.css
      frontmatter yaml
    }
    

    Note: Caddy does complain if I give a filepath to a non-existing css resource, so it does seem to be working on some level.

    Thanks!

    Copied from original issue: hacdias/filemanager-old#13

  • Command line argument to set default theme to dark mode

    Command line argument to set default theme to dark mode

    Im running filebrowser in kubernetes and I would like to be able to add a command in my deployment yaml to set the default theme as dark mode instead of light. Something like FB_THEME=DARK/LIGHT

  • build(deps): bump json5, @vue/cli-plugin-babel, @vue/cli-plugin-eslint, @vue/cli-service and webpack in /frontend

    build(deps): bump json5, @vue/cli-plugin-babel, @vue/cli-plugin-eslint, @vue/cli-service and webpack in /frontend

    Bumps json5 to 2.2.2 and updates ancestor dependencies json5, @vue/cli-plugin-babel, @vue/cli-plugin-eslint, @vue/cli-service and webpack. These dependencies need to be updated together.

    Updates json5 from 0.5.1 to 2.2.2

    Release notes

    Sourced from json5's releases.

    v2.2.2

    • Fix: Properties with the name __proto__ are added to objects and arrays. (#199) This also fixes a prototype pollution vulnerability reported by Jonathan Gregson! (#295).

    v2.2.1

    • Fix: Removed dependence on minimist to patch CVE-2021-44906. (#266)

    v2.2.0

    • New: Accurate and documented TypeScript declarations are now included. There is no need to install @types/json5. (#236, #244)

    v2.1.3 [code, diff]

    • Fix: An out of memory bug when parsing numbers has been fixed. (#228, #229)

    v2.1.2

    • Fix: Bump minimist to v1.2.5. (#222)

    v2.1.1

    • New: package.json and package.json5 include a module property so bundlers like webpack, rollup and parcel can take advantage of the ES Module build. (#208)
    • Fix: stringify outputs \0 as \\x00 when followed by a digit. (#210)
    • Fix: Spelling mistakes have been fixed. (#196)

    v2.1.0

    • New: The index.mjs and index.min.mjs browser builds in the dist directory support ES6 modules. (#187)

    v2.0.1

    • Fix: The browser builds in the dist directory support ES5. (#182)

    v2.0.0

    • Major: JSON5 officially supports Node.js v6 and later. Support for Node.js v4 has been dropped. Since Node.js v6 supports ES5 features, the code has been rewritten in native ES5, and the dependence on Babel has been eliminated.

    • New: Support for Unicode 10 has been added.

    • New: The test framework has been migrated from Mocha to Tap.

    • New: The browser build at dist/index.js is no longer minified by default. A minified version is available at dist/index.min.js. (#181)

    • Fix: The warning has been made clearer when line and paragraph separators are used in strings.

    • Fix: package.json5 has been restored, and it is automatically generated and

    ... (truncated)

    Changelog

    Sourced from json5's changelog.

    v2.2.2 [code, diff]

    • Fix: Properties with the name __proto__ are added to objects and arrays. (#199) This also fixes a prototype pollution vulnerability reported by Jonathan Gregson! (#295).

    v2.2.1 [code, diff]

    • Fix: Removed dependence on minimist to patch CVE-2021-44906. (#266)

    v2.2.0 [code, diff]

    • New: Accurate and documented TypeScript declarations are now included. There is no need to install @types/json5. (#236, #244)

    v2.1.3 [code, diff]

    • Fix: An out of memory bug when parsing numbers has been fixed. (#228, #229)

    v2.1.2 [code, diff]

    • Fix: Bump minimist to v1.2.5. (#222)

    v2.1.1 [code, diff]

    • New: package.json and package.json5 include a module property so bundlers like webpack, rollup and parcel can take advantage of the ES Module build. (#208)
    • Fix: stringify outputs \0 as \\x00 when followed by a digit. (#210)
    • Fix: Spelling mistakes have been fixed. (#196)

    ... (truncated)

    Commits
    • 14f8cb1 2.2.2
    • 10cc7ca docs: update CHANGELOG for v2.2.2
    • 7774c10 fix: add proto to objects and arrays
    • edde30a Readme: slight tweak to intro
    • 97286f8 Improve example in readme
    • d720b4f Improve readme (e.g. explain JSON5 better!) (#291)
    • 910ce25 docs: fix spelling of Aseem
    • 2aab4dd test: require tap as t in cli tests
    • 6d42686 test: remove mocha syntax from tests
    • 4798b9d docs: update installation and usage for modules
    • Additional commits viewable in compare view

    Updates @vue/cli-plugin-babel from 4.5.12 to 5.0.8

    Release notes

    Sourced from @​vue/cli-plugin-babel's releases.

    v5.0.8

    :bug: Bug Fix

    v5.0.7

    • @vue/cli-service
    • @vue/cli-ui
      • #7210 chore: upgrade to apollo-server-express 3.x

    Committers: 2

    v5.0.6

    Fix compatibility with the upcoming Vue 2.7 (currently in alpha) and Vue Loader 15.10 (currently in beta).

    In Vue 2.7, vue-template-compiler is no longer a required peer dependency. Rather, there's a new export under the main package as vue/compiler-sfc.

    v5.0.5

    :bug: Bug Fix

    • @vue/cli
      • #7167 fix(upgrade): prevent changing the structure of package.json file during upgrade (@​blzsaa)
    • @vue/cli-service
    • @vue/cli-plugin-e2e-cypress
      • [697bb44] fix: should correctly resolve cypress bin path for Cypress 10 (Note that the project is still created with Cypress 9 by default, but you can upgrade to Cypress 10 on your own now)

    Committers: 3

    v5.0.4

    :bug: Bug Fix

    • @vue/cli-service
    • @vue/cli-shared-utils, @vue/cli-ui
      • 75826d6 fix: replace node-ipc with @achrinza/node-ipc to further secure the dependency chain

    Committers: 1

    v5.0.3

    ... (truncated)

    Changelog

    Sourced from @​vue/cli-plugin-babel's changelog.

    5.0.7 (2022-07-05)

    • @vue/cli-service
    • @vue/cli-ui
      • #7210 chore: upgrade to apollo-server-express 3.x

    Committers: 2

    5.0.6 (2022-06-16)

    Fix compatibility with the upcoming Vue 2.7 (currently in alpha) and Vue Loader 15.10 (currently in beta).

    In Vue 2.7, vue-template-compiler is no longer a required peer dependency. Rather, there's a new export under the main package as vue/compiler-sfc.

    5.0.5 (2022-06-16)

    :bug: Bug Fix

    • @vue/cli
      • #7167 feat(upgrade): prevent changing the structure of package.json file during upgrade (@​blzsaa)
    • @vue/cli-service

    Committers: 3

    5.0.4 (2022-03-22)

    :bug: Bug Fix

    • @vue/cli-service
    • @vue/cli-shared-utils, @vue/cli-ui
      • 75826d6 fix: replace node-ipc with @achrinza/node-ipc to further secure the dependency chain

    Committers: 1

    ... (truncated)

    Commits

    Updates @vue/cli-plugin-eslint from 4.5.12 to 5.0.8

    Release notes

    Sourced from @​vue/cli-plugin-eslint's releases.

    v5.0.8

    :bug: Bug Fix

    v5.0.7

    • @vue/cli-service
    • @vue/cli-ui
      • #7210 chore: upgrade to apollo-server-express 3.x

    Committers: 2

    v5.0.6

    Fix compatibility with the upcoming Vue 2.7 (currently in alpha) and Vue Loader 15.10 (currently in beta).

    In Vue 2.7, vue-template-compiler is no longer a required peer dependency. Rather, there's a new export under the main package as vue/compiler-sfc.

    v5.0.5

    :bug: Bug Fix

    • @vue/cli
      • #7167 fix(upgrade): prevent changing the structure of package.json file during upgrade (@​blzsaa)
    • @vue/cli-service
    • @vue/cli-plugin-e2e-cypress
      • [697bb44] fix: should correctly resolve cypress bin path for Cypress 10 (Note that the project is still created with Cypress 9 by default, but you can upgrade to Cypress 10 on your own now)

    Committers: 3

    v5.0.4

    :bug: Bug Fix

    • @vue/cli-service
    • @vue/cli-shared-utils, @vue/cli-ui
      • 75826d6 fix: replace node-ipc with @achrinza/node-ipc to further secure the dependency chain

    Committers: 1

    v5.0.3

    ... (truncated)

    Changelog

    Sourced from @​vue/cli-plugin-eslint's changelog.

    5.0.7 (2022-07-05)

    • @vue/cli-service
    • @vue/cli-ui
      • #7210 chore: upgrade to apollo-server-express 3.x

    Committers: 2

    5.0.6 (2022-06-16)

    Fix compatibility with the upcoming Vue 2.7 (currently in alpha) and Vue Loader 15.10 (currently in beta).

    In Vue 2.7, vue-template-compiler is no longer a required peer dependency. Rather, there's a new export under the main package as vue/compiler-sfc.

    5.0.5 (2022-06-16)

    :bug: Bug Fix

    • @vue/cli
      • #7167 feat(upgrade): prevent changing the structure of package.json file during upgrade (@​blzsaa)
    • @vue/cli-service

    Committers: 3

    5.0.4 (2022-03-22)

    :bug: Bug Fix

    • @vue/cli-service
    • @vue/cli-shared-utils, @vue/cli-ui
      • 75826d6 fix: replace node-ipc with @achrinza/node-ipc to further secure the dependency chain

    Committers: 1

    ... (truncated)

    Commits

    Updates @vue/cli-service from 4.5.12 to 5.0.8

    Release notes

    Sourced from @​vue/cli-service's releases.

    v5.0.8

    :bug: Bug Fix

    v5.0.7

    • @vue/cli-service
    • @vue/cli-ui
      • #7210 chore: upgrade to apollo-server-express 3.x

    Committers: 2

    v5.0.6

    Fix compatibility with the upcoming Vue 2.7 (currently in alpha) and Vue Loader 15.10 (currently in beta).

    In Vue 2.7, vue-template-compiler is no longer a required peer dependency. Rather, there's a new export under the main package as vue/compiler-sfc.

    v5.0.5

    :bug: Bug Fix

    • @vue/cli
      • #7167 fix(upgrade): prevent changing the structure of package.json file during upgrade (@​blzsaa)
    • @vue/cli-service
    • @vue/cli-plugin-e2e-cypress
      • [697bb44] fix: should correctly resolve cypress bin path for Cypress 10 (Note that the project is still created with Cypress 9 by default, but you can upgrade to Cypress 10 on your own now)

    Committers: 3

    v5.0.4

    :bug: Bug Fix

    • @vue/cli-service
    • @vue/cli-shared-utils, @vue/cli-ui
      • 75826d6 fix: replace node-ipc with @achrinza/node-ipc to further secure the dependency chain

    Committers: 1

    v5.0.3

    ... (truncated)

    Changelog

    Sourced from @​vue/cli-service's changelog.

    5.0.7 (2022-07-05)

    • @vue/cli-service
    • @vue/cli-ui
      • #7210 chore: upgrade to apollo-server-express 3.x

    Committers: 2

    5.0.6 (2022-06-16)

    Fix compatibility with the upcoming Vue 2.7 (currently in alpha) and Vue Loader 15.10 (currently in beta).

    In Vue 2.7, vue-template-compiler is no longer a required peer dependency. Rather, there's a new export under the main package as vue/compiler-sfc.

    5.0.5 (2022-06-16)

    :bug: Bug Fix

    • @vue/cli
      • #7167 feat(upgrade): prevent changing the structure of package.json file during upgrade (@​blzsaa)
    • @vue/cli-service

    Committers: 3

    5.0.4 (2022-03-22)

    :bug: Bug Fix

    • @vue/cli-service
    • @vue/cli-shared-utils, @vue/cli-ui
      • 75826d6 fix: replace node-ipc with @achrinza/node-ipc to further secure the dependency chain

    Committers: 1

    ... (truncated)

    Commits
    • b154dbd v5.0.8
    • 0260e4d fix: add devServer.server.type to useHttps judgement (#7222)
    • 4a0655f v5.0.7
    • beffe8a fix: allow disabling progress plugin via devServer.client.progress
    • 558dea2 fix: support devServer.server option, avoid deprecation warning
    • bddd64d fix: optimize the judgment on whether HTTPS has been set in options (#7202)
    • ef08a08 v5.0.6
    • fcf27e3 fixup! fix: compatibility with Vue 2.7
    • a648958 fix: compatibility with Vue 2.7
    • 98c66c9 v5.0.5
    • Additional commits viewable in compare view

    Updates webpack from 4.46.0 to 5.75.0

    Release notes

    Sourced from webpack's releases.

    v5.75.0

    Bugfixes

    • experiments.* normalize to false when opt-out
    • avoid NaN%
    • show the correct error when using a conflicting chunk name in code
    • HMR code tests existance of window before trying to access it
    • fix eval-nosources-* actually exclude sources
    • fix race condition where no module is returned from processing module
    • fix position of standalong semicolon in runtime code

    Features

    • add support for @import to extenal CSS when using experimental CSS in node
    • add i64 support to the deprecated WASM implementation

    Developer Experience

    • expose EnableWasmLoadingPlugin
    • add more typings
    • generate getters instead of readonly properties in typings to allow overriding them

    v5.74.0

    Features

    • add resolve.extensionAlias option which allows to alias extensions
      • This is useful when you are forced to add the .js extension to imports when the file really has a .ts extension (typescript + "type": "module")
    • add support for ES2022 features like static blocks
    • add Tree Shaking support for ProvidePlugin

    Bugfixes

    • fix persistent cache when some build dependencies are on a different windows drive
    • make order of evaluation of side-effect-free modules deterministic between concatenated and non-concatenated modules
    • remove left-over from debugging in TLA/async modules runtime code
    • remove unneeded extra 1s timestamp offset during watching when files are actually untouched
      • This sometimes caused an additional second build which are not really needed
    • fix shareScope option for ModuleFederationPlugin
    • set "use-credentials" also for same origin scripts

    Performance

    • Improve memory usage and performance of aggregating needed files/directories for watching
      • This affects rebuild performance

    Extensibility

    • export HarmonyImportDependency for plugins

    v5.73.0

    ... (truncated)

    Commits

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
    • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
    • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
    • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

    You can disable automated security fix PRs for this repo from the Security Alerts page.

  • Show very long file name

    Show very long file name

    Description Hello, I feel like I'm missing something, but I can't find a way or option to show the full name of a file without clicking on rename, or opening it, which I find unfortunate.

    Expected behaviour Show full file name without opening it or trying to rename it

    What is happening instead? File name is truncated and hidden with three dots

    How to reproduce? Create a file with a very long name

    image

  • Is there any option to disable redirects (make them proper 404) if they do not reach baseurl

    Is there any option to disable redirects (make them proper 404) if they do not reach baseurl

    Is your feature request related to a problem? Please describe. I am trying to run --noauth option but I do not want for filebrowser to be easily accessible. Thus I can generate a guid and run filebrowser on this custom basepath. Private enough for me.

    Describe the solution you'd like Generally any option (flag or config setting) to not have the UI popping at root path(due to redirect) just make it 404 if user has not entered correct basepath.

  • 403 Forbidden

    403 Forbidden

    Description When I try to upload a file or folder or try to create a new folder then a pop appears on the bottom right corner saying 403 FORBIDDEN.

    Expected behaviour I expect that when I drag and drop a file or upload any file or folder than it should upload the file or folder to my server using filemanager.

    What is happening instead? A pop is appearing and saying 403 Forbidden and the file/folder not uploading.

    Capture Additional context I have attached a screenshot of the issue.

A database/file backup tool with web interfaces
A database/file backup tool with web interfaces

backup-x 带Web界面的数据库/文件备份增强工具。原理:执行自定义shell命令输出文件,增强备份功能。

Dec 26, 2022
Abstract File Storage

afs - abstract file storage Please refer to CHANGELOG.md if you encounter breaking changes. Motivation Introduction Usage Matchers Content modifiers S

Dec 30, 2022
a tool for handling file uploads simple

baraka a tool for handling file uploads for http servers makes it easier to make operations with files from the http request. Contents Install Simple

Nov 30, 2022
Bigfile -- a file transfer system that supports http, rpc and ftp protocol https://bigfile.site
Bigfile -- a file transfer system that supports http, rpc and ftp protocol   https://bigfile.site

Bigfile ———— a file transfer system that supports http, rpc and ftp protocol 简体中文 ∙ English Bigfile is a file transfer system, supports http, ftp and

Dec 31, 2022
Go file operations library chasing GNU APIs.
Go file operations library chasing GNU APIs.

flop flop aims to make copying files easier in Go, and is modeled after GNU cp. Most administrators and engineers interact with GNU utilities every da

Nov 10, 2022
Read csv file from go using tags

go-csv-tag Read csv file from Go using tags The project is in maintenance mode. It is kept compatible with changes in the Go ecosystem but no new feat

Nov 16, 2022
File system event notification library on steroids.

notify Filesystem event notification library on steroids. (under active development) Documentation godoc.org/github.com/rjeczalik/notify Installation

Dec 31, 2022
Pluggable, extensible virtual file system for Go

vfs Package vfs provides a pluggable, extensible, and opinionated set of file system functionality for Go across a number of file system types such as

Jan 3, 2023
An epoll(7)-based file-descriptor multiplexer.

poller Package poller is a file-descriptor multiplexer. Download: go get github.com/npat-efault/poller Package poller is a file-descriptor multiplexer

Sep 25, 2022
QueryCSV enables you to load CSV files and manipulate them using SQL queries then after you finish you can export the new values to a CSV file
QueryCSV enables you to load CSV files and manipulate them using SQL queries then after you finish you can export the new values to a CSV file

QueryCSV enable you to load CSV files and manipulate them using SQL queries then after you finish you can export the new values to CSV file

Dec 22, 2021
Goful is a CUI file manager written in Go.
Goful is a CUI file manager written in Go.

Goful Goful is a CUI file manager written in Go. Works on cross-platform such as gnome-terminal and cmd.exe. Displays multiple windows and workspaces.

Dec 28, 2022
Read a tar file contents using go1.16 io/fs abstraction
Read a tar file contents using go1.16 io/fs abstraction

go-tarfs Read a tar file contents using go1.16 io/fs abstraction Usage ⚠️ go-tarfs needs go>=1.16 Install: go get github.com/nlepage/go-tarfs Use: pac

Dec 1, 2022
Open Source Continuous File Synchronization
Open Source Continuous File Synchronization

Goals Syncthing is a continuous file synchronization program. It synchronizes files between two or more computers. We strive to fulfill the goals belo

Jan 9, 2023
Cross-platform file system notifications for Go.

File system notifications for Go fsnotify utilizes golang.org/x/sys rather than syscall from the standard library. Ensure you have the latest version

Jan 1, 2023
The best HTTP Static File Server, write with golang+vue
The best HTTP Static File Server, write with golang+vue

gohttpserver Goal: Make the best HTTP File Server. Features: Human-friendly UI, file uploading support, direct QR-code generation for Apple & Android

Dec 30, 2022
Dragonfly is an intelligent P2P based image and file distribution system.
Dragonfly is an intelligent P2P based image and file distribution system.

Dragonfly Note: The master branch may be in an unstable or even broken state during development. Please use releases instead of the master branch in o

Jan 9, 2023
Fast, dependency-free, small Go package to infer the binary file type based on the magic numbers signature

filetype Small and dependency free Go package to infer file and MIME type checking the magic numbers signature. For SVG file type checking, see go-is-

Jan 3, 2023
Plik is a scalable & friendly temporary file upload system ( wetransfer like ) in golang.

Want to chat with us ? Telegram channel : https://t.me/plik_root_gg Plik Plik is a scalable & friendly temporary file upload system ( wetransfer like

Jan 2, 2023
File system for GitHub
File system for GitHub

HUBFS · File System for GitHub HUBFS is a read-only file system for GitHub and Git. Git repositories and their contents are represented as regular dir

Dec 28, 2022