750
edits
Phabricator/UpgradeProcess: Difference between revisions
Jump to navigation
Jump to search
no edit summary
(Indicate if a migration is necessary in deployment bugs) |
DaveLawrence (talk | contribs) No edit summary |
||
| Line 21: | Line 21: | ||
* Run: `docker build -t mozilla/phabext:test .` | * Run: `docker build -t mozilla/phabext:test .` | ||
2.4. In my | 2.4. In my demo clone, change `docker-compose.yml` file's `phabricator->image` to `mozilla/phabext:test` | ||
* make sure you do not override this in `docker-compose.override.yml` | * make sure you do not override this in `docker-compose.override.yml` | ||
2.5. Run `docker-compose up --build` in the ` | 2.5. Run `docker-compose up --build` in the `demo` directory. This will spin up all containers with an additional one called shell with arc installed. | ||
2.6. Make sure that the you configure your Firefox proxy to use the tinyproxy started on docker-ip:1090. | 2.6. Make sure that the you configure your Firefox proxy to use the tinyproxy started on docker-ip:1090. | ||
| Line 31: | Line 31: | ||
2.7. Go to http://phabricator.test in firefox - you should get an error message about a MySQL upgrade if this upgrade cycle had any. | 2.7. Go to http://phabricator.test in firefox - you should get an error message about a MySQL upgrade if this upgrade cycle had any. | ||
2.8 Upgrade database: | 2.8 Upgrade database: Shell into demo phabricator (`docker exec -it demo_phabricator_1 /bin/sh`), run db migration: `phabricator/ $ ./bin/storage upgrade` | ||
3. The upgrade mechanic performs a simple smoke test: start up the phabricator.test container and log in, post a revision, accept the revision, verify that the attachment is created and r+ed in BMO. | 3. The upgrade mechanic performs a simple smoke test: start up the phabricator.test container and log in, post a revision, accept the revision, verify that the attachment is created and r+ed in BMO. | ||