Migration of the demo app to a new IBM Cloud account

[amfred]

• Will need the account access info first
• Next, try re-deploying Docker containers in Kube
• Would it be possible to do a backup of the Cloudant DB in the old account and a restore into the new account? - Looking into that
• Once the pieces are deployed, re-wire everything to use the new connection info
• Update the READMEs and docs to point to the new demo systems

[krook]

@amfred @upkarlidder are we still working through this?

[github-actions]

👋 Hi! This issue has been marked stale due to inactivity. If no further activity occurs, it will automatically be closed.

[amfred]

I'm not sure if we're still working through this or not because I've been off the grid for a few weeks. @upkarlidder and @yochanah might know.

[upkarlidder]

Yes. This is still being worked on. Thank you @amfred

[amfred]

It looks like the bot auto closed it even though we commented on it. Is it necessary to remove the stale tag as well?

[upkarlidder]

Thanks @amfred. As per the docs, it is supposed to remove the stale label and restart the close timer if you comment on a stale issue. It does not seem to work though.

The configuration must be on the default branch and the default values will:
- Add a label "Stale" on issues and pull requests after 60 days of inactivity
- Close the stale issues and pull requests after 7 days of inactivity
- If an update/comment occur on stale issues or pull requests, the stale label will be removed and the timer will restart

I believe the stale strategy is good, but we do not want to close the issues. How about I increase the number of days before closing a stale issue to 365. Is that a good workaround?

@demilolu

[github-actions]

👋 Hi! This issue has been marked stale due to inactivity. If no further activity occurs, it will automatically be closed.

[github-actions]

👋 Hi! This issue has been marked stale due to inactivity. If no further activity occurs, it will automatically be closed.