Skip to content
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

Improve and document how to easily "archive" previous years #748

Open
6 tasks
abraham opened this issue Mar 10, 2020 · 0 comments · May be fixed by #2172
Open
6 tasks

Improve and document how to easily "archive" previous years #748

abraham opened this issue Mar 10, 2020 · 0 comments · May be fixed by #2172
Assignees
Labels
enhancement New feature or request help wanted Contributions welcome

Comments

@abraham
Copy link
Member

abraham commented Mar 10, 2020

It should be easier to keep previous years conferences sites around. I'm thinking the approach should be to copy all the data to another Firebase project excluding the blog posts which should stay on the main site. Some things to include:

  • npm script to copy entire database from one project to another
  • npm script to copy images from one project to another
    • links in the database will not be updated
  • Simplify pointing/redirecting blog to another site
  • disable/clear schedule on current site
  • Git repo branching suggestions
  • Documentation page describing process
@abraham abraham added the enhancement New feature or request label Mar 10, 2020
@abraham abraham self-assigned this Mar 10, 2020
@abraham abraham added the help wanted Contributions welcome label Apr 3, 2020
@abraham abraham mentioned this issue Apr 4, 2020
@abraham abraham linked a pull request Jan 29, 2022 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Contributions welcome
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant