Skip to content

Added update dependencies in readme.md #471

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
softyoda wants to merge 3 commits into from
Closed

Added update dependencies in readme.md #471

softyoda wants to merge 3 commits into from

Conversation

@softyoda
Copy link

@softyoda softyoda commented Sep 9, 2022

Added the info on how to update conda environment "conda env update --file environment.yaml"

havardgulldahl and others added 3 commits September 6, 2022 07:07
@havardgulldahl
Add instructions on how to install alongside pyenv (#393)
dbc8fc7 
Like probably many others, I have a lot of different virtualenvs, one for each project. Most of them are handled by `pyenv`. 
After installing according to these instructions I had issues with ´pyenv`and `miniconda` fighting over the $PATH of my system.
But then I stumbled upon this nice solution on SO: https://stackoverflow.com/a/73139031 , upon which I have based my suggested changes.

It runs perfectly on my M1 setup, with the anaconda setup as a virtual environment handled by pyenv. 

Feel free to incorporate these instructions as you see fit. 

Thanks a million for all your hard work.
@hvanmegen
Disabled debug output (#436)
049ea02 
Co-authored-by: Henry van Megen <hvanmegen@gmail.com>
@Niek
Fix macOS pyenv instructions, add code block highlight (#441)
79ac0f3 
Fix: `anaconda3-latest` does not work, specify the correct virtualenv, add missing init.
@softyoda
Copy link
Author

softyoda commented Sep 9, 2022

I may have failed my pulled request, the aim of this pr was to add

You may also update the environment dependencies via this command:

<markdown code balise>
(ldm) ~/stable-diffusion$ conda env update --file environment.yaml
<markdown code balise>

at line 520 of the readme.md

@tildebyte
Copy link
Contributor

tildebyte commented Sep 9, 2022

@softyoda; It looks like you're trying to open a PR using the GitHub Editor (which is mostly OK). Please close this one, and try again, but base it on the 'development' branch, instead of 'main'.

That is; from the main page of the repo, click where it says 'main' (just below "< Code >"), and select 'development' from the list. THEN you can edit the README and start a new PR.

Also, note that the marks you're looking for above, where you have

<markdown code balise>

should actually be

```

@softyoda
Copy link
Author

softyoda commented Sep 9, 2022 •
edited
Loading

I'm trying to found a way to simply edit (like wiki edition) without generating many forks, but yeah, sorry, I'm not used to it for now.

Also I can't insert ``` inside another markdown code balise (and doing \ ` `` doesn't work like escaping in python)

@softyoda softyoda closed this Sep 9, 2022
@tildebyte
Copy link
Contributor

tildebyte commented Sep 9, 2022

@softyoda; No worries! Thanks for trying. I'll open a PR with your changes.

@tildebyte tildebyte mentioned this pull request Sep 9, 2022
Merged
@tildebyte
Copy link
Contributor

tildebyte commented Sep 9, 2022

@softyoda; Opened #475 for you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

6 participants

@softyoda @tildebyte @havardgulldahl @hvanmegen @Niek