question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Update folder must exists.

See original GitHub issue

Hi,

I created a new keystone website with yo keystone, followed by node keystyone and then receive the following error:

KeystoneJS Update Error:

An updates folder must exist in your project root to use automatic updates.
If you want to use a custom path for your updates, set the `updates` option.
If you don't want to use updates, set the `auto update` option to `false`.
See http://keystonejs.com/docs/configuration/#updates for more information.

The generated website contains an updates folder, with the file 0.0.1-admins.js

Maybe I’m missing something ?

Issue Analytics

  • State:closed
  • Created 10 years ago
  • Comments:9 (2 by maintainers)

github_iconTop GitHub Comments

1reaction
schindldcommented, Mar 11, 2014

The problem is that [project_root]/node_modules/keystone/lib/updates.js doesn’t define a default value for the updates path.

A work-around is to add this line to your keystone.js file’s init object: ‘updates’: ‘updates’, The ‘updates’ on the left is the variable name that isn’t instantiated. The ‘updates’ on the right is the path (the cwd gets prepended).

0reactions
s2zamancommented, Mar 13, 2014

The problem https://github.com/JedWatson/keystone/issues/224#issue-29197120 is solved as follow: I set these values for cloudinary config from cloudinary, so the admin page is now OK to Sign-in with the already-generated email: user@keystonejs.com and password: admin.

keystone.set('cloudinary config', {
  cloud_name: 'my-cloud',
  api_key: 'abc',
  api_secret: '123'
});
// optional, will prefix all built-in tags with 'keystone_'
keystone.set('cloudinary prefix', 'keystone');
Read more comments on GitHub >

github_iconTop Results From Across the Web

How to Fix Destination Folder Already Exists Error in WordPress
Fixing Destination Folder Already Exists Error in WordPress​​ First you will need to connect to your WordPress site using an FTP client or...
Read more >
"The folder you're trying to use already exists. You can only ...
Go to the Windows control panel and select "Folder Options" and then "View" · Under hidden files and folders, select "Show hidden files...
Read more >
How To Fix the “Installation Failed: Destination ... - YouTube
The 4 methods you need to fix this (rather annoying ) error are here ... folder from your site files, you'll be free...
Read more >
How To Fix the “Installation Failed: Destination Folder ... - Kinsta
How To Fix the “Installation Failed: Destination Folder Already Exists” Error (4 Methods) · 1. Replace the Existing Folder With an Uploaded File....
Read more >
Fixing the Destination Folder Already Exists Error - Muffin Group
WordPress users must understand that it uses a structured folder system to organize and keep its core files. They separate the file for...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found