migrating to verdaccio

[verdaccio]

migrating to verdaccio

[juanpicado]

Just switch it, it's backwards compatible.

[qballer]

I'm running verdaccio with forever, and looks good. 10x

future ref: forever <install folder>/node_modules/.bin/verdaccio -c <data-folder>/config.yaml &

[kroltan]

I have this issue too. Installed Verdaccio and changed the config so storage points to the same path as the old Sinopia storage, but no modules show up on the web interface, nor can I download them.

[dev-rowbot]

@juanpicado I'm away from the office so I will try remember the exact steps...

Essentially you need to setup an instance of Verdaccio 2.x (I think we are on 2.7.1 but the exact version should not matter).

Run the container as per the docker example on the homepage but add a data volume, e.g.:

docker run -it --name verdaccio -v /data/verdaccio2/storage:/verdaccio/storage -p 4873:4873 verdaccio/verdaccio:2.7.1

Set this registry as your npm registry and run an npm install so that it caches a few packages. Then publish a local package as well so that you have at least 1 package showing on the UI landing page.

Now create a 2nd verdaccio instance (you can stop the first if you need the same port) but give it a new data volume location.

docker run -it --name verdaccio -v /data/verdaccio3/storage:/verdaccio/storage -p 4873:4873 verdaccio/verdaccio:3.1.0

Copy the data from /data/verdaccio2/storage to /data/verdaccio3/storage.

rsync -avzh /data/verdaccio2/storage/ /data/verdaccio3/storage

Even after a container restart nothing will appear in the UI and publishing new packages will probably fail as well.

I noticed with our 2.x instance that the verdaccio process runs as root and the 3.1.0 instance runs as verdaccio so there are rights issues. You can fix this by changing ownership but it doesn't solve the problem for me:

docker exec -it -u root verdaccio /bin/sh
chown -R verdaccio:verdaccio /verdaccio/storage
exit

I hope this helps!

[jmwilkinson]

I think the question is about migrating the package history over to the running verdaccio instance? Is that correct?

[Nicholaiii]

If you're still in doubt, I believe you just need to move the folder from the sinopia install to the verdaccio install.

[jmellor]

Nicolaiii stated:

I believe you just need to move the folder from the sinopia install to the verdaccio install.

I have a running docker instance of Sinopia and one of Verdaccio. Both have a bind mount for the storage directory. I need to migrate all the local packages to Verdaccio. I must be missing something, because copying the storage directory from Sinopia to verdaccio does not appear to actually work as described. The packages are present in storage, but not visible in the web page. What else needs to be done to successfully move from Sinopia to Verdaccio?

[juanpicado]

@jmellor I'm not able to reproduce your issue. I have one instance of Sinopia and another one for Verdaccio, both pointing the same config file and same storage folder. I published 5 modules through Sinopia and 2 from Verdaccio.

This is the storage overview

Whether I load the web UI with Sinopia, all modules published with Sinopia are displayed, but, not those published with Verdaccio.

Whether I load the web UI with Verdaccio, all modules are displayed, even those published through Sinopia.

The database's content is the following, btw, Verdaccio still remains using .sinopia-db.json.

{"list":[
"crypto_test",
"crypto_test_verdaccio",
"crypto_test_sinopia",
"crypto_test_sinopia1",
"crypto_test_sinopia2",
"crypto_test_verdaccio2",
"crypto_test_sinopia_33"],
"secret":"cc1eb2ec68c4053ef6dd9b8f7e685841af0e05d822f2b4ee84894f8c851f0b3e"}

So, the unique "bug" I see by far is Sinopia is not able to display those modules published through Verdaccio, but that's irrelevant in your case.

[jmellor]

Help! I’m back on trying to migrate from Sinopia to Verdaccio, but I’m stuck . The Sinopia implementation is running in the keyvanfatehi/sinopia:latest docker image from 19 months ago. I asked Keyvan about fixes, and he replied that that I should just move over to Verdaccio, but the most obvious migration path seems to be broken. The sinopia docker image makes the assumption that the storage directory is in /opt/sinopia, while it looks like the verdaccio image puts this in /verdaccio. My existing sinopia startup script looks like: docker run --name sinopia -d -p 4873:4873 -v /opt/sinopia/storage:/opt/sinopia/storage keyvanfatehi/sinopia:latest My current attempt at migrating is to: 1. Assume that the [large] storage directory is the same content in both sinopia and verdaccio 2. add the verdaccio conf/config.yaml file to a new /opt/sinopia/conf directory 3. add a new empty local_storage directory in the /opt/sinopia directory 4. boot the docker image with: docker run --name verdaccio -d -p 4873:4873 -v /opt/sinopia:/verdaccio verdaccio/verdaccio:latest This should make it so that it all operates as expected, but there are no packages found. Instead, the docker image comes up fine and the web page looks as-expected on port 4873, but there is no content. What am I doing wrong? How can I debug this? [cid:[email protected]] From: jotadeveloper [mailto:[email protected]] Sent: April-04-17 15:09 To: verdaccio/verdaccio <[email protected]> Cc: John Mellor <[email protected]>; Mention <[email protected]> Subject: Re: [verdaccio/verdaccio] migrating to verdaccio (#69) @jmellor<https://github.com/jmellor> I'm not able to reproduce your issue. I have one instance of Sinopia and another one for Verdaccio, both pointing the same config file and same storage folder. I published 5 modules through Sinopia and 2 from Verdaccio. This is the storage overview [file_system]<https://cloud.githubusercontent.com/assets/558752/24673829/db8fd2a0-1979-11e7-90e9-235884e97c7a.png> Whether I load the web UI with Sinopia, all modules published with Sinopia are displayed, but, not those published with Verdaccio. [sinopia_web]<https://cloud.githubusercontent.com/assets/558752/24673822/d896ec82-1979-11e7-8518-2b84146abb9a.png> Whether I load the web UI with Verdaccio, all modules are displayed, even those published through Sinopia. [verdaccio_web]<https://cloud.githubusercontent.com/assets/558752/24673821/d89038c4-1979-11e7-9f2b-79a437d196fb.png> The database's content is the following, btw, Verdaccio still remains using .sinopia-db.json. {"list":[ "crypto_test", "crypto_test_verdaccio", "crypto_test_sinopia", "crypto_test_sinopia1", "crypto_test_sinopia2", "crypto_test_verdaccio2", "crypto_test_sinopia_33"], "secret":"cc1eb2ec68c4053ef6dd9b8f7e685841af0e05d822f2b4ee84894f8c851f0b3e"} So, the unique "bug" I see by far is Sinopia is not able to display those modules published through Verdaccio, but that's irrelevant in your case. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#69 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AKkBZVnIZuQIGU5CU0ODbnf6fc0X52H3ks5rspVagaJpZM4KUoWo>.

[dev-rowbot]

I have a similar issue - migrating from docker Verdaccio 2.x to docker Verdaccio 3.1.0 on a different server.
I copied the data volumes across but the new instance does not pick up the data. I eventually wrote a script to read the locally published packages from the old .sinopia-db.json file and push each tarball to the new Verdaccio instance.

Nothing special but this may help: https://gist.github.com/dev-rowbot/38b7ad3b0e0b951598e9df144160e17f

[juanpicado]

I copied the data volumes across but the new instance does not pick up the data.

I'm not expert in Docker, but, it would be great to have a simple list steps to reproduce it. Migration should be clean, even in Docker.

[juanpicado]

@dev-rowbot ok I see you were using a quite old Verdaccio docker image. The latest 2.x were using verdaccio as the user already (https://github.com/verdaccio/verdaccio/releases/tag/v2.2.5)

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.