Closed tlvu closed 3 years ago
Current instructions (https://github.com/Ouranosinc/pavics-sdi/blob/8b071057f76f80fae08764a21dd2560a89dad4f9/docs/source/dev/installation.rst#pavics-installation-with-docker-compose) still refer to the old private PAVICS repo. The new public birdhouse-deploy repo has replaced that old PAVICS repo.
New features (Vagrant, autodeploy) are not mentioned.
Also there are documentations directly in the birdhouse-deploy repo (https://github.com/bird-house/birdhouse-deploy/blob/5c5813677951247890f32ea07366c4ba75b61f5f/birdhouse/README.md) which is closer to the code and easier to update as the code changes.
Should we point the documentation here in pavics-sdi to the documentation in birdhouse-repo to avoid duplication of documentation?
Is there another place in this repo or in another repo that still reference to the old private PAVICS repo?
Ok, let's move installation documentation to birdhouse-deploy and point to it.
Current instructions (https://github.com/Ouranosinc/pavics-sdi/blob/8b071057f76f80fae08764a21dd2560a89dad4f9/docs/source/dev/installation.rst#pavics-installation-with-docker-compose) still refer to the old private PAVICS repo. The new public birdhouse-deploy repo has replaced that old PAVICS repo.
New features (Vagrant, autodeploy) are not mentioned.
Also there are documentations directly in the birdhouse-deploy repo (https://github.com/bird-house/birdhouse-deploy/blob/5c5813677951247890f32ea07366c4ba75b61f5f/birdhouse/README.md) which is closer to the code and easier to update as the code changes.
Should we point the documentation here in pavics-sdi to the documentation in birdhouse-repo to avoid duplication of documentation?
Is there another place in this repo or in another repo that still reference to the old private PAVICS repo?