Como usar Next.js com Docker e Docker Compose

Neste tutorial, aprenderemos como usar Next.js com Docker e Docker Compose para iniciantes

Antes de pular para o código, abaixo estão alguns requisitos:

• Você deve ter o Node.js instalado em seu sistema, de preferência o LTS mais recente, que é o Node.js v 18 no momento da redação. Da mesma forma, algum conhecimento de npm e npx também será necessário.
• Tenha o Docker instalado e o docker-compose instalado em sua máquina
• Qualquer experiência anterior com o Next.js é benéfica, mas não necessária.

Na próxima seção, você instalará o Next.js sem o Docker e, em seguida, o dockerizará.

Instalar Next.js sem Docker

Para este tutorial, você usará o exemplo de API Routes dos exemplos oficiais do Next.js. Você pode instalar este exemplo executando:

npx create-next-app --example api-routes api-routes-app

Ele mostrará uma saída como a abaixo:

Para testar se o exemplo está funcionando corretamente, você pode executar:

cd api-routes-app
npm run dev

Ele rodará o servidor e agora você pode acessar o app em http://locahost:3000 que ficará assim:

Você pode clicar nos nomes e brincar. Na próxima seção, você fará o Dockerize deste aplicativo Next.js de exemplo, que possui APIs para as pessoas.

Imagem do Docker para Next.js

Para Dockerize o aplicativo acima, você adicionará o seguinte Dockerfile na raiz do projeto:

FROM node:18-alpine AS deps
RUN apk add --no-cache libc6-compat
WORKDIR /app

COPY package.json package-lock.json ./
RUN  npm install --production

FROM node:18-alpine AS builder
WORKDIR /app
COPY --from=deps /app/node_modules ./node_modules
COPY . .

ENV NEXT_TELEMETRY_DISABLED 1

RUN npm run build

FROM node:18-alpine AS runner
WORKDIR /app

ENV NODE_ENV production
ENV NEXT_TELEMETRY_DISABLED 1

RUN addgroup --system --gid 1001 nodejs
RUN adduser --system --uid 1001 nextjs

COPY --from=builder --chown=nextjs:nodejs /app/.next ./.next
COPY --from=builder /app/node_modules ./node_modules
COPY --from=builder /app/package.json ./package.json

USER nextjs

EXPOSE 3000

ENV PORT 3000

CMD ["npm", "start"]

Este é um Dockerfile de vários estágios que começa com um estágio de deps . Nesta primeira etapa que começa a partir da imagem Node.js Alpine. Em seguida, ele adiciona o pacote lib6-comat necessário para construir o Next.js. Como o estágio é chamado de deps para dependências, neste estágio os módulos npm são instalados em seguida.

Depois disso, você adiciona o estágio do construtor onde os módulos do nó são copiados e o comando npm run build é executado para construir o projeto Next.js. Você também está desabilitando a telemetria Next.js, isso acelera um pouco a compilação.

Depois disso, você define o estágio do corredor . Este é o palco principal que executa o Next.js. Aqui você usa a imagem Node.js 18 Alpine semelhante a todos os estágios acima. Em seguida, adicione um grupo e usuário para Next.js. Também é importante para a segurança. Depois disso, você copia a próxima pasta do estágio do construtor , os módulos do nó e o arquivo package.json. Em seguida, você define o usuário como nextjs que executará o comando para executar o projeto Next.js. No final, você executa o npm start , que iniciará o contêiner com esse comando.

Adicionando Docker Compose para Next.js

Você pode executar o Next.js apenas com o arquivo Docker acima, mas será um comando longo. Para manter as coisas simples, você introduzirá um novo arquivo docker-compose.yml com o seguinte conteúdo na raiz do projeto:

version: '3.8'
services:
  web:
    build:
      context: ./
      target: runner
    volumes:
      - .:/app
    command: npm run dev
    ports:
      - "3000:3000"
    environment:
      NODE_ENV: development

Aqui você define um serviço chamado web e o stage/target a ser runner . Você vincula o diretório local a /app no ​​contêiner, isso ajudará com o hot reload no desenvolvimento local, pois os arquivos serão substituídos localmente em cada salvamento.

Em seguida, você substitui o comando para ser npm run dev e vincula a porta local 3000 à porta do contêiner 3000. Finalmente, você define o NODE_ENV como development .

O detalhe mais importante que você deve lembrar aqui é que o arquivo Docker acima está pronto para produção e o Docker Compose, neste caso, foi projetado para ser usado apenas para desenvolvimento.

Executar Next.js com docker compose

Para executar o projeto Next.js com docker-compose, você criará a imagem do docker e executará o contêiner. Para fazer isso, você executará:

