search

c6fc / npk

A mostly-serverless distributed hash cracking platform
508 stars 59 forks source link

NPK / CloudShell Deployment Question #37

Closed bzekanovic closed 2 years ago

bzekanovic commented 2 years ago

I just deployed NPK in dev environment using new CloudShell deployment process without any issues. However, I'm not sure many users know that CloudShell local files do expire after 190 days if there is no activity within that user's CloudShell.

Do you think best practice would be to pull down /aws/mde/npk directory or do you have better ways to go about not losing NPK local files? Also, previous Docker deployment allowed other users to pull down the container and make changes / re-deploy NPK, but with CloudShell seems like only way is to pull down /aws/mde/npk directory and store that in S3.

c6fc commented 2 years ago

There's no need to save any part of what's created in the cloudshell. The npk-settings.json is automatically saved to S3, and the local files are generated on-demand. The only thing needed to re-create and re-attach a deployment from scratch is to run the one-liner.

Anyone with admin rights can run the CloudShell one-liner to modify an existing NPK installation

c6fc commented 2 years ago

In fact, best practice here is to delete the home directory and reset the CloudShell before running the one-liner, just to ensure that it's pristine. The one-liner is idempotent for both new and existing installs.