Skip to content

Conversation

@saltonmassally
Copy link
Contributor

demo plan is then spurned every 24 hours. Consequently you can have a demontration database that is refreshed every 24 hours

demo plan is then spurned every 24 hours. Consequently you can have a demontration database that is refreshed every 24 hours
@yelizariev
Copy link
Contributor

@tarzan0820 , could you explain why the module has name "SaaS Portal Demo Template"?
I thought to create new database each time when user need a demo. Your solution can saves resources.
But in your approach there could be only one demo database. What do you think about adding option "Refresh periodically" directly to saas_portal.client?
Then your module could have a name saas_portal_refresh_db or like that

@saltonmassally
Copy link
Contributor Author

@yelizariev I agree with you that the naming is a bit off... the whole idea is to have a demo database that is refreshed periodically (as should be the case for a open demonstration instance)... I will rename to saas_portal_refresh_db

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants