First deploy fails

[ArneNostitz]

hi - i installed all from scratch following the really great and easy tutorial. but sadly netify fails deploying the site in the first place... what am I doing wrong?

this is the log:
1:28:09 PM: build-image version: a2d22d22e4555d1ef0a972ed14a0a4b366ad20c4 (focal)
1:28:09 PM: build-image tag: v4.16.3
1:28:09 PM: buildbot version: e2f63efe7f752311197ae3394a83cb4531d1cbd2
1:28:09 PM: Fetching cached dependencies
1:28:09 PM: Failed to fetch cache, continuing with build
1:28:09 PM: Starting to prepare the repo for build
1:28:09 PM: No cached dependencies found. Cloning fresh repo
1:28:09 PM: git clone --filter=blob:none --no-checkout https://github.com/*****removed private info*****
1:28:10 PM: Preparing Git Reference refs/heads/main
1:28:10 PM: Parsing package.json dependencies
1:28:11 PM: Starting build script
1:28:11 PM: Installing dependencies
1:28:11 PM: Python version set to 2.7
1:28:12 PM: v16.19.0 is already installed.
1:28:12 PM: Now using node v16.19.0 (npm v8.19.3)
1:28:12 PM: Enabling Node.js Corepack
1:28:12 PM: Started restoring cached build plugins
1:28:12 PM: Finished restoring cached build plugins
1:28:12 PM: Attempting Ruby version 2.7.2, read from environment
1:28:13 PM: Using Ruby version 2.7.2
1:28:13 PM: Using PHP version 8.0
1:28:13 PM: Started restoring cached go cache
1:28:13 PM: Finished restoring cached go cache
1:28:14 PM: Installing Go version 1.19.5 (requested 1.19.x)
1:28:19 PM: unset GOOS;
1:28:19 PM: unset GOARCH;
1:28:19 PM: export GOROOT='/opt/buildhome/.gimme/versions/go1.19.5.linux.amd64';
1:28:19 PM: export PATH="/opt/buildhome/.gimme/versions/go1.19.5.linux.amd64/bin:${PATH}";
1:28:19 PM: go version >&2;
1:28:19 PM: export GIMME_ENV="/opt/buildhome/.gimme/env/go1.19.5.linux.amd64.env"
1:28:19 PM: go version go1.19.5 linux/amd64
1:28:19 PM: Detected 0 framework(s)
1:28:19 PM: Installing missing commands
1:28:19 PM: Verify run directory
1:28:19 PM: Section completed: initializing
1:28:21 PM: ​
1:28:21 PM: Netlify Build
1:28:21 PM: ────────────────────────────────────────────────────────────────
1:28:21 PM: ​
1:28:21 PM: ❯ Version
1:28:21 PM: @netlify/build 29.5.1
1:28:21 PM: ​
1:28:21 PM: ❯ Flags
1:28:21 PM: baseRelDir: true
1:28:21 PM: buildId: 63ca88cd214ffb00091acff5
1:28:21 PM: deployId: 63ca88cd214ffb00091acff7
1:28:21 PM: ​
1:28:21 PM: ❯ Current directory
1:28:21 PM: /opt/build/repo
1:28:21 PM: ​
1:28:21 PM: ❯ Config file
1:28:21 PM: No config file was defined: using default values.
1:28:21 PM: ​
1:28:21 PM: ❯ Context
1:28:21 PM: production
1:28:21 PM: ​
1:28:21 PM: 1. Build command from Netlify app
1:28:21 PM: ────────────────────────────────────────────────────────────────
1:28:21 PM: ​
1:28:21 PM: $ npm install && npm run build
1:28:21 PM: npm ERR! code ENOENT
1:28:21 PM: npm ERR! syscall open
1:28:21 PM: npm ERR! path /opt/build/repo/package.json
1:28:21 PM: npm ERR! errno -2
1:28:21 PM: npm ERR! enoent ENOENT: no such file or directory, open '/opt/build/repo/package.json'
1:28:21 PM: npm ERR! enoent This is related to npm not being able to find a file.
1:28:21 PM: npm ERR! enoent
1:28:21 PM: npm ERR! A complete log of this run can be found in:
1:28:21 PM: npm ERR! /opt/buildhome/.npm/_logs/2023-01-20T12_28_21_343Z-debug-0.log
1:28:21 PM: ​
1:28:21 PM: "build.command" failed
1:28:21 PM: ────────────────────────────────────────────────────────────────
1:28:21 PM: ​
1:28:21 PM: Error message
1:28:21 PM: Command failed with exit code 254: npm install && npm run build (https://ntl.fyi/exit-code-254)
1:28:21 PM: ​
1:28:21 PM: Error location
1:28:21 PM: In Build command from Netlify app:
1:28:21 PM: npm install && npm run build
1:28:21 PM: ​
1:28:21 PM: Resolved config
1:28:21 PM: build:
1:28:21 PM: command: npm install && npm run build
1:28:21 PM: commandOrigin: ui
1:28:21 PM: publish: /opt/build/repo/dist
1:28:21 PM: publishOrigin: ui
1:28:21 PM: functionsDirectory: /opt/build/repo/netlify/functions
1:28:21 PM: Caching artifacts
1:28:21 PM: Started saving build plugins
1:28:21 PM: Finished saving build plugins
1:28:21 PM: Started saving pip cache
1:28:21 PM: Finished saving pip cache
1:28:21 PM: Started saving emacs cask dependencies
1:28:23 PM: Failed during stage 'building site': Build script returned non-zero exit code: 2 (https://ntl.fyi/exit-code-2)
1:28:22 PM: Finished saving emacs cask dependencies
1:28:22 PM: Started saving maven dependencies
1:28:22 PM: Finished saving maven dependencies
1:28:22 PM: Started saving boot dependencies
1:28:22 PM: Finished saving boot dependencies
1:28:22 PM: Started saving rust rustup cache
1:28:22 PM: Finished saving rust rustup cache
1:28:22 PM: Started saving go dependencies
1:28:22 PM: Finished saving go dependencies
1:28:23 PM: Build failed due to a user error: Build script returned non-zero exit code: 2
1:28:23 PM: Failing build: Failed to build site
1:28:23 PM: Finished processing build request in 13.977045435s

[ArneNostitz]

i noticed, that the repository on git was empty. i did a manual clone of the template. then the deploy succeeded - but the site does not update on a push - somehow the deploy does not get triggered. (also site theme settings etc are not updated without a manual deploy on netify)

how do i trigger the auto deploy?

[ArneNostitz]

(i redid the whole thing to check - and the "deploy to netify" does create an empty repo and does not copy the template in)

[ArneNostitz]

does it need to trigger a whole deploy every time i update/upload a (new) file?

[oleeskild]

There seems to be an issue with Netlify, where it won't clone the repository 🤔 I guess we'll just have to wait until they fix it.
In the meantime, to get around it, you can do the following to replace the deploy to netlify step:

1. Go to the digital garden repo. Select "Use this template", then "Create new template". This will create a copy of the repo in your own account.

2. Then go to Netlify and click the "Add new site" and "Import an existing project"

3. Now pick the repo you created in step 1. Then follow the rest of the "Getting Started" tutorial and you should be good to go. Let me know if you run into any trouble.

[oleeskild]

As this doesn't seem to get fixed by Netlify, I've recently changed the getting started guide and readme to use Vercel instead of Netlify. They are really similar to each other, and the garden is fully functional on both platforms. Existing gardens will still remain fully functional. But new gardens should now work, by using the new "Deploy to Vercel" button.