Answers to frequently asked questions.

Warning about next-auth version

After npm install or npm ci you can have this warn :

npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'next-auth@4.14.0',
npm WARN EBADENGINE   required: { node: '^12.19.0 || ^14.15.0 || ^16.13.0' },
npm WARN EBADENGINE   current: { node: 'v18.12.1', npm: '8.19.2' }

The version required by next-auth is 18.12. In any case, the NodeJS version doesn’t really matter for the next-auth library and you can ignore this warning or upgrade your NodeJS.

Change default hostname or port for application

By default the application starts a server on and your application will therefore be accessible on any IP available on your host at port 3000.

If you want to make your application accessible only on localhost:3000 (for use with a proxy for example), edit the package.json file and modify this line :

"start": "next start",

To :

"start": "next start -H localhost",

And, if you want to change the default port (for example 4000), you can change this line like this :

"start": "next start -H localhost -p 4000",

Thank you to Philipp Rintz for its contribution to the reflection on this issue.

Does BorgWarehouse have to be installed on the same server as borgbackup ?

Yes. I am not saying that it is impossible to run BorgWarehouse on a server that would run the shells on another. However, the application is now thought and designed to run on the server that will store the repositories and run the server part of borgbackup.

Thank you to Pierrick Brun for its contribution.

What is the NEXT_TELEMETRY_DISABLED environment variable ?

Next.JS is the amazing open-source web development framework used to build BorgWarehouse. Next.JS can collect completely anonymous telemetry regarding usage. This information is used to shape Next.js’ roadmap and prioritize features.

If you want to help Next.JS by sharing anonymous telemetry, remove this environment variable.

Full documentation about nextJS telemetry is here : https://nextjs.org/telemetry

Can I change the directory /var/borgwarehouse ?

Actually you can’t, I plan to review this, but not immediately. In the meantime you can of course use a symbolic link to place your data directory wherever you want.

Rebuild the repo.json file

If you lose the repo.json file, this script will help you to rebuild a new one. It reads the BorgWarehouse repository tree and generates a corresponding object. This script is only intended to be used in emergencies (data corruption, update problems…) and as a last resort to rebuild your repo.json file.

Of course, certain parameters cannot be recovered, such as comments, repository quota, name or aliases. You’ll have to re-configure this from the web interface, but most of the work is done with it.

This script should be used with the root user, as it is necessary to read authorized_keys files.

This script simply displays a valid JSON object on your screen. Copy its entire content into the config/repo.json file. There’s no need to restart or rebuild BorgWarehouse, as this can be done on the fly.

Contact the creator ?

You can contact me on borgwarehouse @ r4ven.fr