When running pipenv install, a new Pipfile is created in the root directory. If you then install a Pinax starter project, the project directory will also contain a Pipfile. If you try to use the --location flag to install the Pinax starter project in the root directory, the Pipfile already exists, which creates a conflict. I have tried several ways to get the dev version of team-wiki project up and running easily, but couldn't do it. I was not able to use pipenv install a second time to install the dependencies. I had to install some manually.
One possible solution, given by a member of our Slack, is to set the pipenv variable 'PIPENV_NO_INHERIT' in the environment parent directory so that it uses the Pipfile within the current directory. Poetry has also been mentioned but it appears that this replaces Pipfile.
When running
pipenv install, a new Pipfile is created in the root directory. If you then install a Pinax starter project, the project directory will also contain a Pipfile. If you try to use the--locationflag to install the Pinax starter project in the root directory, the Pipfile already exists, which creates a conflict. I have tried several ways to get the dev version of team-wiki project up and running easily, but couldn't do it. I was not able to usepipenv installa second time to install the dependencies. I had to install some manually.One possible solution, given by a member of our Slack, is to set the pipenv variable 'PIPENV_NO_INHERIT' in the environment parent directory so that it uses the Pipfile within the current directory. Poetry has also been mentioned but it appears that this replaces Pipfile.