Replies: 9 comments 35 replies
-
|
Thanks for the suggestion.
It is not inappropriate to include it in the code, however, we don't yet want to pre-commit to a particular way of using the web app with Docker. This is because
So for now, I'm not fully sure if we want to add this Dockerfile to the web code. Maybe this is the correct approach, but still want to mull a bit more over this before adding something (and then later trying to take it out).
Feel free! That is maybe the best option now, it can help other people too. You can add your guide in a new file under https://github.com/ente-io/ente/tree/main/docs/docs/self-hosting/guides (+add an entry in sidebar.ts), and once published it'll appear in https://help.ente.io/self-hosting/guides/.
rather, thank you 😊 |
Beta Was this translation helpful? Give feedback.
-
|
Great, I'll write a document when I have time! I hope you'll take your time thinking about dockerising your web app :) |
Beta Was this translation helpful? Give feedback.
-
|
My 2 cents, the vast majority of people enclined to self-host the whole ente stack, server and webapps, would probably be interested only in photos and auth - indeed not the whole enchilada. Even if this is more trivial than the server, having official images, built and pushed to a container repo, would make it easier to spawn a docker-compose stack, maintain and update it. Plus it's not unusual as a selfhoster for things to break a little upon updates - if you start off with a solution for the webapp docker image, and then update the docker image, env variables, port mappings etc, because you find a way more aligned with your goals, it's my responsibility to adapt in order to update or stick to an earlier of my working stack. |
Beta Was this translation helpful? Give feedback.
-
|
This does not seem to work for me, the build exits with an error: Any hints? |
Beta Was this translation helpful? Give feedback.
-
|
Looks like the failures are only happening with Podman |
Beta Was this translation helpful? Give feedback.
-
|
Oh, sorry. I don't have the time to devote to ente right now, so I won't be able to check it. I think you can try to verify that the web application was buildable in the local system, not in a podman. |
Beta Was this translation helpful? Give feedback.
-
|
I built using Docker and that worked fine. I then pushed the built image to a local registry and used that to start the container with Podman. This must be a podman bug. |
Beta Was this translation helpful? Give feedback.
-
|
Glad to hear it worked out for you. Thanks for sharing. :) |
Beta Was this translation helpful? Give feedback.
-
|
server-minio-3v.-1z server-minio-provision- e95h 0 igit JH i Ugommm ujmuoohhhh9g0o5o9server-minio-prommmvision-1 RDllllprovision-vb0o1server-min.m exclu c👁️🗨️io-provi. B99@pop 0 9 |
Beta Was this translation helpful? Give feedback.
-
|
I liked this Dockerfile and wanted to make it so it automatically updated itself from the git repo. This is what I came up with, hopefully others find it useful: Dockerfile FROM node:20-alpine
RUN apk add --no-cache git
WORKDIR /app
RUN npm install -g serve
COPY entrypoint.sh /entrypoint.sh
RUN chmod +x /entrypoint.sh
ENTRYPOINT ["/entrypoint.sh"]
CMD ["serve", "-s", "/data/ente/web/apps/photos/out", "-l", "tcp://0.0.0.0:3000"]
EXPOSE 3000entrypoint.sh #!/bin/sh
# Exit on any error
set -e
# Clone the repository
if [ ! -d "/data/ente/.git" ]; then
git clone https://github.com/ente-io/ente.git /data/ente
cd /data/ente/web
git submodule update --init --recursive
else
cd /data/ente
git pull
cd /data/ente/web
git submodule update --recursive
fi
# Install dependencies
yarn install
# Build the application
if [ -d "/data/ente/web/apps/photos/out" ]; then
echo "Removing previous build directory."
rm -rf /data/ente/web/apps/photos/out
fi
yarn build:photos
# Execute the command provided as arguments to the entrypoint (if any)
exec "$@"compose.yml services:
app:
container_name: ente-photos
environment:
NEXT_PUBLIC_ENTE_ENDPOINT: "https://foo.bar"
NEXT_PUBLIC_ALBUMS_ENDPOINT: "https://foo.bar"
build: .
volumes:
- ./data:/data
ports:
- "3000:3000"
restart: always |
Beta Was this translation helpful? Give feedback.
-
|
update: everything works now, simple solution, just need to reverse proxy everything instead of just web and the server. |
Beta Was this translation helpful? Give feedback.
-
Are you able to share your working config? I've been trying for a couple of days to get this working behind Traefik without luck. The UI and account creation works but upload is broken. |
Beta Was this translation helpful? Give feedback.
-
I have the server + s3 + web frontend setup working using docker / caprover. I'll try this weekend and maybe make a shell script to generate any necessary config files, docker files, etc. I know when I first started out I had my s3 and server behind cloudflare proxy which restricted the file upload size. I've since used caddy to provide a hacky waf (real reason I was using cloudflare to begin with) and everything works wonderfully. I gotta say, Ente is definitely #1 self hosted piece of software in my stack. |
Beta Was this translation helpful? Give feedback.
-
You still need help? Can discord me at .nurish if you want and I can share the screen instead since I don't remember everything I did. |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
@plumber-craic @aqsede @LI-NA @adamlacombe I have spent the last 1.5 weeks trying to edit the dockerfile here - https://help.ente.io/self-hosting/guides/external-s3 to be able to include photos and accounts (for passkey) support and have been miserably unsuccessful. With the image generated from the current dockerfile when I choose passkey it routes me to account.ento.io instead of account.xxx.in. Please could one of you help me edit the dockerfile to include web/accounts or if there is already a dockerfile with you where passkey works ? Happy to ping you on discord/reddit etc but really trying to get this straightned out. Here is the dockerfile that I edited with help from chatgpt (sorry i'm no developer) but all I reach on port 8082, 8083 is the nginx welcome page |
Beta Was this translation helpful? Give feedback.
-
Sorry, I don't enable passkey, so my config doesn't have any difference. My understanding there it require extra auth service to be enabled outside of ente. |
Beta Was this translation helpful? Give feedback.
-
|
The docker file you attached doesn't seem to be listening to anything on ports 8082, 8083. If I were you, I'd create the following two docker files and expose each to a port instead of having nginx inside. (Although it will take a long time to build...) # For Photo
FROM node:21-alpine as builder
WORKDIR /app
COPY . .
ARG NEXT_PUBLIC_ENTE_ENDPOINT=http://localhost:8080
ENV NEXT_PUBLIC_ENTE_ENDPOINT=${NEXT_PUBLIC_ENTE_ENDPOINT}
ARG NEXT_PUBLIC_ENTE_ACCOUNTS_URL=http://localhost:8081
ENV NEXT_PUBLIC_ENTE_ACCOUNTS_URL=${NEXT_PUBLIC_ENTE_ACCOUNTS_URL}
RUN yarn install && yarn build
FROM node:21-alpine
WORKDIR /app
COPY --from=builder /app/apps/photos/out .
RUN npm install -g serve
ENV PORT=3000
EXPOSE ${PORT}
CMD serve -s . -l tcp://0.0.0.0:${PORT}# For Account
FROM node:21-alpine as builder
WORKDIR /app
COPY . .
ARG NEXT_PUBLIC_ENTE_ENDPOINT=http://localhost:8080
ENV NEXT_PUBLIC_ENTE_ENDPOINT=${NEXT_PUBLIC_ENTE_ENDPOINT}
ARG NEXT_PUBLIC_ENTE_ACCOUNTS_URL=http://localhost:8081
ENV NEXT_PUBLIC_ENTE_ACCOUNTS_URL=${NEXT_PUBLIC_ENTE_ACCOUNTS_URL}
RUN yarn install && yarn build
FROM node:21-alpine
WORKDIR /app
COPY --from=builder /app/apps/accounts/out .
RUN npm install -g serve
ENV PORT=3000
EXPOSE ${PORT}
CMD serve -s . -l tcp://0.0.0.0:${PORT}Importantly, you must specify 'NEXT_PUBLIC_ENTE_ENDPOINT' and 'NEXT_PUBLIC_ENTE_ACCOUNTS_URL' when you build the dockerfile. See the sample compose file below. services:
photo:
build:
context: ./ente/web
dockerfile: ../../photo.Dockerfile
network: host
args:
NEXT_PUBLIC_ENTE_ENDPOINT: https://your_museum_endpoint
NEXT_PUBLIC_ENTE_ACCOUNTS_URL: https://your_account_domain
container_name: ente-photo
restart: on-failure:3
# Your photo expose port:3000
ports:
- 8080:3000
networks:
- net
account:
build:
context: ./ente/web
dockerfile: ../../account.Dockerfile
network: host
args:
NEXT_PUBLIC_ENTE_ENDPOINT: https://your_museum_endpoint
NEXT_PUBLIC_ENTE_ACCOUNTS_URL: https://your_account_domain
container_name: ente-account
restart: on-failure:3
# Your account expose port:3000
ports:
- 8081:3000
networks:
- net
networks:
net:Actually, I don't have the time right now, so I've shown you the method I used in the past... It's definitely possible to run both apps in one container with nginx inside... and save a little bit more memory. For reference, I'm putting it all together in a compose file running Museum and managing it as a single compose project. |
Beta Was this translation helpful? Give feedback.
-
|
Hi, node noob here that only read documentation and didn't try at all to run this yet, can I ask a technical detail on your Dockerfile? If I understood right, once built with Is |
Beta Was this translation helpful? Give feedback.
-
|
You're right, The reason I chose the |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, I thought that it needed node for calling some server function. It's definitely simpler in this way; traffic would be almost zero in my case, so it's ok |
Beta Was this translation helpful? Give feedback.
-
|
@LI-NA I have provided below changes that were made that seems incorrect. Let me know if I have made a mistake? Are you able to help how the dockerfile can be changed to include everything during the build process itself? and not when the containers start. For older systems it take a long wait time (~30 mins) for containers to spin up the first time. Any other thoughts?? # For Photo
FROM node:21-alpine as builder
WORKDIR /app
COPY . .
ARG NEXT_PUBLIC_ENTE_ENDPOINT=http://localhost:8080
ENV NEXT_PUBLIC_ENTE_ENDPOINT=${NEXT_PUBLIC_ENTE_ENDPOINT}
ARG NEXT_PUBLIC_ENTE_ALBUMS_ENDPOINT=http://localhost:8081 #changed to ALBUMBS_ENDPOINT
ENV NEXT_PUBLIC_ENTE_ALBUMS_ENDPOINT=${NEXT_PUBLIC_ENTE_ALBUMS_ENDPOINT} #changed to ALBUMBS_ENDPOINT
RUN yarn install && yarn build
FROM node:21-alpine
WORKDIR /app
COPY --from=builder /app/apps/photos/out .
RUN npm install -g serve
ENV PORT_PHOTOS=3000 #PORT FOR ENTE WEB TO WORK
EXPOSE ${PORT_PHOTOS}
ENV PORT_ALBUMS=3002 #PORT FOR ALBUM SHARING
EXPOSE ${PORT_ALBUMS}
CMD ["sh", "-c", "serve -s /data/ente/web/apps/photos/out -l tcp://0.0.0.0:${PORT_PHOTOS} & serve -s /data/ente/web/apps/photos/out -l tcp://0.0.0.0:${PORT_ALBUMS} & wait"] #EXPOSE BOTH PORTS# For Account
FROM node:21-alpine as builder
WORKDIR /app
COPY . .
ARG NEXT_PUBLIC_ENTE_ENDPOINT=http://localhost:8080
ENV NEXT_PUBLIC_ENTE_ENDPOINT=${NEXT_PUBLIC_ENTE_ENDPOINT}
ARG NEXT_PUBLIC_ENTE_ACCOUNTS_URL=http://localhost:3031
ENV NEXT_PUBLIC_ENTE_ACCOUNTS_URL=${NEXT_PUBLIC_ENTE_ACCOUNTS_URL}
RUN yarn install && yarn build
FROM node:21-alpine
WORKDIR /app
COPY --from=builder /app/apps/accounts/out .
RUN npm install -g serve
ENV PORT=3001
EXPOSE ${PORT}
CMD serve -s . -l tcp://0.0.0.0:${PORT}services:
photo:
build:
context: ./ente/web
dockerfile: ../../photo.Dockerfile
network: host
args:
NEXT_PUBLIC_ENTE_ENDPOINT: https://your_museum_endpoint
NEXT_PUBLIC_ENTE_ALBUMS_ENDPOINT: https://your_account_domain #This was changed to reflect albums endpoint
container_name: ente-photo
restart: on-failure:3
# Your photo expose port:3000
ports:
- 3000:3000 #WEB
- 3002:3002 #ALBUM SHARING
networks:
- net
account:
build:
context: ./ente/web
dockerfile: ../../account.Dockerfile
network: host
args:
NEXT_PUBLIC_ENTE_ENDPOINT: https://your_museum_endpoint
NEXT_PUBLIC_ENTE_ACCOUNTS_URL: https://your_account_domain
container_name: ente-account
restart: on-failure:3
# Your account expose port:3001
ports:
- 3001:3001
networks:
- net
networks:
net: |
Beta Was this translation helpful? Give feedback.
-
|
@vicky-bs You don't need 2 serve commands in your Photos Dockerfile as both photos and albums are being served from the same directory. You just need to pass -l twice (See my Dockerfile) @LI-NA You can use one Dockerfile for multiple apps without nginx as well. Here is what I have for Photos, Albums and the Auth apps. |
Beta Was this translation helpful? Give feedback.
-
|
The -s rewrites all not-found requests to \index.html
I don't know why accounts is like this. This is not really my area of expertise. "Luckily" the desktop app (or the mobile apps) doesn't work with self-hosted passkeys as it automatically uses accounts.ente.io, so I was able to launch passkeys from there and then just modify the url to point to my accounts page and delete the passkey. |
Beta Was this translation helpful? Give feedback.
-
|
I've never actually hosted accounts before, so I didn't realize it was an issue. In most cases, single-page applications built with static web require the -s option because index.html is supposed to handle all requests, so I figured accounts would need it as well. Anyway, I checked the documentation in web/accounts and it looks like it needs to be set up in the museum - have you checked this out? I'm not quite sure what that means yet. webauthn:
rpid: "localhost"
rporigins:
- "http://localhost:3001"https://github.com/ente-io/ente/tree/main/web/apps/accounts#development |
Beta Was this translation helpful? Give feedback.
-
|
@LI-NA yes this is included in museum.yaml. The passkey gets registered on https://accounts.example.com but when logged out and log back in. It doesn't seem to accept the passkey saved on 1password. It routes back to https://ente.example.com/credentials so technically required for the password to be entered again. It goes on an on after that |
Beta Was this translation helpful? Give feedback.
-
|
@ekadin-mtc any luck?? |
Beta Was this translation helpful? Give feedback.
-
|
@vicky-bs Yes! I just posted on Discord. @LI-NA All the apps need to be served without the |
Beta Was this translation helpful? Give feedback.
-
|
Ente web can also be run as a super simple systemd-service if you don't want to get into the mess of setting up a separate dockerfile. I'll mostly add this to the docs after talking with the devs, but till then here's the systemd-service which is working fine for me. [Unit]
Description=Run Ente Web as a service
[Service]
Type=simple
Restart=always
WorkingDirectory=/home/mangesh/dev/ente/web
Environment=NEXT_PUBLIC_ENTE_ENDPOINT=http://localhost:8000
ExecStart=/usr/bin/yarn dev
[Install]
WantedBy=multi-user.targetPut the above contents into a separate file under
|
Beta Was this translation helpful? Give feedback.
-
|
hello all. very confusion regarding the album,ente and accounts URL |
Beta Was this translation helpful? Give feedback.
-
|
Domains, yes |
Beta Was this translation helpful? Give feedback.
-
|
im trying with tailscale. lets see what happen |
Beta Was this translation helpful? Give feedback.
-
|
but I need hits what all I need to change to make it work. Im ready for testing |
Beta Was this translation helpful? Give feedback.
-
Did not understand what you meant to say here. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi there.
Recently ente became open source and I'm looking for a way to deploy all ente apps at once using docker-compose.
I've written the following code and am using it to deploy the web version with docker as well.
(This dockerfile is for photo.)
How about adding a dockerfile like this to the web folder and making it easier for many users to use the web in docker-compose?
If you think it's inappropriate to include it in the code, I'll write documentation about it so people can build web manually.
Thank you for taking the time to read my discussion.
Beta Was this translation helpful? Give feedback.
All reactions