0.3.0-beta.9 perseus deploy Couldn't get render configuration!: StoreError... on startup
#63
Comments
|
Wow. First off, thank you for the detail, that's greatly appreciated! I'll begin investigating this shortly, because I'd be surprised if this isn't a bug. |
arctic-hen7
added
C-bug
|
Okay, I'm about 90% sure this is actually really simple: you need to be in |
|
This should be fixable with |
|
This seems to avoid the errors in the Dockerfile, so I'll release this as beta 11. |
|
Nice. Thank you for making a new beta release so quickly. I posted everything I could cause I'd have never figured out what causes the problem and I'm really glad you did! Now when deploying with docker, the only thing that was missing was setting the Dockerfile # get the base image
FROM rust:1.55-slim AS build
# install build dependencies
RUN apt update \
&& apt install -y --no-install-recommends lsb-release apt-transport-https \
git inotify-tools ca-certificates build-essential make gcc curl
# prepare root project dir
WORKDIR /app
# download the target for wasm
RUN rustup target add wasm32-unknown-unknown
# install wasm-pack
RUN cargo install wasm-pack
# retrieve the project dir
RUN curl https://codeload.github.com/arctic-hen7/perseus/tar.gz/main | tar -xz --strip=2 perseus-main/examples/basic
# go to src dir
WORKDIR /app/basic
# remove perseus from repo
RUN rm -rf .perseus/
# install perseus-cli
RUN cargo install perseus-cli --version 0.3.0-beta.11
# adjust perseus version
RUN sed -i s'/perseus = .*/perseus = "0.3.0-beta.11"/' ./Cargo.toml
# deploy app
RUN perseus deploy
# prepare deployment image
FROM debian:bullseye-slim
WORKDIR /app
COPY --from=build /app/basic/pkg /app/
ENV PERSEUS_STANDALONE=true
ENV HOST=0.0.0.0
CMD ["/app/server"]Output of REPOSITORY TAG IMAGE ID CREATED SIZE
perseus-basic 2021-10-16 cdef870e7a10 32 seconds ago 91.8MB
<none> <none> d32992ff17eb 18 minutes ago 2.33GB
rust 1.55-slim 1ee58c5365b4 3 days ago 654MB
debian bullseye-slim dd984c2cf05c 4 days ago 80.4MBOnce I manage to add all the optimizations and deploy to a VPS, would you mind if I sent a PR documenting the docker deployment to production? Actually, I've got no idea where and how to start changing the docs, so, that should be interesting. |
|
My pleasure, glad I could help! Ah, I observed that too, but I thought it might be my firewall (which really hates Docker with a passion). Please go ahead, that'd be great! I'll update the contributing page for adding to the docs, because I don't think there's actually anything about doing so yet... |
|
Okay, the contributing docs have been updated, and there's a new Bonnie script for working easily with the docs. Let me know in a discussion/issue (whatever's appropriate) if you have any problems. |
|
Great. Thanks for the congributing page update. I'll see if I can understand any of that. While trying to add |
This fixes a regression from the original fix for #63.
Describe the bug
Once perseus app is deployed using
perseus deployand the standaloneserverbinary inpkg/dir is executed perseus app throws an error. Bellow is the whole procedure leveraging docker, including outputs from when I ran all of the commands necessary to reproduce the error.To Reproduce
Expected behavior
No error and the web app served at http://localhost:8080/
Environment (please complete the following information):
Additional context
Note that the
Dockerfileas shown above is created using multilinecatcommand ending withEOLon it's own line, simply for posterity reasons. Creation of theDockerfiledoesn't need to be done this way.Note that the
FROM rust:1.55-slimcall is used twice in theDockerfileas this shows a two stage image build process producing two docker images.Finally note that the
Dockerfiledownloads thebasicexample withcurlfrom this repo automatically, which makes it standalone.The text was updated successfully, but these errors were encountered: