Ciao from Italy!

I was experimenting with the old 1.0.2 version before the 1.1 version came out, specifically I made some little customizations to the layout (also, translating text into Italian).

Since you suggest using backups when upgrading Strawberry, and 1.0.2 doesn't support backups, I was trying to understand how I should backup my 1.0.2 version manually, and so I tried to do a backup of the example site that comes with Strawberry, to see how the _backup folder is built.

I had this error while running "npm run backup" (by the way, I'm using Windows 10):

Error: ENOENT: no such file or directory, copyfile 'C:\Users\user\Documents\website\src\_includes\navbar.html' -> 'C:\Users\user\Documents\website\_backup\src\_includes\navbar.html'

I thought it couldn't find the source file, but I found out that, actually, it's complaining that the _includes folder doesn't exist in the _backup folder.

I added this in the back-up.js file, after the fs.mkdirSync lines:

fs.mkdirSync(path.normalize('_backup/src/_includes'));

and then it seemed to work (the script printed "Site backed up successfully.")

I'm still not sure, though, how should I use the _backup folder: do I take the contents of the folder and put it in the main folder, or do I take the _backup folder and put it inside the main folder?

Thank you so much for your work!

hi!

thanks for reporting what looks like a nasty mistake in the backup script; i'll take a look at that sometime this week and get an update out soon. i didn't encounter this issue among my testers so i'm curious to see what's up - i might have pushed a bad version of the script or something

as for the backup folder, you want to put its *contents* into the main folder