How to Deploy front-end

[chenyong0923]

Building a new image from the official Dockerfile creates a back-end service, right? Does the front-end service need to be deployed separately? When accessing the container's port through a browser, it keeps loading.

[chenyong0923]

When deploying to the production environment, you would first package the image, then deploy the backend, and then deploy the frontend via nginx, right?

[LinkinStars]

@chenyong0923 First of all, for the whole project, the frontend doesn't need to be deployed separately. Just compile the frontend and then the backend, and finally package it into a docker image to start. Then just use the nginx proxy you mentioned to access the port of the container.

[chenyong0923]

@chenyong0923 First of all, for the whole project, the frontend doesn't need to be deployed separately. Just compile the frontend and then the backend, and finally package it into a docker image to start. Then just use the nginx proxy you mentioned to access the port of the container.

Now the mirrored boot has started, and the browser is trying to access the boot port, but it is not able to enter the install page normally. Why is that?

[LinkinStars]

@chenyong0923 If you are rebuilding the image, could you give the command and dockerfile that you built it with? If there are any other modifications please include them as well.

[chenyong0923]

@chenyong0923 If you are rebuilding the image, could you give the command and dockerfile that you built it with? If there are any other modifications please include them as well.

I just supported uploading videos, changed the local storage of images and videos to OSS, and kept the Dockerfile the same as the official one.

# Licensed to the Apache Software Foundation (ASF) under one
# or more contributor license agreements.  See the NOTICE file
# distributed with this work for additional information
# regarding copyright ownership.  The ASF licenses this file
# to you under the Apache License, Version 2.0 (the
# "License"); you may not use this file except in compliance
# with the License.  You may obtain a copy of the License at
#
#   http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing,
# software distributed under the License is distributed on an
# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
# KIND, either express or implied.  See the License for the
# specific language governing permissions and limitations
# under the License.

FROM golang:1.22-alpine AS golang-builder
LABEL maintainer="linkinstar@apache.org"

ARG GOPROXY
# ENV GOPROXY ${GOPROXY:-direct}
# ENV GOPROXY=https://proxy.golang.com.cn,direct
ENV GOPROXY=https://goproxy.cn,direct

ENV GOPATH /go
ENV GOROOT /usr/local/go
ENV PACKAGE github.com/apache/incubator-answer
ENV BUILD_DIR ${GOPATH}/src/${PACKAGE}
ENV ANSWER_MODULE ${BUILD_DIR}

ARG TAGS="sqlite sqlite_unlock_notify"
ENV TAGS "bindata timetzdata $TAGS"
ARG CGO_EXTRA_CFLAGS

COPY . ${BUILD_DIR}
WORKDIR ${BUILD_DIR}
RUN apk --no-cache add build-base git bash nodejs npm && npm install -g pnpm@8.9.2 \
    && make clean build

RUN chmod 755 answer
RUN ["/bin/bash","-c","script/build_plugin.sh"]
RUN cp answer /usr/bin/answer

RUN mkdir -p /data/uploads && chmod 777 /data/uploads \
    && mkdir -p /data/i18n && cp -r i18n/*.yaml /data/i18n

FROM alpine
LABEL maintainer="linkinstar@apache.org"

ARG TIMEZONE
ENV TIMEZONE=${TIMEZONE:-"Asia/Shanghai"}

RUN apk update \
    && apk --no-cache add \
        bash \
        ca-certificates \
        curl \
        dumb-init \
        gettext \
        openssh \
        sqlite \
        gnupg \
        tzdata \
    && ln -sf /usr/share/zoneinfo/${TIMEZONE} /etc/localtime \
    && echo "${TIMEZONE}" > /etc/timezone

COPY --from=golang-builder /usr/bin/answer /usr/bin/answer
COPY --from=golang-builder /data /data
COPY /script/entrypoint.sh /entrypoint.sh
RUN chmod 755 /entrypoint.sh

VOLUME /data
EXPOSE 80
ENTRYPOINT ["/entrypoint.sh"]

[sosyz]

@chenyong0923 Maybe you can use storage-aliyunoss if you want to save files on OSS ?

[chenyong0923]

@chenyong0923 Maybe you can use storage-aliyunoss if you want to save files on OSS ?

Thanks，I mainly want to upload videos, does this plugin support video uploads? Or is it only for storing images on Oss? I have already implemented the local function, but the problem is that the rebuilt image service keeps loading.

[LinkinStars]

@chenyong0923 If you haven't modified the dockerfile, then maybe the build should have a problem. First, you can try to build the frontend locally by make ui command. If there is no problem, then keep the output log when executing the docker build command to see if there are any error messages during the frontend build process.

[chenyong0923]

@chenyong0923 If you haven't modified the dockerfile, then maybe the build should have a problem. First, you can try to build the frontend locally by make ui command. If there is no problem, then keep the output log when executing the docker build command to see if there are any error messages during the frontend build process.

I am currently doing it like this: first, I build the front-end make ui, then the back-end make build, both of which are working fine. Finally, I build the image.

[LinkinStars]

@chenyong0923 OK. Then it's very likely that there's a problem with the docker image build process.

[chenyong0923]

@chenyong0923 OK. Then it's very likely that there's a problem with the docker image build process.

Sometimes building an image may result in errors due to installation dependency issues, but even if an image is successfully built, there may still be issues.

[LinkinStars]

@chenyong0923 Well, it looks like a network issue. 🤔

[chenyong0923]

@chenyong0923 Well, it looks like a network issue. 🤔

Yes, just keep trying, and you'll be able to build it successfully. However, when I build a successful image, the browser keeps loading the page, and this has been bothering me for a long time. I don't know what the cause is. Even when I build an image using the official main branch code, it also keeps loading.

[LinkinStars]

Even when I build an image using the official main branch code, it also keeps loading.

@chenyong0923 That's kind of weird. But you can try using the official image first. docker pull apache/answer:latest. If there is no problem, then there must be something wrong with the docker build process. Because the official image is built from the dockerfile in the code repository. The whole process is built using GitHub action with no human intervention.

[chenyong0923]

Even when I build an image using the official main branch code, it also keeps loading.

@chenyong0923 That's kind of weird. But you can try using the official image first. docker pull apache/answer:latest. If there is no problem, then there must be something wrong with the docker build process. Because the official image is built from the dockerfile in the code repository. The whole process is built using GitHub action with no human intervention.

It's normal to pull the official image directly from the Docker Hub, and cloning the official source code and building the image also results in a loading status. I will try it on another computer.

[chenyong0923]

Even when I build an image using the official main branch code, it also keeps loading.

@chenyong0923 That's kind of weird. But you can try using the official image first. docker pull apache/answer:latest. If there is no problem, then there must be something wrong with the docker build process. Because the official image is built from the dockerfile in the code repository. The whole process is built using GitHub action with no human intervention.

When will the official mirror image support the last video? This is a necessary requirement, so I have made a secondary development.

[chenyong0923]

Even when I build an image using the official main branch code, it also keeps loading.

@chenyong0923 That's kind of weird. But you can try using the official image first. docker pull apache/answer:latest. If there is no problem, then there must be something wrong with the docker build process. Because the official image is built from the dockerfile in the code repository. The whole process is built using GitHub action with no human intervention.

I found the problem, start the plug-in, the front-end route is lost, get the plug-in state, return undefined, need to add a backstory logic，return undefined, assign an empty array

[shuashuai]

I found the problem, start the plug-in, the front-end route is lost, get the plug-in state, return undefined, need to add a backstory logic，return undefined, assign an empty array

@chenyong0923

I tested it, and it is indeed like this. It should be related to the adjustment of the routing logic of the last load of the socket. The number of interfaces allowed to be accessed when ignoring /install is limited, so there is a problem here during initialization. I will fix it, thanks for the feedback.