Skip to content
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.

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

Create new miniforge Blogpost #80

Merged
merged 6 commits into from
Jul 24, 2024
Merged

Create new miniforge Blogpost #80

merged 6 commits into from
Jul 24, 2024

Conversation

marabuuu
Copy link
Collaborator

@marabuuu marabuuu commented Jul 23, 2024

Hi @stefanhahmann,

Thank you for your input regarding this blog post. I decided to go with your suggestion

Perhaps, the cleanest solution would have been to actually write a new blog post (like we did, to document the changes from anaconda to mambaforge) and reference the new blog post from the current one (like the mambaforge blog post was referenced from the anaconda blog post).

Because if we change the link then we would need to update all the resources where we mentioned this blogpost and I think this installation blogpost was mentioned in several different resources, not only my own, but also for example Roberts and I would not have the overview in which of these resources I need to update the link.

Therefore, I created here a new PR as this was easier for me than modifying PR #79. Hope that is oki. If we merge this one, I will delete the other PR.

It would be cool if you could check if the link in the outdated blog post works for you that should link to the new blog post (https://biapol.github.io/blog/mara_lampert/getting_started_with_miniforge_and_python/Readme.html).

Just for documentation purposes

I updated the Miniforge blogpost again and it would be super cool if you could have a look at it.
I had a chat with Robert and there I found out that we don't need to write mamba ... anymore, but can simply use conda ....

And now, I was trying to find out if I can also remove the -c conda-forge from all commands and it seems to be ok, because according to the conda-forge documentation, conda-forge is the default channel of Miniforge.

I feel that these two changes make the installation instructions a bit easier to follow for python beginners, but I am always happy about your input and let me know if you want to have anything changed.

And I just saw that two Issues are still open regarding this blogpost that you Stefan and also Till already addressed, so I will add them here so they are closed when we merge this:
closes #73
closes #68

Best,
Mara

Copy link
Contributor

@stefanhahmann stefanhahmann left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks mostly good to me. I have suggested some minor changes below.

The link
https://biapol.github.io/blog/mara_lampert/getting_started_with_miniforge_and_python/Readme.html looks good to me. Whether it actually works, I can only check, once this PR is merged.

@stefanhahmann
Copy link
Contributor

stefanhahmann commented Jul 24, 2024

When this PR is merged, #79 can be closed.

@marabuuu
Copy link
Collaborator Author

Hi @stefanhahmann,

Thank you for your help and input. I hope I addressed everything now and I think we can merge this now.

Best,
Mara

@stefanhahmann stefanhahmann self-requested a review July 24, 2024 08:54
@stefanhahmann
Copy link
Contributor

Looks alright. Feel free to merge.

@marabuuu marabuuu merged commit e2c1af2 into master Jul 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants