Replies: 2 comments 6 replies
-
I agree. I'd love to get more familiar with Github Actions (or similar) and have actions that automatically build and deploy packages and containers.
GHCR free plan has a 500MB limit. I feel like we would reach the 500MB relatively fast.
The 100 pulls limit on the other hand seems very high. (How often do you deploy a new version of CTFNote ?)
If you are low on memory, here is how I compile the front for my server : diff --git a/front/Dockerfile b/front/Dockerfile
index 4c35f732..19911867 100644
--- a/front/Dockerfile
+++ b/front/Dockerfile
@@ -11,6 +11,10 @@ WORKDIR /usr/src/app
RUN yarn build
+# _--------_
+FROM scratch AS export
+COPY --from=build-deps /usr/src/app/dist/spa /
+
# _--------_
FROM nginx@sha256:5ba534070ae1e5e83d52141b11ddced689b476c0001e7205f50979dc0cbdde3d Then I compile with Questions:
|
Beta Was this translation helpful? Give feedback.
-
For some time we already provide images through GHCR which works solid, so we can close this discussion. |
Beta Was this translation helpful? Give feedback.
-
I get quite often the comment that CTFNote requires a large amount of memory to host (see also #126). This is also my own experience, since it requires around 2-3 GB RAM to build the frontend. However, afterward the building of especially the frontend, CTFNote requires much less RAM to run.
I think it would be nice to provide prebuilt docker images hosted via Github Container Registry or a similar service (which one?). This way, you can bypass the building and host CTFNote even on a 2 GB RAM VPS.
quay.io
However, I think we should not drop the manual build procedure since it may be preferred to not trust the prebuilt images and an easy alternative should be provided. But we may change the default docker-compose.yml file to use the prebuilt images.
Would this be supported by the CTFNote maintainers?
Beta Was this translation helpful? Give feedback.
All reactions