← Back to team overview

mvhub-dev team mailing list archive

[Bug 432885] Re: move_to_production.txt needs update when mvhub legacy moves to v3 code

 

** Visibility changed to: Public

** This bug is no longer flagged as a security vulnerability

** Description changed:

- -----BEGIN PGP SIGNED MESSAGE-----
- Hash: SHA1
- 
-  affects mvhub
-  importance low
-  milestone mvhub-production-to-v3
-  security no
-  security yes
-  status new
-  tag doc time-4-hrs-or-less
-  done
- 
- 
  When mvhub.com is using the v3 ( /var/www/mvhub/production )  code
  
  the checklist:
  
-         app-mvhub/doc/checklists/move_to_production.txt
+  app-mvhub/doc/checklists/move_to_production.txt
  
  ...will need to be updated, at least so that the db for production.mvh
  is dumped/loaded as production.nsp is
- -----BEGIN PGP SIGNATURE-----
- Version: GnuPG v1.4.9 (GNU/Linux)
- Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
- 
- iEYEARECAAYFAkq0Uq0ACgkQLzI3mETyffxi/wCeKS9KXVC8wcvP/TRlbbmly54z
- N58An3JDjisdG9NDEmnM4HfWkWPylHr1
- =Wvus
- -----END PGP SIGNATURE-----

-- 
move_to_production.txt needs update when mvhub legacy moves to v3 code
https://bugs.launchpad.net/bugs/432885
You received this bug notification because you are a member of mvhub-
dev, which is a direct subscriber.

Status in MVHub, a directory of social services: Confirmed

Bug description:
When mvhub.com is using the v3 ( /var/www/mvhub/production )  code

the checklist:

 app-mvhub/doc/checklists/move_to_production.txt

...will need to be updated, at least so that the db for production.mvh
is dumped/loaded as production.nsp is