Issues after using pushkin armageddon

[MelindaPozzi]

Hi!

I updated my pushkin version from 1.5.5 to 2.0.0 (thinking that maybe this was the reason why I could not connect to the local host). But then I had some issues and I first tried pushkin kill and then pushkin armageddon.

Now I have this error message when I run pushkin prep:

And I have this question that I cannot answer when I run pushkin start:

Thank you in advance for your help!
Mélinda

[parkerrobbins]

Hi, @MelindaPozzi! A couple of other users have reported similar issues (e.g., #88, #100, #135). Your issue appears to be slightly different.

1. Could you double-check that the Pushkin CLI did indeed update to 2.0.0 by running pushkin --version? Some users had trouble upgrading to the newest version (e.g., Pushkin update #132, still with pushkin version 1.1.5 after upgrade #134).
2. Could you check that Docker is configured correctly by running docker run hello-world?
3. You may need to reinstall the site and experiments in a new directory (you can save your current directory and re-add any customizations you may have made to the code in the new directory). That worked for another user who had trouble after the update.

You are running this on Windows via an AWS instance, right?

[MelindaPozzi]

Hi!

Sorry for my late answer. Yes, I'm running this on Windows via an AWS instance.

I have the newest version (2.0.0) of Pushkin CLI and Docker seems to be configured correctly:

I've tried to create a new directory but when I run pushkin prep, I got this error message:

Thank you for your help!
Mélinda

[parkerrobbins]

Hi, @MelindaPozzi!

1. The newest version is now 2.2.10. You can update by running: yarn global upgrade pushkin-cli --latest.
2. After updating, please run pushkin armageddon again.
3. If you have customized your Pushkin site or experiment(s), then follow these instructions, which involve this pushkin.yaml file and this config.js file to migrate your existing site to work with the current version of the CLI.
4. If you were just making a test (no real customizations), then I would recommend just creating a new pushkin site. Be sure to use the basic site template, not the default site template, as the basic site template is the one that's going to allow you to test on Windows using your AWS EC2 instance.

Please let me know if you have any questions or need any more help.

[MelindaPozzi]

Hi!

Thank your for your answer! When I try to connect from Putty to my AWS EC2 instance, I got this error message:

So I can't even update Pushkin CLI.

[parkerrobbins]

So it looks like you don't have any space remaining on your instance. You can find information here about how to increase the amount of disk space on your EC2 instance.

[parkerrobbins]

You might find this tutorial a bit easier than reading the AWS docs.

[jkhartshorne]

@parkerrobbins - since this has come up a few times, do you think it makes sense to add something to the FAQ?

[parkerrobbins]

@jkhartshorne Definitely. I'll add an issue.

[MelindaPozzi]

Hi again!

I've followed all your instructions and it finally works!

Thank you very much for your help!
Mélinda

[jkhartshorne]

Awesome!

[restmegan]

Hi @MelindaPozzi ! I just wanted to check in to see how Pushkin has been going for you. The Pushkin team is online today answering questions so if there's anything you need help with please let us know!

[MelindaPozzi]

Hi @restmegan,

Thank you for asking ! I could solve all the issues thanks to the team's answers, so everything is fine for me.

A big thank you to all the team for this worshop!
Mélinda