Benvenuto

Ciao BDavis (WMF)!

Benvenuta/o su Wikivoyage in lingua italiana! Stiamo realizzando un'attendibile guida turistica mondiale libera e aggiornabile. Aiutaci anche tu! Se hai appena conosciuto Wikivoyage e non sai come funziona e in che modo puoi aiutarci, poni le tue domande nella Lounge, il punto d'incontro dei wikiviaggiatori, oppure consulta le nostre pagine di aiuto.

Potrai trovare risposte ai tuoi dubbi anche nelle pagine delle domande frequenti e dei consigli per i nuovi arrivati.

Ricordati soprattutto che è vietato copiare testi protetti da copyright. Il nostro obiettivo non è proporre contenuti copiati da altri siti, ma scrivere una nuova guida turistica di nostro pugno.
 


--Andyrom75 (discussioni) 21:04, 30 mag 2020 (CEST)Rispondi

Wikivoyage tool on Toolforge modifica

Hi Davis, I need support to get edit rights on the tool in the subject. I've been added as maintainer but I can't modified anything yet (see this discussion for more details). Please let me know, --Andyrom75 (discussioni) 21:10, 30 mag 2020 (CEST)Rispondi

[@ Andyrom], I created phab:T254107 to track this issue. Reporting issues with Toolforge through Phabricator is preferred to attempting 1-to-1 contact through User talk pages. --BDavis (WMF) (discussioni) 21:05, 31 mag 2020 (CEST)Rispondi
Thanks for get it done! Today I'll start to do some preliminary test, before studing some future improvements. --Andyrom75 (discussioni) 06:51, 1 giu 2020 (CEST)Rispondi
I hope you don't mind if I ask you a couple of basic info about the relationship between toolforge and Phabricator. Today I've changed a file in Phabricator as a mere test with GIT, but I don't see the relevant change on toolforge. On the other side, I've launched a script in toolforge that create a log file, but this log file is not visible on Phabricator. Could you explain me why and maybe which is the correct way to modify such files? --Andyrom75 (discussioni) 14:40, 1 giu 2020 (CEST)Rispondi
Andyrom75, by "Phabricator" I assume you mean a git repository hosted using the Diffusion component of phabricator.wikimedia.org. There is no system wide automation to sync changes in the authoritative git repo to a clone in a tool's $HOME in either direction. A typical workflow would be to make changes in a local git clone on your laptop, test those changes in any way you can locally, git push to send the changes from your laptop to the authoritative repo, ssh to login.toolforge.org, become wikivoyage, cd path/to/your/git/clone, git pull to update the local clone on Toolforge to match the current HEAD on the authoritative repo, and commonly finish with some sort of restart procedure for your bot or webservice to make it aware of the files that have changed on disk.
All of the details here are specific to the tool in question. I can't really generically tell you how your co-maintainers of the wikivoyage tool have set things up. You should really be asking them what workflows to use. And if you want to be a really great co-maintainer, take those answers, verify that they are correct, and preserve them on a page like wikitech:Tool:Wikivoyage along with other info that would useful for you and other co-maintainers to have when troubleshooting problems or onboarding another co-maintainer in the future. See other pages in wikitech:Category:Toolforge tools for examples of docs written for other tools. --BDavis (WMF) (discussioni) 19:35, 1 giu 2020 (CEST)Rispondi
Thanks for clarifing the confusion that my words created around Diffusion. Now I got that these two environment are independents. Now with my GIT, I'm able to interact correctly with Diffusion. Unfortunately I'm not able to do the same with toolforge using putty; I've followed these instructions ... or at least I've tried... but without success. Any suggestion? Currently I'm using the same SSH keys that I've created for Diffusion; do I have to create a new set with PuTTYgen? --Andyrom75 (discussioni) 12:31, 3 giu 2020 (CEST)Rispondi