Ente
-
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.
wrote 23 days ago last edited by@andreasdueren caddy is great, it just doesn't need certs once packaged.
-
@andreasdueren caddy is great, it just doesn't need certs once packaged.
wrote 23 days ago last edited by@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
-
@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
wrote 23 days ago last edited by@andreasdueren I feel you.
I had similar issues trying to plumb ZeroNet.
-
wrote 23 days ago last edited by
Actually, here they are using Caddy?! -.-
-
Actually, here they are using Caddy?! -.-
wrote 23 days ago last edited by@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.
wrote 23 days ago last edited by@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.
-
wrote 23 days ago last edited by robi 23 days ago
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.
-
wrote 23 days ago last edited by
Great job guys, can't wait to use it on Cloudron
️ -
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.
wrote 23 days ago last edited by@robi Yes, I think this is not far from running. Don't have time to work on it today unfortunately
-
wrote 6 days ago last edited by
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.wrote 5 days ago last edited by -
wrote 4 days ago last edited by
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.
