Ente
-
It looks like it's just using port 8080 for the front end App facing parts which is configurable in the clients, which then make more HTTP calls to localhost ports 3000-3004 for the backend.
In a LAMP scenario it's one change for the Apache config and the rest is just making the backend run and available.
-
It looks like it's just using port 8080 for the front end App facing parts which is configurable in the clients, which then make more HTTP calls to localhost ports 3000-3004 for the backend.
In a LAMP scenario it's one change for the Apache config and the rest is just making the backend run and available.
-
Ente Photos has reached v1 stable on 28 March: https://ente.io/blog/v1/
Looks very interesting. -
Ente Photos has reached v1 stable on 28 March: https://ente.io/blog/v1/
Looks very interesting. -
I just installed this using their instructions for self-hosting. Other than having trouble figuring out what the proper endpoint is (partly due to the need to manually setup a whole bunch of DNS entries for things like /albums, /photos which even after a few hours of fiddling, I couldn't get it), I opted to not use this:, I feel you all should know the real reason: the backend is Minio. Minio is terrific for organizing files which are accessed by software. If you are hoping to drop a folder of folder of folders of pics onto this, and then one day decide you want to use something else, all your pics will be "well organized" but in an arcane folder system which Minio uses. It will NOT be browsable-friendly. You will not be able to get your pics out in a timely and simple fashion. At least, this is what it looks like to me.
-
You could just use Ente export feature to do the exact thing that you are wishing for.
-
You could just use Ente export feature to do the exact thing that you are wishing for.
@jayonrails If you were replying to my concern, I can just see the Forum posts now: "Help, my Ente export isn't working on my library with 12867 images, and 1380 videos! It's supposed to work!"
Good luck and best wishes to whoever uses this, but I'm sticking with whatever lets me leave my media in their existing folders. Back in the day FileRun did this for free, but they now charge 99 EUR. I tried ResourceSpace but it also moves everything around to its own organization.
A life lived in fear is a life half-lived
-
@jayonrails If you were replying to my concern, I can just see the Forum posts now: "Help, my Ente export isn't working on my library with 12867 images, and 1380 videos! It's supposed to work!"
Good luck and best wishes to whoever uses this, but I'm sticking with whatever lets me leave my media in their existing folders. Back in the day FileRun did this for free, but they now charge 99 EUR. I tried ResourceSpace but it also moves everything around to its own organization.
-
@robi Actually, I'm still on the free version of Filerun. I've been using it for quite awhile. Once they moved to a paid version they removed the free one for download unless you already had it running. So, I'm good.
A life lived in fear is a life half-lived
-
@robi Actually, I'm still on the free version of Filerun. I've been using it for quite awhile. Once they moved to a paid version they removed the free one for download unless you already had it running. So, I'm good.
-
-
This link was in the latest newsletter of Ente: https://ente.io/blog/self-hosting-quickstart/
-
@robi Yes, I think this is not far from running. Don't have time to work on it today unfortunately
@andreasdueren said in Ente:
@robi Yes, I think this is not far from running. Don't have time to work on it today unfortunately
time to circle back?
-
@andreasdueren said in Ente:
@robi Yes, I think this is not far from running. Don't have time to work on it today unfortunately
time to circle back?
-
@robi no pressure, huh 🥸
@andreasdueren Hehe. just a gentle reminder of a previous completion attempt
-
Would love to see it soon in the Cloudron App Store!
-
Would love to see it soon in the Cloudron App Store!
-
@Nerdrelaxo same:)
Mobile App lot of faster than Immich, E2EE@sponch Yes me too, but I've been struggling with this packaging but also I'm a bit discouraged because I've packaged two apps now but I'm not sure if they'll make it to the app store at all. I udnerstand maintaining apps brings additional overhead but trying to get packages working is an investment I'm not sure I want to make if I don't know if it will actually make it to the store.
-
@sponch Yes me too, but I've been struggling with this packaging but also I'm a bit discouraged because I've packaged two apps now but I'm not sure if they'll make it to the app store at all. I udnerstand maintaining apps brings additional overhead but trying to get packages working is an investment I'm not sure I want to make if I don't know if it will actually make it to the store.
@andreasdueren this is a continuing issue, the need for easy deployment for custom apps via the App Store, if necessary as unsupported apps.
Big picture view : however hard they try, and even with a bigger team, [@]staff will never be able to keep up with the flow of new software and demand from users for X or Y or very niche Z.
But there are many users who need an AppStore UI/process to install custom apps., rather than manual build and install.
We already have "unstable" as a status.
It would help greatly if there was also "unsupported", requiring only a basic initial review and no ongoing official support or maintenance.
AppDev and less techie users could be more free to explore/extend without creating a burden for Cloudron ops.
️
? 
