35 lines
1.8 KiB
Markdown
35 lines
1.8 KiB
Markdown
# Ente Cloudron – Quick Guide
|
||
|
||
## Build
|
||
```bash
|
||
git clone https://github.com/andreasdueren/ente-cloudron.git
|
||
cd ente-cloudron
|
||
|
||
cloudron build \
|
||
--set-build-service builder.docker.due.ren \
|
||
--build-service-token e3265de06b1d0e7bb38400539012a8433a74c2c96a17955e \
|
||
--set-repository andreasdueren/ente-cloudron \
|
||
--tag 0.5.3
|
||
```
|
||
|
||
## Install
|
||
```bash
|
||
cloudron install \
|
||
--location ente.due.ren \
|
||
--image andreasdueren/ente-cloudron:0.5.3
|
||
```
|
||
|
||
## After Install
|
||
1. **S3** – In Cloudron File Manager open `/app/data/config/s3.env`, fill in your endpoint/region/bucket/access/secret, then restart the app from the dashboard. Optional replication: add `S3_SECONDARY_ENDPOINT`, `S3_SECONDARY_ACCESS_KEY`, `S3_SECONDARY_SECRET_KEY`, and `S3_SECONDARY_DC` (plus overrides for region/bucket/prefix) to mirror uploads to a second provider. See Ente’s [object storage guide](https://ente.io/help/self-hosting/administration/object-storage).
|
||
2. **Secondary hostnames** – During installation Cloudron now prompts for hostnames for the Accounts/Auth/Cast/Albums/Family web apps (powered by `httpPorts`). Ensure matching DNS records exist that point to the primary app domain. If you use Cloudron-managed DNS, those records are created automatically; otherwise create CNAME/A records such as `accounts.<app-domain> → <app-domain>`.
|
||
|
||
Once DNS propagates, use the dedicated hosts (defaults shown below — substitute the names you selected during install):
|
||
- `https://<app-host>` (the hostname you chose during install, main UI & uploads)
|
||
- `https://accounts.<app-domain>`
|
||
- `https://auth.<app-domain>`
|
||
- `https://cast.<app-domain>`
|
||
- `https://albums.<app-domain>`
|
||
- `https://family.<app-domain>`
|
||
|
||
Check `cloudron logs --app ente.due.ren -f` or `/app/data/logs/startup.log` if anything looks off.
|