COMPOSE_DOCKER_CLI_BUILD=1 DOCKER_BUILDKIT=1 docker-compose build

Você está instruindo o docker a usar o Buildkit, o que acelerará o processo de compilação do docker. O comando, se executado com sucesso, terminará da seguinte maneira:

Para executar Next.js com Docker e docker-compose, você pode executar:

docker-compose up

Ele mostrará a mesma saída ao executar o aplicativo sem o docker quando você clicar em http://localhost:3000 em seu navegador favorito depois que o docker-compose up for executado sem nenhum erro:

Se alterar o pages/index.tsx para retornar o seguinte no final do arquivo:

return (
  <div>
    <h2>With Docker</h2>
    <ul>
      {data.map((p: Person) => (
      <PersonComponent key={p.id} person={p} />
      ))}
    </ul>
  </div>
)

As alterações serão captadas rapidamente e exibidas no navegador da seguinte maneira:

Parabéns! Você dockerizou com sucesso um projeto Next.js. Como o aplicativo foi dockerizado, você pode executá-lo em qualquer serviço com ou sem Kubernetes. Você também pode experimentar o PostgreSQL com Docker e Docker compose e conectá-lo ao seu aplicativo Next.js.

Obrigado por acompanhar, você pode encontrar todo o código deste tutorial neste repositório do GitHub . Para o código específico do docker, consulte este GitHub .

What is GEEK

Buddha Community

NBB: Ad-hoc CLJS Scripting on Node.js

Nbb

Not babashka. Node.js babashka!?

Ad-hoc CLJS scripting on Node.js.

Status

Experimental. Please report issues here.

Goals and features

Nbb's main goal is to make it easy to get started with ad hoc CLJS scripting on Node.js.

Additional goals and features are:

• Fast startup without relying on a custom version of Node.js.
• Small artifact (current size is around 1.2MB).
• First class macros.
• Support building small TUI apps using Reagent.
• Complement babashka with libraries from the Node.js ecosystem.

Requirements

Nbb requires Node.js v12 or newer.

How does this tool work?

CLJS code is evaluated through SCI, the same interpreter that powers babashka. Because SCI works with advanced compilation, the bundle size, especially when combined with other dependencies, is smaller than what you get with self-hosted CLJS. That makes startup faster. The trade-off is that execution is less performant and that only a subset of CLJS is available (e.g. no deftype, yet).

Usage

Install nbb from NPM:

$ npm install nbb -g

Omit -g for a local install.

Try out an expression:

$ nbb -e '(+ 1 2 3)'
6

And then install some other NPM libraries to use in the script. E.g.:

$ npm install csv-parse shelljs zx

Create a script which uses the NPM libraries:

(ns script
  (:require ["csv-parse/lib/sync$default" :as csv-parse]
            ["fs" :as fs]
            ["path" :as path]
            ["shelljs$default" :as sh]
            ["term-size$default" :as term-size]
            ["zx$default" :as zx]
            ["zx$fs" :as zxfs]
            [nbb.core :refer [*file*]]))

(prn (path/resolve "."))

(prn (term-size))

(println (count (str (fs/readFileSync *file*))))

(prn (sh/ls "."))

(prn (csv-parse "foo,bar"))

(prn (zxfs/existsSync *file*))

(zx/$ #js ["ls"])

Call the script:

$ nbb script.cljs
"/private/tmp/test-script"
#js {:columns 216, :rows 47}
510
#js ["node_modules" "package-lock.json" "package.json" "script.cljs"]
#js [#js ["foo" "bar"]]
true
$ ls
node_modules
package-lock.json
package.json
script.cljs

Macros

Nbb has first class support for macros: you can define them right inside your .cljs file, like you are used to from JVM Clojure. Consider the plet macro to make working with promises more palatable:

(defmacro plet
  [bindings & body]
  (let [binding-pairs (reverse (partition 2 bindings))
        body (cons 'do body)]
    (reduce (fn [body [sym expr]]
              (let [expr (list '.resolve 'js/Promise expr)]
                (list '.then expr (list 'clojure.core/fn (vector sym)
                                        body))))
            body
            binding-pairs)))

Using this macro we can look async code more like sync code. Consider this puppeteer example:

(-> (.launch puppeteer)
      (.then (fn [browser]
               (-> (.newPage browser)
                   (.then (fn [page]
                            (-> (.goto page "https://clojure.org")
                                (.then #(.screenshot page #js{:path "screenshot.png"}))
                                (.catch #(js/console.log %))
                                (.then #(.close browser)))))))))

Using plet this becomes:

(plet [browser (.launch puppeteer)
       page (.newPage browser)
       _ (.goto page "https://clojure.org")
       _ (-> (.screenshot page #js{:path "screenshot.png"})
             (.catch #(js/console.log %)))]
      (.close browser))

See the puppeteer example for the full code.

Since v0.0.36, nbb includes promesa which is a library to deal with promises. The above plet macro is similar to promesa.core/let.

Startup time

$ time nbb -e '(+ 1 2 3)'
6
nbb -e '(+ 1 2 3)'   0.17s  user 0.02s system 109% cpu 0.168 total

The baseline startup time for a script is about 170ms seconds on my laptop. When invoked via npx this adds another 300ms or so, so for faster startup, either use a globally installed nbb or use $(npm bin)/nbb script.cljs to bypass npx.

Dependencies

NPM dependencies

Nbb does not depend on any NPM dependencies. All NPM libraries loaded by a script are resolved relative to that script. When using the Reagent module, React is resolved in the same way as any other NPM library.

Classpath

To load .cljs files from local paths or dependencies, you can use the --classpath argument. The current dir is added to the classpath automatically. So if there is a file foo/bar.cljs relative to your current dir, then you can load it via (:require [foo.bar :as fb]). Note that nbb uses the same naming conventions for namespaces and directories as other Clojure tools: foo-bar in the namespace name becomes foo_bar in the directory name.

To load dependencies from the Clojure ecosystem, you can use the Clojure CLI or babashka to download them and produce a classpath:

$ classpath="$(clojure -A:nbb -Spath -Sdeps '{:aliases {:nbb {:replace-deps {com.github.seancorfield/honeysql {:git/tag "v2.0.0-rc5" :git/sha "01c3a55"}}}}}')"

and then feed it to the --classpath argument:

$ nbb --classpath "$classpath" -e "(require '[honey.sql :as sql]) (sql/format {:select :foo :from :bar :where [:= :baz 2]})"
["SELECT foo FROM bar WHERE baz = ?" 2]

Currently nbb only reads from directories, not jar files, so you are encouraged to use git libs. Support for .jar files will be added later.

Current file

The name of the file that is currently being executed is available via nbb.core/*file* or on the metadata of vars:

(ns foo
  (:require [nbb.core :refer [*file*]]))

(prn *file*) ;; "/private/tmp/foo.cljs"

(defn f [])
(prn (:file (meta #'f))) ;; "/private/tmp/foo.cljs"

Reagent

Nbb includes reagent.core which will be lazily loaded when required. You can use this together with ink to create a TUI application:

$ npm install ink

ink-demo.cljs:

(ns ink-demo
  (:require ["ink" :refer [render Text]]
            [reagent.core :as r]))

(defonce state (r/atom 0))

(doseq [n (range 1 11)]
  (js/setTimeout #(swap! state inc) (* n 500)))

(defn hello []
  [:> Text {:color "green"} "Hello, world! " @state])

(render (r/as-element [hello]))

Promesa

Working with callbacks and promises can become tedious. Since nbb v0.0.36 the promesa.core namespace is included with the let and do! macros. An example:

(ns prom
  (:require [promesa.core :as p]))

(defn sleep [ms]
  (js/Promise.
   (fn [resolve _]
     (js/setTimeout resolve ms))))

(defn do-stuff
  []
  (p/do!
   (println "Doing stuff which takes a while")
   (sleep 1000)
   1))

(p/let [a (do-stuff)
        b (inc a)
        c (do-stuff)
        d (+ b c)]
  (prn d))

$ nbb prom.cljs
Doing stuff which takes a while
Doing stuff which takes a while
3

Also see API docs.

Js-interop

Since nbb v0.0.75 applied-science/js-interop is available:

(ns example
  (:require [applied-science.js-interop :as j]))

(def o (j/lit {:a 1 :b 2 :c {:d 1}}))

(prn (j/select-keys o [:a :b])) ;; #js {:a 1, :b 2}
(prn (j/get-in o [:c :d])) ;; 1

Most of this library is supported in nbb, except the following:

• destructuring using :syms
• property access using .-x notation. In nbb, you must use keywords.

See the example of what is currently supported.

Examples

See the examples directory for small examples.

Also check out these projects built with nbb:

• c64core: retrocompute aesthetics twitter bot
• gallery.cljs: script to download walpapers from windowsonearth.org.
• nbb-action-example: example of a Github action built with nbb.

API

See API documentation.

Migrating to shadow-cljs

See this gist on how to convert an nbb script or project to shadow-cljs.

Build

Prequisites:

• babashka >= 0.4.0
• Clojure CLI >= 1.10.3.933
• Node.js 16.5.0 (lower version may work, but this is the one I used to build)

To build:

• Clone and cd into this repo
• bb release

Run bb tasks for more project-related tasks.

Download Details:
Author: borkdude
Download Link: Download The Source Code
Official Website: https://github.com/borkdude/nbb 
License: EPL-1.0

#node #javascript

Google analytics Setup with Next JS, React JS using Router Events - 14

In this video, we are going to implement Google Analytics to our Next JS application. Tracking page views of an application is very important.

Google analytics will allow us to track analytics information.

Frontend: https://github.com/amitavroy/video-reviews
API: https://github.com/amitavdevzone/video-review-api
App link: https://video-reviews.vercel.app

You can find me on:
Twitter: https://twitter.com/amitavroy7​
Discord: https://discord.gg/Em4nuvQk

#next js #js #react js #react #next #google analytics

Docker Explained: Docker Architecture | Docker Registries

Following the second video about Docker basics, in this video, I explain Docker architecture and explain the different building blocks of the docker engine; docker client, API, Docker Daemon. I also explain what a docker registry is and I finish the video with a demo explaining and illustrating how to use Docker hub

In this video lesson you will learn:

• What is Docker Host
• What is Docker Engine
• Learn about Docker Architecture
• Learn about Docker client and Docker Daemon
• Docker Hub and Registries
• Simple demo to understand using images from registries

#docker #docker hub #docker host #docker engine #docker architecture #api

Next.js on Fargate - Serverless Container Hosting with Docker and AWS Amplify

In this video we’ll start from scratch, creating a new Next.js app and then initializing a new Amplify project in the Next.js app directory. We’ll then configure a custom domain and deploy the Next.js app to Amazon ECS on AWS Fargate using the Amplify CLI using the custom domain.

Delete all infrastructure at any time by running “amplify delete”.

0:00 – Introduction
1:00 – Initializing the project
2:18 – Configuring the custom domain
4:33 – Enabling Fargate Hosting with the Amplify CLI
5:46 – Configuring the Dockerfile
7:27 – Testing the Docker image locally
8:32 – Deploying the app to Fargate using the Amplify CLI
12:00 – Conclusion

Dockerfile: https://gist.github.com/dabit3/6eb125dad05c1b1723bc44b6618e8ac4
Amplify Container docs: https://docs.amplify.aws/cli/usage/containers#hosting
Blog post: https://dev.to/dabit3/serverless-containers-with-next-js-aws-fargate-and-aws-amplify-17fe

#aws amplify #next.js #next #serverless container #docker

Cómo instalar Drupal con Docker Compose

Введение

Docker позволяет легко помещать приложения и службы в контейнеры, чтобы их можно было запускать где угодно. Однако при работе с Docker можно легко накопить чрезмерное количество неиспользуемых образов, контейнеров и томов данных, замедляющих работу и потребляющих место на диске.

Docker предоставляет все необходимые инструменты для очистки системы из командной строки. В этом руководстве с полезными советами кратко описываются полезные команды для освобождения места на диске и организации системы посредством удаления неиспользуемых образов, контейнеров и томов Docker.

Использование этого руководства:

• Это руководство в формате полезных советов содержит автономные сниппеты для командной строки
• Вы можете перейти к любому разделу, актуальному для задачи, которую вы пытаетесь выполнить.

Синтаксис замены команды command $(``command``), используемый в командах, доступен во многих популярных оболочках, включая bash, zsh и Windows Powershell.

Очистка всех неиспользуемых или не связанных с контейнерами образов, контейнеров, томов и сетей

В Docker имеется команда, очищающая все не связанные с контейнерами ресурсы, в том числе образы, контейнеры, тома и сети:

docker system prune

Чтобы удалить все остановленные контейнеры и неиспользуемые образы (а не только образы, не связанные с контейнерами), добавьте в эту команду флаг -a:

docker system prune -a

Удаление образов Docker

Удаление одного или нескольких конкретных образов

Используйте команду docker images с флагом -a, чтобы найти идентификатор удаляемых образов. Эта команда покажет вам все образы, включая промежуточные слои образов. Когда вы определитесь с составом удаляемых образов, вы можете передать их идентификаторы или теги в docker rmi:

Список:

docker images -a

Удаление:

docker rmi Image Image

Удаление образов, не привязанных к контейнеру

Образы Docker состоят из нескольких слоев. Несвязанные образы — это слои, не имеющие связей с каким-либо образами с тегами. У них нет никакого назначения, и они просто занимают место на диске. Их можно найти, добавив флаг фильтра -f со значением dangling=true в команду docker images. Если вы уверены, что хотите удалить их, вы можете использовать команду docker images purge:

#drupal #docker #docker compose #docker images