-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
demo.tramline.app - Notes #762
Comments
Important Links: |
Other notes and links:
|
Old seed script that is much simpler: https://github.com/simpledotorg/simple-server/blob/a9caebff67d748ae1535097ca145744f862725de/app/jobs/seed_user_data_job.rb
Strategies
Sizing
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Context
Currently to help potential customers try out tramline, a throwaway "viewer" account via the rake task
create_external_viewer
Link. Some data from thestaging
/production
environment(s) is then anonymized and seeded for this new "viewer" account and given to the customer to try out.Potential Issues with the current approach
There are multiple reasons to why this is not an ideal approach to help new and potential customers to try the platform. I'm listing some down below:
staging
environment, this doesn't yield a very professional appearance to Tramline as we approach new prospects.is pretty annoying and time consuming. Since we also risk the data becoming stale and unusable after a certain point
staging
orproduction
environments is invasive and expensive.Hence having a dedicated
demo
will help alleviate these issues and alsostaging
|production
environmentsdemo
fresh and easy to get most information and context out of trying the appSteps involved to resolve this ticket
tramline
production
|staging
)demo
demo
siteOther notes
WIP
The text was updated successfully, but these errors were encountered: