docker-node
Hexo
docker-node | Hexo | |
---|---|---|
62 | 28 | |
8,069 | 38,492 | |
0.3% | 0.5% | |
8.3 | 8.2 | |
9 days ago | 4 days ago | |
Shell | TypeScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
docker-node
-
Standalone Next.js. When serverless is not an option
FROM node:16-alpine AS base FROM base AS deps # Check https://github.com/nodejs/docker-node/tree/b4117f9333da4138b03a546ec926ef50a31506c3#nodealpine to understand why libc6-compat might be needed. RUN apk add --no-cache libc6-compat WORKDIR /app COPY package.json package-lock.json* ./ RUN npm ci FROM base AS builder WORKDIR /app COPY --from=deps /app/node_modules ./node_modules COPY . . RUN npm run build # Production image, copy all the files and run next FROM base AS runner WORKDIR /app ENV NODE_ENV production COPY --from=builder /app/.next/standalone ./ COPY --from=builder /app/.next/static ./.next/static COPY --from=builder /app/public ./public EXPOSE 3000 ENV PORT 3000 ENV HOSTNAME localhost CMD ["node", "server.js"]
-
Deploying a Web Service on a Cloud VPS Using Kubernetes MicroK8s: A Comprehensive Guide
This instructs docker to start building our image from an existing node image based on Alpine Linux. Alpine distribution is the smallest Linux distribution which allows building lightweight images.
-
.dockerignore being ignored by docker-compose? no space left on device
FROM node:21-alpine AS base FROM base AS builder Check https://github.com/nodejs/docker-node/tree/b4117f9333da4138b03a546ec926ef50a31506c3#nodealpine to understand why libc6-compat might be needed. RUN apk add --no-cache libc6-compat RUN apk update Set working directory WORKDIR /app Install pnpm with corepack RUN corepack enable && corepack prepare pnpm@latest --activate Enable pnpm add --global on Alpine Linux by setting home location environment variable to a location already in $PATH https://github.com/pnpm/pnpm/issues/784#issuecomment-1518582235 ENV PNPM_HOME=/usr/local/bin RUN pnpm install turbo --global COPY . . RUN turbo prune web --docker Add lockfile and package.json's of isolated subworkspace FROM base AS installer RUN apk add --no-cache libc6-compat RUN apk update WORKDIR /app First install the dependencies (as they change less often) COPY .gitignore .gitignore COPY --from=builder /app/out/json/ . COPY --from=builder /app/out/pnpm-workspace.yaml ./pnpm-workspace.yaml COPY --from=builder /app/out/pnpm-lock.yaml ./pnpm-lock.yaml RUN pnpm install Build the project COPY --from=builder /app/out/full/ . RUN pnpm turbo run build --filter=web FROM base AS runner WORKDIR /app Don't run production as root RUN addgroup --system --gid 1001 nodejs RUN adduser --system --uid 1001 nextjs USER nextjs COPY --from=installer /app/apps/web/next.config.js . COPY --from=installer /app/apps/web/package.json . Automatically leverage output traces to reduce image size https://nextjs.org/docs/advanced-features/output-file-tracing COPY --from=installer --chown=nextjs:nodejs /app/apps/web/.next/standalone ./ COPY --from=installer --chown=nextjs:nodejs /app/apps/web/.next/static ./apps/web/.next/static COPY --from=installer --chown=nextjs:nodejs /app/apps/web/public ./apps/web/public CMD node apps/web/server.js
-
WTF...Next.js app deployed with Docker?
FROM node:18-alpine AS base # Install dependencies only when needed FROM base AS deps # Check https://github.com/nodejs/docker-node/tree/b4117f9333da4138b03a546ec926ef50a31506c3#nodealpine to understand why libc6-compat might be needed. RUN apk add --no-cache libc6-compat WORKDIR /app # Install dependencies based on the preferred package manager COPY package.json yarn.lock* package-lock.json* pnpm-lock.yaml* ./ RUN \ if [ -f yarn.lock ]; then yarn --frozen-lockfile; \ elif [ -f package-lock.json ]; then npm ci; \ elif [ -f pnpm-lock.yaml ]; then yarn global add pnpm && pnpm i --frozen-lockfile; \ else echo "Lockfile not found." && exit 1; \ fi # Rebuild the source code only when needed FROM base AS builder WORKDIR /app COPY --from=deps /app/node_modules ./node_modules COPY . . # Next.js collects completely anonymous telemetry data about general usage. # Learn more here: https://nextjs.org/telemetry # Uncomment the following line in case you want to disable telemetry during the build. # ENV NEXT_TELEMETRY_DISABLED 1 RUN yarn build # If using npm comment out above and use below instead # RUN npm run build # Production image, copy all the files and run next FROM base AS runner WORKDIR /app ENV NODE_ENV production # Uncomment the following line in case you want to disable telemetry during runtime. # ENV NEXT_TELEMETRY_DISABLED 1 RUN addgroup --system --gid 1001 nodejs RUN adduser --system --uid 1001 nextjs COPY --from=builder /app/public ./public # Set the correct permission for prerender cache RUN mkdir .next RUN chown nextjs:nodejs .next # Automatically leverage output traces to reduce image size # https://nextjs.org/docs/advanced-features/output-file-tracing COPY --from=builder --chown=nextjs:nodejs /app/.next/standalone ./ COPY --from=builder --chown=nextjs:nodejs /app/.next/static ./.next/static USER nextjs EXPOSE 3000 ENV PORT 3000 # set hostname to localhost ENV HOSTNAME "0.0.0.0" # server.js is created by next build from the standalone output # https://nextjs.org/docs/pages/api-reference/next-config-js/output CMD ["node", "server.js"]
-
Node.js built-ins on Deno Deploy
Official docker image for node is built from Alpine or Debian [1]
Forgive me if I don't believe that running a full OS on a host OS to run a single node command doesn't amount to running a VM.
[1] https://github.com/nodejs/docker-node/tree/main/20
-
Beginner recommendations
This is Node's Docker image.
-
Dockerize Your App: An Introduction to Docker
Since the project is written in Node.js, we need to find a Node.js environment on Docker Hub. We can find the official Node image on Docker Hub by searching for "Node.js".
-
Managing upstream security fixes in uselagoon docker images
This node image is just one of a range published by the Node.js team (https://hub.docker.com/_/node), and they also have the Dockerfile for their build available
-
How can i get a container with npm command?I can’t find it with internet.
do you mean container image? npm comes in the "node" container image https://hub.docker.com/_/node
-
nodejs docker on SCALE?
I'm trying to setup a docker container for running a node js app. I'm a bit of a newbie when it comes to docker, but from what I've read all I need to do is "Launch docker image" and enter the image name from the docker repo. In this case: https://hub.docker.com/_/node My config looks like this. After that the UI just says deploying forever. I must be missing something obvious, any ideas?
Hexo
-
Ask HN: Looking for lightweight personal blogging platform
A lot of great suggestions here and some stuff I’ve never heard of before!
Throwing my own suggestion into the ring, as I was just looking into this last week.
I started setting up a blog using Hexo. It’s another Node based SSG that uses markdown and supports tags. It has a lot of neat plugins that people have developed, too.
I like it so far!
https://github.com/hexojs/hexo
-
Hexo, WebFinger and better discoverability
In my case, the latter is not possible because this blog is a static site, generated via Hexo and hosted on GitHub. It simply lacks a modifiable active server component.
-
Top ten popular static site generators (SSG) in 2023
Hexo — best lightweight SSG
-
Nuxt 3 - showcase your sites
Previously I've used Nuxt2 and even sooner - hexo.io
-
Building a static blog using Jekyll & Strapi
To make their creation easier, numerous open-source static websites generators are available: Jekyll, Hugo, Gatsby, Hexo, etc. Most of the time, the content is managed through static (ideally Markdown) files or a Content API. Then, the generator requests the content, injects it in templates defined by the developer and generates a bunch of HTML files.
-
Running a blog on GithubPages with Markdown storage
https://gohugo.io/ written in go, support md https://hexo.io/ written in node
-
Comparing Static and Dynamic Websites
Hexo's
-
who is self-hosting a static website and what are you using to build it?
I'm currently using Hexo, I write articles in markdown, commit them to a git repository and push them to Github. I then have a Github Action to bundle the static website and publish it on Github Pages, so I get free hosting 👌
-
Deploy your blog via let.sh
There are also many alternatives for selecting Static-Side Generating blog framework such as Hexo, Gatsby, Next.js (more details here). We will pick Hexo as our framework because it is a fast, simple & powerful blog framework.
-
What I'm Learning in 2022
Some alternatives I'm considering learning instead of Gatsby are Jeckyll or Hexo.
What are some alternatives?
nvm - Node Version Manager - POSIX-compliant bash script to manage multiple active node.js versions
Hugo - The world’s fastest framework for building websites.
klipper-web-control-docker - Klipper with Moonraker shipped with Fluidd and/or Mainsail
Ghost - Independent technology for modern publishing, memberships, subscriptions and newsletters.
berry - 📦🐈 Active development trunk for Yarn ⚒
Jekyll - :globe_with_meridians: Jekyll is a blog-aware static site generator in Ruby
docker-flutter - flutter docker image with full android sdk
Pelican - Static site generator that supports Markdown and reST syntax. Powered by Python.
colima - Container runtimes on macOS (and Linux) with minimal setup
GrapesJS - Free and Open source Web Builder Framework. Next generation tool for building templates without coding
docker-openresty - Docker tooling for OpenResty
astro - The web framework for content-driven websites. ⭐️ Star to support our work!