Closed giannidallatorre closed 1 year ago
Available at https://docs.egi.eu/documentation/544
Available at https://docs.egi.eu/documentation/544
Available at https://docs.egi.eu/documentation/544
Available at https://docs.egi.eu/documentation/544
Available at https://docs.egi.eu/documentation/544
Available at https://docs.egi.eu/documentation/544
Available at https://docs.egi.eu/documentation/544
Available at https://docs.egi.eu/documentation/544
Available at https://docs.egi.eu/documentation/544
I think this is quite useful information, but it would be good to also link it more with other resources available: we have documentation on using ansible, terraform, a page about using the Infrastructure Manager... It also relates a bit to #547, but maybe the security-related aspects will better be in a dedicated page.
Sure, feel free to do what you like with the page and thanks for having reviewed and improved it. I had to write a few emails on the topics and I thought it may be good to collect the info together into a single page and clean it up a bit. So yes I am sure it can be better integrated with the rest of the documentation, I didn't really think about that. I will try to do that, but I need to find some time to improve my local set-up first if I want to contribute more to the documentation. The style policies are quite restrictive and fixing them after a pool request is time-consuming, so I need to check my vim configuration (which is quite dirty) and make the linter and checks work locally.
The style policies are quite restrictive and fixing them after a pool request is time-consuming, so I need to check my vim configuration (which is quite dirty) and make the linter and checks work locally.
Yes, if you are using vim/neovim, a proper vim configuration is really helping a lot, mine (beware there are many plugins and it's also customised for my own env/desires) is managed using vim-plug and automatically running prettier on files I'm editing, so it's very convenient to get all the basic formatting done when saving a file. It's relying on ALE, cf https://prettier.io/docs/en/vim.html#alehttpsgithubcomdense-analysisale. See also https://docs.egi.eu/about/contributing/style/#automating-formatting-and-checking
Available at https://docs.egi.eu/documentation/544
Available at https://docs.egi.eu/documentation/544
Available at https://docs.egi.eu/documentation/544
@giannidallatorre for running tests locally you can look at https://github.com/EGI-Federation/documentation/issues/468 (not covering all tests, but allowing to test the main ones: markdown linting and link checking).
Available at https://docs.egi.eu/documentation/544
Available at https://docs.egi.eu/documentation/544
Available at https://docs.egi.eu/documentation/544
Available at https://docs.egi.eu/documentation/544
Available at https://docs.egi.eu/documentation/544
Available at https://docs.egi.eu/documentation/544
Available at https://docs.egi.eu/documentation/544
Available at https://docs.egi.eu/documentation/544
Available at https://docs.egi.eu/documentation/544
Available at https://docs.egi.eu/documentation/544
Available at https://docs.egi.eu/documentation/544
Available at https://docs.egi.eu/documentation/544
Available at https://docs.egi.eu/documentation/544
Available at https://docs.egi.eu/documentation/544
For now, we cannot replace the remaining links, so I guess we could bypass the errors and force the merge, and fix the links later, once we will know the new URLs.
Available at https://docs.egi.eu/documentation/544
Available at https://docs.egi.eu/documentation/544
Available at https://docs.egi.eu/documentation/544
Available at https://docs.egi.eu/documentation/544
The last broken link to be fixed seems to be https://www.egi.eu/federation/data-centres/, and we should have a new URL soon.
Available at https://docs.egi.eu/documentation/544
Available at https://docs.egi.eu/documentation/544
Available at https://docs.egi.eu/documentation/544
@glarocca @sebastian-luna-valero can you check this one?
See the :open_file_folder: files view or the :scroll:action log for details.
:steam_locomotive: If you're seeing this message and your PR is from a branch that doesn't have check-spelling, please merge to your PR's base branch to get the version configured for your repository.
See the :open_file_folder: files view or the :scroll:action log for details.
:steam_locomotive: If you're seeing this message and your PR is from a branch that doesn't have check-spelling, please merge to your PR's base branch to get the version configured for your repository.
See the :open_file_folder: files view or the :scroll:action log for details.
:steam_locomotive: If you're seeing this message and your PR is from a branch that doesn't have check-spelling, please merge to your PR's base branch to get the version configured for your repository.
See the :open_file_folder: files view or the :scroll:action log for details.
mytoken
To have the bot do this for you, reply quoting the following line: @check-spelling-bot apply updates.
Available at https://docs.egi.eu/documentation/544
Available at https://docs.egi.eu/documentation/544
Available at https://docs.egi.eu/documentation/544
Summary
New users are often not familiar with the networking & configuration requirements to set up an ssh connection with a VM hosted in OpenStack. Added a specific page in the Tutorial section to address the most important concepts and provide some general information.
Related issue :#543