Ability to Delete Nuggets in Nugget List/Do Database Dump on Frontend

[chrisivester]

Per the title... Ability to Delete Nuggets in Nugget List/Do Database Dump on Frontend.

With all the testing we've been doing, we need a way to clear the database. This will also come in handy if something goes wrong with our auto upload script and we have 1000+ entries that we need to clear out.

Additionally, we need a way to delete nuggets on the nugget list. Will look to see if this is already a comment in the nugget list issue and delete here if this is true.

[jahio]

@chrisivester This should be done. It's shipping up to the server now. The way this works is you grab a nugget off the list, then click the toggle for "all database properties".

Once you've done that, scroll to the bottom and you'll see a big red button that has a warning under it and after you've clicked it:

I buried this under that toggle and with warnings so that nobody could "accidentally" click it. Tested in development, changes are minor and should work in production. Please confirm after testing.

As for purging ALL the nuggets from the database, prior to launch I plan to purge the entire DB by hand - just nuke the whole thing. We'll make a backup first "just in case", but I doubt we'll need it.

[jahio]

Actually, going to close this for now as I'm relatively certain this is complete. Re-open if I'm wrong. Thanks.

[chrisivester]

Austin,

This is complete. Is there any way that you can add a password protected feature to dump the database? I will need to dump data occasionally and need to be able to it access this via GUI.

-Chris

[jahio]

@chrisivester I've just shipped a simple feature to allow you to purge the database - everything but your users (so logins should still work). The way this works is you're going to have to login, click the "admin" button at the bottom, read the warning, type "purge" in the box to be sure you're not doing something by accident, and then press enter or click the purge button. You'll be prompted for ANOTHER username and password:

Username: chris Password: counterstrike

This is el-cheapo for now since it's not intended to be permanent, but it'll get the job done. I have not tested this in production yet because I don't know how much of that data you want kept, and I'm extremely paranoid about deleting data (which is why there's all the extra steps and warnings). Please give this a go and let me know how it turns out. Thanks.

[chrisivester]

Austin,

Sorry for delayed response... I haven't tested this feature yet, but I'll let you know if it is functioning properly when we have the need to clear the DB.

Thanks! Chris

On Sun, Feb 2, 2014 at 6:52 PM, J. Austin Hughey notifications@github.comwrote:

@chrisivester https://github.com/chrisivester I've just shipped a simple feature to allow you to purge the database - everything but your users (so logins should still work). The way this works is you're going to have to login, click the "admin" button at the bottom, read the warning, type "purge" in the box to be sure you're not doing something by accident, and then press enter or click the purge button. You'll be prompted for ANOTHER username and password:

Username: chris Password: counterstrike

This is el-cheapo for now since it's not intended to be permanent, but it'll get the job done. I have not tested this in production yet because I don't know how much of that data you want kept, and I'm extremely paranoid about deleting data (which is why there's all the extra steps and warnings). Please give this a go and let me know how it turns out. Thanks.

Reply to this email directly or view it on GitHubhttps://github.com/realmassive/prospector/issues/24#issuecomment-33918713 .

Chris Ivester | Launch Manager

512-426-9331 | RealMassive.com

-

This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. If verification is required please request a hard-copy version.

[chrisivester]

Hey Austin,

Was trying to purge the prospector database today, but the user/pass combo in the previous email is not working!

This is the use/pass combo I have to perform a purge:

Username: chris Password: counterstrike

-Chris

On Tue, Feb 4, 2014 at 4:39 PM, Chris Ivester <chris.ivester@realmassive.com

wrote:

Austin,

Sorry for delayed response... I haven't tested this feature yet, but I'll let you know if it is functioning properly when we have the need to clear the DB.

Thanks! Chris

On Sun, Feb 2, 2014 at 6:52 PM, J. Austin Hughey <notifications@github.com

wrote:

@chrisivester https://github.com/chrisivester I've just shipped a simple feature to allow you to purge the database - everything but your users (so logins should still work). The way this works is you're going to have to login, click the "admin" button at the bottom, read the warning, type "purge" in the box to be sure you're not doing something by accident, and then press enter or click the purge button. You'll be prompted for ANOTHER username and password:

Username: chris Password: counterstrike

This is el-cheapo for now since it's not intended to be permanent, but it'll get the job done. I have not tested this in production yet because I don't know how much of that data you want kept, and I'm extremely paranoid about deleting data (which is why there's all the extra steps and warnings). Please give this a go and let me know how it turns out. Thanks.

Reply to this email directly or view it on GitHubhttps://github.com/realmassive/prospector/issues/24#issuecomment-33918713 .

Chris Ivester | Launch Manager

512-426-9331 | RealMassive.com

-

This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. If verification is required please request a hard-copy version.

Chris Ivester Launch Manager www.RealMassive.com http://www.realmassive.com/ c: 512.426.9331 t: @realmassive

-

This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. If verification is required please request a hard-copy version.

[jahio]

Chris,

I've figured this one out. The problem is that the "cheap authentication" I put in place to prevent abuse by the public at large - the little login box that pops up when you first use the app - was getting in the way of the authentication on the "purge" action. I've just turned off the cheap auth for that specific action since you have to be logged in anyway (which requires the "cheap auth" in the first place anyway) so it's not a huge security risk at this point.

The database is being purged right now as we speak. It's a slow process because there's a lot in there and it's removing bunches of old junk from Amazon S3 as well (part of how this was engineered to begin with). Just know that in the future if you purge it, it could take a while (possibly hours depending on how much stuff is in there) before you see everything at zero on the dashboard.

[chrisivester]

Austin,

Thanks for getting this figured out!

-Chris

On Fri, Mar 14, 2014 at 2:57 AM, J. Austin Hughey notifications@github.comwrote:

Chris,

I've figured this one out. The problem is that the "cheap authentication" I put in place to prevent abuse by the public at large - the little login box that pops up when you first use the app - was getting in the way of the authentication on the "purge" action. I've just turned off the cheap auth for that specific action since you have to be logged in anyway (which requires the "cheap auth" in the first place anyway) so it's not a huge security risk at this point.

The database is being purged right now as we speak. It's a slow process because there's a lot in there and it's removing bunches of old junk from Amazon S3 as well (part of how this was engineered to begin with). Just know that in the future if you purge it, it could take a while (possibly hours depending on how much stuff is in there) before you see everything at zero on the dashboard.

Reply to this email directly or view it on GitHubhttps://github.com/realmassive/prospector/issues/24#issuecomment-37624055 .

Chris Ivester Launch Manager www.RealMassive.com http://www.realmassive.com/ c: 512.426.9331 t: @realmassive

-

This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. If verification is required please request a hard-copy version.

[jahio]

Going to mark this one as closed in GitHub now; re-open if you see issues.