-
Notifications
You must be signed in to change notification settings - Fork 217
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
Windows support for Frontera #282
Comments
Yes, Frontera wasn't tested/developed on Windows yet, but it could be. If you can, please submit a PR fixing this. |
Hello, is frontera version==0.8.1 support windows 10 platform now? What is the best platform to use the frontera? |
Linux! |
I am a student who trying to build a distributed crawler, and i have no experience of linux, but i willing to learn it. Besides, im a windows user for a long time. May i wish to get your suggestion which linux distros that is suits for Frontera and easy to use. Lastly, do you recommend me to install the linux using virtual box or alongside with my windows for development purpose? Thanks in advance! |
Ubuntu is usually a default choice in such cases. |
If you want to use Frontera on Windows, follow next steps.
Points 1-3 resolves issues with installing Twisted package and then will be also used to build CityHash. Points 8-11 installs python binding of CityHash for Windows. CityHash from pip does not compile on Windows (#367), and thus it cannot be installed through pip. Another way is to replace CityHash usage with some other library in Points 13-15 resolves issues occurring due to usage of Unix-specific signal SIGUSR1. It is used for debugging: a user can sent it to print current stack trace. This signal cannot be used on Windows. |
Hi, I'm trying to use the distributed mode of Frontera for a broad crawl but I am running into issues testing it on my local machine in windows. I am getting an import error (cannot import error name SIGUSR1) when I start a db worker due to SIGUSR1 not being available on windows. Would love if Frontera could develop a way that this software could be used on a windows machine and circumvent this issue.
The text was updated successfully, but these errors were encountered: