Shutting down while enabling a demo?

[jwbowers]

It seems like we are being charged about $1/day for the app engine. It would be nice to stop this drip of funds. I think that we still like the idea of having access to a demo of the technology, but we do not need the whole site to be running.

I think that the main charge is for the blobstore. So, perhaps we just can leave it running but with no data stored?

[rubenson]

Sounds reasonable to me.

On 2013-01-07, at 5:23 PM, "Jake Bowers" <[email protected]mailto:[email protected]> wrote:

It seems like we are being charged about $1/day for the app engine. It would be nice to stop this drip of funds. I think that we still like the idea of having access to a demo of the technology, but we do not need the whole site to be running.

I think that the main charge is for the blobstore. So, perhaps we just can leave it running but with no data stored?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/237.

[jwbowers]

It seems like I should delete the "Blobstore Stored Data" from both the en-followup and the "community-mapping' apps. At least, that would make us not have to continue to pay Google as far as I can tell. Can we treat one or other data.yaml files [I guess two of them] as "final" and then back them up both to dreamhost and to DVD and then delete the data that we are storing on the app engine?

[rubenson]

Hi,

What's the status of this? Is there anything needed from my end? I think amazon is still charging us as well...

Daniel

Daniel Rubenson | Associate Professor | Department of Politics | Ryerson University, Toronto
t: +1.416.979.5000 x4052 | w: www.politics.ryerson.ca/rubenson

Visiting Professor (2012-2013) | Centre d'études européennes | Sciences Po, Paris

On 2013-01-21, at 5:41 PM, Jake Bowers wrote:

It seems like I should delete the "Blobstore Stored Data" from both the en-followup and the "community-mapping' apps. At least, that would make us not have to continue to pay Google as far as I can tell. Can we treat one or other data.yaml files [I guess two of them] as "final" and then back them up both to dreamhost and to DVD and then delete the data that we are storing on the app engine?

—
Reply to this email directly or view it on GitHub.

[jwbowers]

Hi Daniel,

On the Google side, I think we need to delete any data that we are storing there. Ashlea, can you make sure that the latest/last data.yaml file(s) are in the CanadaContextDropbox folder? Basically, we should have all of the files that the Makefile uses to create its final files. If any data file for use in analysis is created outside the Makefile, then let me know and I'll add them to the Makefile --- the Makefile basically is like a record of what led to what. I'll try to burn a DVD containing those data and a snapshot of the work that we've done.

On the Amazon side, we could migrate from one account to another (perhaps mine). It looks like I have some new money that is expressly for spending on Amazon EC2-type services. That migration should probably be done by Mark, although I'd like to learn more about how to deal with the database and back it up somehow.

Jake

On Jan 26, 2013, at 6:05 AM, rubenson [email protected] wrote:

Hi,

What's the status of this? Is there anything needed from my end? I think amazon is still charging us as well...

Daniel

Daniel Rubenson | Associate Professor | Department of Politics | Ryerson University, Toronto
t: +1.416.979.5000 x4052 | w: www.politics.ryerson.ca/rubenson

Visiting Professor (2012-2013) | Centre d'études européennes | Sciences Po, Paris

On 2013-01-21, at 5:41 PM, Jake Bowers wrote:

It seems like I should delete the "Blobstore Stored Data" from both the en-followup and the "community-mapping' apps. At least, that would make us not have to continue to pay Google as far as I can tell. Can we treat one or other data.yaml files [I guess two of them] as "final" and then back them up both to dreamhost and to DVD and then delete the data that we are storing on the app engine?

—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub.

[rubenson]

Jake,

This all sounds good to me, thanks.

D

On 2013-01-26, at 3:33 PM, Jake Bowers wrote:

Hi Daniel,

On the Google side, I think we need to delete any data that we are storing there. Ashlea, can you make sure that the latest/last data.yaml file(s) are in the CanadaContextDropbox folder? Basically, we should have all of the files that the Makefile uses to create its final files. If any data file for use in analysis is created outside the Makefile, then let me know and I'll add them to the Makefile --- the Makefile basically is like a record of what led to what. I'll try to burn a DVD containing those data and a snapshot of the work that we've done.

On the Amazon side, we could migrate from one account to another (perhaps mine). It looks like I have some new money that is expressly for spending on Amazon EC2-type services. That migration should probably be done by Mark, although I'd like to learn more about how to deal with the database and back it up somehow.

Jake

On Jan 26, 2013, at 6:05 AM, rubenson [email protected] wrote:

Hi,

What's the status of this? Is there anything needed from my end? I think amazon is still charging us as well...

Daniel

Daniel Rubenson | Associate Professor | Department of Politics | Ryerson University, Toronto
t: +1.416.979.5000 x4052 | w: www.politics.ryerson.ca/rubenson

Visiting Professor (2012-2013) | Centre d'études européennes | Sciences Po, Paris

On 2013-01-21, at 5:41 PM, Jake Bowers wrote:

It seems like I should delete the "Blobstore Stored Data" from both the en-followup and the "community-mapping' apps. At least, that would make us not have to continue to pay Google as far as I can tell. Can we treat one or other data.yaml files [I guess two of them] as "final" and then back them up both to dreamhost and to DVD and then delete the data that we are storing on the app engine?

—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub.

[ARundlett]

Hi all,

Sorry for the delay - I've backed up all Makefile files on dropbox (unless they were already pushed to the CanadaContextPapers/data repository) except for a couple:
I cannot find survey-one.yaml or survey-two.yaml, although I do have the rda files. Not sure if the difference is important.
I also cannot find the following:
district-drawing-community-s1.csv
survey-one-id-latlon.csv
survey.one.redraw.csv

Finally, vote-compass-demographics.csv in the Makefile should be named vote-compass-ids.csv.

Thanks,
Ashlea

[jwbowers]

Ok. Mark, would you mind deleting the datastore on app engine? I think that since we have data.yaml as of Aug 20 in the Dropbox, we no longer need to store data on the app engine --- and that is what we are being charged for.
On Feb 4, 2013, at 4:06 PM, Ashlea Rundlett [email protected] wrote:

Hi all,

Sorry for the delay - I've backed up all Makefile files on dropbox (unless they were already pushed to the CanadaContextPapers/data repository) except for a couple:
I cannot find survey-one.yaml or survey-two.yaml, although I do have the rda files. Not sure if the difference is important.
I also cannot find the following:
district-drawing-community-s1.csv
survey-one-id-latlon.csv
survey.one.redraw.csv

Finally, vote-compass-demographics.csv in the Makefile should be named vote-compass-ids.csv.

Thanks,
Ashlea

—
Reply to this email directly or view it on GitHub.

[markmfredrickson]

Will do. I'll take care of it today or tomorrow.