Ente CLI or Linux App
Stupid Question....
I have Ente installed on my VPS. I want my local headless Raspi-based NAS to make a backup of my unencrypted library. At the moment there is no ENTE software whatsoever on the Raspberry Pi.
To use ENTE CLI to do this, do I need to just download the appropriate build of the CLI and make it executable?
Is there a way to install the linux app on a headless version of Linux?
Do I need to install the Ente self-hosted instance on my Pi, in order to get it CLI to work?
,,
GitHub
tag:cli-v0 · Releases · ente-io/ente
🔒 End-to-end encrypted cloud for photos, videos and 2FA secrets. - ente-io/ente
ente
Ente - Download
Download Ente Photos - the encrypted photo storage app. Available on App Store, Play Store, F-Droid, macOS, Linux and Windows. Get started with 10GB free.
21 Replies
To use Ente CLI, download the appropriate build from https://github.com/ente-io/ente/releases?q=tag%3Acli-v0 and make it executable.
It is not clear from the documentation if the Linux app can be installed on a headless version of Linux.
To use Ente CLI, it is not clear from the documentation if you need to install the Ente self-hosted instance on your Pi.
-# If your issue is resolved, please use the /solved command to close this thread. If you'd like to ask me another question use /docsearch
GitHub
tag:cli-v0 · Releases · ente-io/ente
🔒 End-to-end encrypted cloud for photos, videos and 2FA secrets. - ente-io/ente
You need the EnteCLI tool and within its directory modify
config.yaml
I think "api" is enough for what you are planning.
You can then log into your photo-account using
You will be prompted to enter an export-path. That will be the path in which all your albums will be created as directories and containing the unencrypted media.
You then need to authenticate
after that you can run
That should create an unencrypted export of all your media.
Be aware: Pictures which are in multiple albums will be copied to each album directory.
EDIT: Unsure if this could be run on a schedule.
Thanks for writting this. I still need to use CLI, but decided to run it on the same server as my ENTE instance.
I will try it and repost back
Instead of running on the same server, it will be advisable to run it on your local machine (laptop, desktop) that you would use for accessing Ente Photos or Auth and use that for keeping an unencrypted backup of your data for recovery.
This 👍
Ah, so it is designed to be used remotely?
I havent even got to the backup part yet. I am trying to increase the user's filesize.
Yes.
Wouldn't make much sense to use on the same server (unless you just want to admin operations) since exporting in the remote server will not be reliable in case if you experience downtime in server, making disaster recovery harder.
I want to be able to do admin actions as well. is there a way I can do that on the server without installing CLI?
I just installed CLI on my mac (not my server) using brew. i will see what I can do
For anyone reading this in the future, if you use brew to install CLI on your mac, the install folder is ~/.ente/
The documentation is kinda vague
https://help.ente.io/self-hosting/administration/cli
if I am installing CLI on my local machine to reach out to a remote server, where do I put the config.yaml?
The documentation says to put it in the path set by
ENTE_CLI_CONFIG_DIR
Where would I define that?
I tried making it in ~/.ente with the following in it:
When I add the account the OTP are sent to me via the ente.io server, and it says the account isn't found. So I am pretty sure its not connecting to my serverEnte CLI for Self-hosted Instance - Self-hosting | Ente Help
Guide to configuring Ente CLI for Self Hosted Instance
We are working on revamping the documentation for CLI, thanks for pointing out.
ENTE_CLI_CONFIG_DIR is an environment variable, it is the directory where your config.yaml file, resides and has to be defined in your shell's rc file to avoid redefining it repeatedly if you wish to store you configuration in any other path apart from ~/.ente/config.yaml
Also please check the documentation again, your configuration should be as follows:
Once you do this, it should work and you can deal with OTTs from the server logs.
As per your suggestion, I installed ente cli on a local machine. My mac, and i installed CLI using brew
enteapi.mydomain.com is my museum URL. It leads to a reverse proxy that goes to mydomain.com:8080
I did export ENTE_CLI_CONFIG_DIR=/Users/myUserName/.ente/
Then I added config.yaml to ~/.ente on my mac, but i think it still reaching out to ente.io's server instead of mine
is there any way using cli to see what that variable is set to?
maybe somthing like ente admin showserverAssuming Museum and reverse proxy runs on same machine, and you have this config:
I think you should consider swapping mydomain.com:8080 for localhost:8080
There's currently no way to see the API endpoint that's set, (fwiw there's a config command in the codebase but it's dead code right now)
If you are just using ENTE_CLI_CONFIG_DIR to set ~/.ente, it's not needed, it's default.
The reverse proxy runs on the sever with ente.
I did try it by putting the mydomain:8080, but it still didn’t work.
Local host won’t work because I’m running cli on my MacBook, and ente is on my vps, that’s on a completely different network.
Im sure it’s the default, but it’s. it working. So it would be nice to make sure it’s set to it’s proper value. Hopefully in future versions
I am not talking about setting localhost in CLI, I am telling to reverse proxy https://enteapi.mydomain.com to http://localhost:8080 with the reverse proxy you're using.
And it should be http://mydomain:8080 or https://mydomain:8080 when setting the value in config.yaml if you wish to use that value, URI scheme is needed for the CLI to work properly
Oh, I understand.
My reverse proxy is set to the ip_address:8080; opposed to localhost:8080
it seems to work fine when using the web app, or the MacOS app. I can change it to local host and see if that makes a difference.
The config.yaml
api:
endpoint: https://enteapi.mydomain.com
I also tried it with http://<<my_ip>>:8080,
and http://<<my_domain>>:8080
is there a way to update the client? Like a command the docker build command?If it works on other clients, CLI should also work the same way.
Update the client as in? CLI? You can download the latest binary from GitHub releases.
And one advice that I can give is, it's better to stick with localhost unless and until there's a scenario where only IP address cuts it out.
No, I mean when I make a change to config.yaml, or an enviromantal var, do I need to enter a command so ente cli knows to update it?
with ente on my server, if i don't do docker compose build, none of the changes take place.
I switched my RP to localhost, and it made no differece unfortionaltly
No commands needed. You haven't still changed the config to
You're using
Without correct config, CLI will default to production URL. Please update it.
I have no idea how I missed that. I don’t know if the ‘typo’ was mentioned, but it’s working now! Thanks
-# If your issue is resolved, you can use the /solved command to close the thread. If not, use /unsolve to cancel.
Thread marked as solved. It will be closed in <t:1755478178:R>.
This thread is now closed.
It's mentioned in the documentation, no worries, happy self-hosting!