Our data is released under various Creative Commons licenses.More information
If you love this content, please consider a donation.
Menu
Have you ever considered contributing to Tatoeba as a developer? Whether you are a beginner or experienced, just curious or ready to go, every contribution to the code, small or big, is welcome.
I have been working at making things easier to contribute. It is now much easier to setup a local instance of Tatoeba and start working on something. In the past, while GNU/Linux users could use Imouto to install Tatoeba, people on Windows or Mac had to install everything manually. It is no longer the case as Imouto now works on Windows and Mac too, and is generally more solid.
How to get started: https://github.com/Tatoeba/tato...as-a-developer
I'm interested in helping out but unfortunately I won't have much time until September.
Excellent. Is there anything special you’d like to work on?
No, nothing special yet.
For a start, I've read all the issues and found some rather easy ones like https://github.com/Tatoeba/tatoeba2/issues/1884.
Looking forward to hearing from you in September :)
Meanwhile I try to tidy up a bit our issues...
I'm not good in PHP (not to mention framework), but I have some experience in JavaScript. The thing I really lack for is leisure time.
That’s very good! We definitely need help on the front-end part. Tatoeba’s front-end has been running for a long time with simple jQuery code. More recently, we started using AngularJS and Material to give it a more modern look and feel. Our ultimate goal is to make the website responsive. Some parts have been rewritten using AngularJS, like the registration form, but other parts like the Wall are still running with legacy jQuery code.
I'm very happy to see that we can do this on Windows. I had no problem getting Tatoeba to run locally, which was great. However, when I typed this command in my Run field:
\\172.19.119.178\tatoeba
Windows Security asked me for a username and password to log onto 172.19.199.178. I don't remember ever setting one up, so I'm not sure how to proceed.
Also, I opened Git Bash and tried to execute this command from the parent directory of the "imouto" directory:
git remote set-url origin git@github.com:<username>/tatoeba2.git
where I replaced "<username>" with my GitHub username. I got this:
fatal: not a git repository (or any of the parent directories): .git
Then I opened Git GUI and tried "Clone Existing Repository". However, I wasn't sure how to fill out the Source Location and Target Directory fields. I also tried "Open Existing Repository" but wasn't sure how to fill out the Repository field.
I could have filled out tickets for these, but wasn't sure that was the right way to go. I did fill out tickets for some genuine issues that I saw.
> Windows Security asked me for a username and password to log onto 172.19.199.178.
I had that problem too but this is something that should have been solved with:
https://github.com/Tatoeba/imou...4e5c379ea19cca
Maybe anonymous login is too unreliable on Windows... Which Windows version do you use by the way?
At least let's check if it works if you create a samba account.
From the imouto root directory, after doing `vagrant up` (which starts the VM), you can connect via SSH to the VM with `vagrant ssh`.
Once you are in the VM, use the command `sudo smbpasswd -a vagrant`. It will ask you to enter a password. You could press enter and have an empty password if you wish.
After that, try again to go to \\172.19.119.178\tatoeba, enter "vagrant" as username and the password you've set above.
The command `git remote set-url ...` is supposed to be executed from the Tatoeba source code folder that is inside the VM (which you can access via \\172.19.119.178\tatoeba, if it would work). The source code folder is otherwise located in ~/Tatoeba in the VM (after login in via SSH, you would just have to "cd Tatoeba").
Because by default, the git repository in the VM is pointing to the official Tatoeba git repository. But unless you have write access to that repository (like gillux or myself), you will not be able to push any change. So you have to change that URL and set it to your fork repository, which is done with the `git remote set-url ...` command.
Excellent! With those instructions, I was able to run:
- the "git remote set-url ..." command
- phpunit tests/TestCase/Model/Table/SentencesTableTest.php
- mysql tatoeba
on my Windows 10 machine. I assume that I won't need to execute the "sudo smbpasswd..." command again, right?
Also, we should tell how to get out of everything. It looks like "exit" works for everything I've tested. I added a note to indicate that you can use it to exit from MySQL.
I submitted a pull request where I updated the instructions to include the "vagrant ssh" and "sudo smbpasswd..." commands. However, I didn't mention that you could use SSH to execute the "git remote set-url" command because that was in an earlier section and I didn't want to do any rearranging on my own.
Many thanks for the help!
Actually, "exit" must not close everything down, because when I shut down the machine, Windows says that Virtual Box is still running and asks whether I want to shut down anyway.
This is still puzzling. In theory there should be no login at all. You should be able to go \\172.19.119.178\tatoeba as if it's a normal folder on your hard drive. I am on Windows 10 as well, and it works fine. I wonder what is different on your side... Perhaps some other hidden settings.
Actually, you could try to enter "\" as username and nothing for the password. I know it didn't work on my side when gillux suggested to me, but perhaps it will work on your side.
Cf. https://serverfault.com/questio...ic-samba-share
The post suggests there is a difference between Windows 10 Home and Pro. I have Windows 10 Pro. Perhaps you have Windows 10 Home.
In any case, you will indeed not need to run `sudo smbpasswd` again (unless you re-clone Imouto and create a new VM). We should probably just create a samba user during the VM setup, so that people who have the same issue as you don't have to run the command.
As for the pull request you mentioned, I think you only created a branch, not a pull request yet. But let's see first if login with "\" works for you. And if not, I think gillux will add the creation of the vagrant user in the VM setup. Then the instructions would just need to mention that if there's a credential popup on Windows, the user can either try "\" or "vagrant".
I'm also using Windows 10 Pro.
When I try to log in with "\" as the username (and nothing for the password), it just asks me for my username. I type in "vagrant" and it comes up fine, but then again it also comes up fine when I type "vagrant" without going through the "\" step.
I’m glad to know that you got things working! :-)
I can of course make it so that the VM already has a the smb account in case anonymous login doesn’t work. The only thing I’m worried about is how long Windows will remember the credentials you entered. It can be annoying if you have to enter them over and over.
About the "exit" command (or Ctrl+D), I personally consider such information as out of the scope of the documentation of Imouto. It feels like explaining how to clean the dishes in a cake recipe. Instead, I’d rather put a link to some tutorial about how to use the command line.
A link to information about the command line would be fine. I just think we should avoid telling someone how to get on without giving them a means to figure out how to get off (cleanly).