hackoregon / civic-devops

Master collection point for issues, procedures, and code to manage the HackOregon Civic platform
MIT License
11 stars 4 forks source link

What to do with the civic-server repo - remove, deprecate? #190

Open MikeTheCanuck opened 6 years ago

MikeTheCanuck commented 6 years ago

In my quest to clean up deprecated/unused HackO resources, I stumbled across this repo: https://github.com/hackoregon/civic-server

Looking at the README.md contents, this sounds a whole lot like the never-completed attempt to publish all the 2017 frontend React sites in a single server-side application.

Now that we're publishing the 2017 React sites via http://2017.civicpdx.org/, there's no further need for this repo.

There are two alternatives:

  1. Delete the repo - it's confusing, unnecessary, and was never completed to the point of being a published, working app. However, it's unclear whether the site was production-ready and just never published via a Travis pipeline, or if it still doesn't quite work.
  2. Leave the repo but update the README significantly to make it clear that this is not an active repo, nor is it known to work in the kind of architecture we're currently operating the rest of our sites on. At the very least we should help outsiders know which assets we recommend, which are active, and which are legacy/deprecated.