Ente
-
I bet at some point we save more time as Cloudron users by packaging apps ourselves and documenting the process, maybe improving it via LLM, than waiting for the roadmap
-
Would like to see it on Cloudron : I use it on my own and got very familiar with it. thumps up
-
Currently attempting to package this. Frontend and backend are loading but not connecting to each other yet. Will have to investigate when I have a little time.
-
Currently attempting to package this. Frontend and backend are loading but not connecting to each other yet. Will have to investigate when I have a little time.
@andreasdueren feel free to post it in case someone else can contribute a bit that gets passed this point.
-
@andreasdueren feel free to post it in case someone else can contribute a bit that gets passed this point.
@robi Sure: https://git.due.ren/andreas/ente-cloudron/
I had to remove my bucket first because I hardcoded my credentials for testing (I'm a lazy sunofabitch)
-
nvm I'm switching to nginx
-
Heads up: I used Caddy because It was easier for me to configure. But I'm happy to use another server if anyone has a preference.
@andreasdueren caddy is great, it just doesn't need certs once packaged.
-
@andreasdueren caddy is great, it just doesn't need certs once packaged.
-
@robi I know but I'm just not getting it to work and the documentation is for nginx so it's probably better to stick with the upstream project
-
-
Actually, here they are using Caddy?! -.-
@andreasdueren Indeed.
If it helps any, you can take a peek at the ZeroNet apache config, it works to take the host nginx proxy and proxy it again to the local running app (for testing in LAMP).
Not sure what you're running into otherwise.
-
@andreasdueren Indeed.
If it helps any, you can take a peek at the ZeroNet apache config, it works to take the host nginx proxy and proxy it again to the local running app (for testing in LAMP).
Not sure what you're running into otherwise.
@robi As far as I can tell, both backend and frontend are working fine. Frontend loads but there eis something wrong with the server implementation and it won't connect to the backend. Probably easy stuff but I need a break.
-
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.
️
