Skip to content

Instantly share code, notes, and snippets.

@smsohan

smsohan/PC Vangant.md

Last active July 30, 2018 19:04
Show Gist options
  • Save smsohan/582306bb7966c30e1dde409ba7868a02 to your computer and use it in GitHub Desktop.
Save smsohan/582306bb7966c30e1dde409ba7868a02 to your computer and use it in GitHub Desktop.
Download ZIP
Raw
PC Vangant.md

The goal is to reduce the overhead of a portal developer and QA working on PC. Vagrant is a great start in that direction. I suggest the following changes:

  1. Everything in git must be in Vagrant. .env is the only place where we should see local changes. No overrides for any other file.
  2. Files must sync between the host and the vm automatically. This applies to deleted files as well.
  3. Must work in dev and test mode so tests can be run easily.
  4. Env vars for paths must be set on login so that custom PC specific variables are preconfigured. e.g. LD_LIBRARY_PATH, PKG_CONFIG_PATH.
  5. By default, the portal in vagrant needs to run in development mode instead of production.
  6. On-demand QA deploy is needed so that QA can quickly verify dev fixes without having to wait for a periodic deploy.
  7. Automated clock sync between the VM and host machine so that Cookies don't expire because the VM has a time lag.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment