History

Karl Horky 3ad55721d1 Remove incorrect entries for pnpm debug log (#47241 ) Reasons for making this change: - it is contained within `node_modules/`, which is already ignored - the previous versions, which were not in `node_modules/`, did not have a period at the beginning of the filename Links to documentation supporting these rule changes: Changelog with proof here: `ba4b2db1f2/pnpm/CHANGELOG.md (L3330)` History: - my PR to remove this from `github/gitignore` here: https://github.com/github/gitignore/pull/4250 - First introduced in `github/gitignore` in https://github.com/github/gitignore/pull/3732 by `@sakurayang` (merged by `@martinwoodward`) <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation or adding/fixing Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # --> --------- Co-authored-by: JJ Kasper <jj@jjsweb.site>		2023-03-26 22:26:05 -07:00
..
blog	Convert `with-videojs`, `with-yoga`, `with-zones` examples to TypeScript (#43280 )	2022-11-23 13:46:54 +01:00
docs	Update multi zones example (#16281 )	2020-11-16 16:21:13 +00:00
home	Convert `with-videojs`, `with-yoga`, `with-zones` examples to TypeScript (#43280 )	2022-11-23 13:46:54 +01:00
.gitignore	Remove incorrect entries for pnpm debug log (#47241 )	2023-03-26 22:26:05 -07:00
package.json	Remove `licence` from all `example/package.json` that has them (#28007 )	2021-08-14 10:48:39 -05:00
README.md	docs(examples): improve DX while copying command to create new project (#38410 )	2022-07-26 21:57:48 -05:00

README.md

Using multiple zones

With Next.js you can use multiple apps as a single app using its multi-zones feature. This is an example showing how to use it.

All pages should be unique across zones. For example, the home app should not have a pages/blog/index.js page.
The home app is the main app and therefore it includes the rewrites that map to the blog app in next.config.js
The blog app sets basePath to /blog so that generated pages, Next.js assets and public assets are within the /blog subfolder.

How to use

Execute create-next-app with npm, Yarn, or pnpm to bootstrap the example:

npx create-next-app --example with-zones with-zones-app

yarn create next-app --example with-zones with-zones-app

pnpm create next-app --example with-zones with-zones-app

With multi zones you have multiple Next.js apps over a single app, therefore every app has its own dependencies and it runs independently.

To start the /home run the following commands from the root directory:

cd home
npm install && npm run dev
# or
cd home
yarn && yarn dev

The /home app should be up and running in http://localhost:3000!

Starting the /blog app follows a very similar process. In a new terminal, run the following commands from the root directory :

cd blog
npm install && npm run dev
# or
cd blog
yarn && yarn dev

The blog app should be up and running in http://localhost:4000!

Preview

Preview the example live on StackBlitz:

Deploy on Vercel

You can deploy this app to the cloud with Vercel (Documentation).

Deploy Your Local Project

To deploy the apps to Vercel, we'll use monorepos support to create a new project for each app.

To get started, push the example to GitHub/GitLab/Bitbucket and import your repo to Vercel. We're not interested in the root directory, so make sure to select the blog directory (do not start with home):

Click continue and finish the import process. After that's done copy the domain URL that was assigned to your project, paste it on home/.env, and push the change to your repo:

# Replace this URL with the URL of your blog app
BLOG_URL="https://with-zones-blog.vercel.app"

Now we'll go over the import flow again using the same repo but this time select the home directory instead:

With the home app deployed you should now be able to see both apps running under the same domain!

Any future commits to the repo will trigger a deployment to the connected Vercel projects. See the blog post about monorepos to learn more.