Issues with the installation of scrapyd on Windows - windows

I am having issues with the installation of scrapyd on Wndows 7 I have installed the package using easy_install, but still the command scrapyd comes up with nothing. Here is the output of my install:
C:\Python27\Lib\site-packages\scrapy>easy_install scrapyd
Searching for scrapyd
Reading https://pypi.python.org/simple/scrapyd/
Best match: scrapyd 1.0.1
Downloading https://pypi.python.org/packages/source/s/scrapyd/scrapyd-1.0.1.tar.gz#md5=bc002742a938c40fa7e80f6743320c95
Processing scrapyd-1.0.1.tar.gz
Writing c:\users\uname\appdata\local\temp\easy_install-q7nfgz\scrapyd-1.0.1\setup.cfg
Running scrapyd-1.0.1\setup.py -q bdist_egg --dist-dir c:\users\uname\appdata\local\temp\easy_install-q7nfgz\scrapyd-1.0.1\egg-dist-tmp-ss3ual
no previously-included directories found matching 'docs\_build'
zip_safe flag not set; analyzing archive contents...
Adding scrapyd 1.0.1 to easy-install.pth file
Installing scrapyd script to C:\Python27\Scripts
Installing scrapyd-deploy script to C:\Python27\Scripts
Installed c:\python27\lib\site-packages\scrapyd-1.0.1-py2.7.egg
Processing dependencies for scrapyd
Finished processing dependencies for scrapyd
C:\Python27\Lib\site-packages\scrapy>scrapyd
'scrapyd' is not recognized as an internal or external command,
operable program or batch file.
Any ideas, what the issue is?

I am new here and I cannot comment. So perhaps it is not an answer but rather workaround.
Firstly, i am not sure if scrapyd works on windows at all. Please see this part of Scrapy documentation.
Personally, I develop on the Windows but deploy on Debian (where couldn't find the scrapyd package at all at the time I was working on it) and noticed that performance of scrapy is considerably worse than on linux box, so you might reconsider your target. But I digress.
However, you don't need scrapyd at all. Scrapyd is just a wrapper that keeps running scrapy server in background. To get same functionality you can run from commandline (from the scrapy project folder):
scrapy server
The scrapy server would be then running as long as the commandline is running but you can workaround this with bat file and some software to running tasks in background. Hope it helps.

Solution:
Starting scrapyd on Windows 7 [after installation] from console:
cd to Python_install_dir/Scripts and run scrapyd from python.
In my case:
1.) cd C:\Python27\Scripts
2.) C:\Python27\Scripts> python scrapyd
now you can connect to scrapyd:
http://127.0.0.1:6800/ & via console
If you wanna running the server in the background, just run this command as a windows background process.

Related

Error Building and installing local chainlink node, when running make install - windows

I am trying to create a local chainlink oracle node, for testing and learning purposes. Using windows 10.
I followed the steps listed on the https://github.com/smartcontractkit/chainlink#install
to install a local chainlink node.
Already installed Go, nodeJS, nvm, yarn, postgres (all latest version as of 21/11/04. All ruuning from root).
Downloaded the Chainlink executing: git clone https://github.com/smartcontractkit/chainlink && cd chainlink
changed the directory to C:\chainlink
and ran make install command to build and install the node.
Got the error:
'make' is not recognized as an intern or extern command, operable program or a batch file
What am I doing wrong?
(Apparently, make install is a command that works for mac command line, I am using windows instead)
Working on Windows, the easiest method of running a node would be to use docker and download the docker image as described in the Chainlink docs.
Make is a UNIX based command and will require either using a virtual UNIX/Linux environment, using a tool like Cgywin or WSL as discussed in this post.

Unable to install or run Octave in a Windows docker container

I'm trying to create a Windows docker container image with Octave (CLI) installed.
I started off with a Dockerfile installing Octave via chocolatey:
FROM mcr.microsoft.com/windows/servercore:1809
# Install chocolatey
RUN ["powershell", "Set-ExecutionPolicy Bypass -Scope Process -Force; iex ((New-Object System.Net.WebClient).DownloadString('https://chocolatey.org/install.ps1'))"]
# Install Octave
RUN ["powershell", "choco install --yes octave"]
Unfortunately the Octave install times out after 2700 seconds, while on my local machine this takes less than 10 minutes.
Progress: 100% - Completed download of C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\octave.install\5.1.0\octave-5.1.0-w64-installer.exe (286.41 MB).
Download of octave-5.1.0-w64-installer.exe (286.41 MB) completed.
Hashes match.
Installing octave.install...
Chocolatey timed out waiting for the command to finish. The timeout
specified (or the default value) was '2700' seconds. Perhaps try a
higher `--execution-timeout`? See `choco -h` for details.
The install of octave.install was NOT successful.
Error while running 'C:\ProgramData\chocolatey\lib\octave.install\tools\chocolateyinstall.ps1'.
See log for details.
In my second trial I ran a Windows servercore container, copied the Octave installer binary into there and tried to run it, however the start call unfortunately immediately returns with error code -1073741515.
My third trial was downloading the portable Octave version and copy it into a running Windows servercore container, copy the portable Octave and run it. Unfortunately when calling octave-cli.exe the call again returns immediately with error code -1073741515.
I then checked with dependency walker, on my local machine, which dependencies the octave-cli has, it seemed to depend on adoptopenjdk\jdk-14.0.1.7. In my last trial I installed this dependency in the Windows servercore container via choco install adoptopenjdk, this however resulted in the same error code.
I'm curious whether anybody did succeed in installing or running Octave into a Windows docker container?
Or does anyone have any hints for me to proceed?

Specifying JupyterHub Path Variable

I am in the process of installing jupyterhub. I successfully install jupyterhub using:
python3 -m pip install jupyterhub
npm install -g configurable-http-proxy
However, when I run jupyterhub -h in the Windows command prompt it gives:
"jupyterhub" is not recognized as an internal or external command, operable
program or batch file.
I added C:\Users\User\AppData\Local\Continuum\Anaconda3\Lib\site-packages\jupyterhub\ to my user environment variable, however still receive the message. What path should I be using?
Please note that according to this, Jupyterhub is not officially supported for Windows yet.
That aside, you could dockerize it to make your life easier. For this error, please check if you can see the executable in C:\Program Files\Continuum Analytics\Anaconda3\scripts. The lib directory you're specifying contains python source files and not the executables.
I had this same issue, and I saw this occurred because jupyterhub is a python script rather than an executable. So to run this on Windows I needed to execute it like python C:\Program Files\Continuum Analytics\Anaconda3\scripts\jupyterhub.
However, I still was unable to run jupyterhub on Windows because it depends on the pwd module, which is a Unix/Linux only module.
As others have said, Windows is not a supported platform. JupyterHub is best used on Linux-like platforms where you have Docker or something similar to conatainerize each user's session.
A good alternative is to install Oracle VirtualBox and run a local VM. I run a 64-bit Ubuntu and it's quite good performance. It makes things much easier to run JupyterHub on. Asides depending on pwd, there are also assumptions around user-creation and other activities that Windows isn't going to handle well.
In short, if you want to run on native Windows, you're going to become the first JupyterHub Windows contributor. I looked at doing it but it looked like too much effort.
The upside of running a VM is that behaviour in the VM is going to more closely resemble what you have running on the server anyway. If you don't plan running on a server, then just "jupyter notebook", as this is all JupyterHub ends up running...

Tor console output issue: running tor --hash-password gives no result

I'm following the blog post here.
I'm using a Windows machine, so I can't follow the exact steps. This is what I've done:
Installed the Tor Browser for Windows
Installed pytorctl
pip install git+https://github.com/aaronsw/pytorctl
Installed Privoxy
Attempted to use the Tor command line. I'm assuming it is the exe file in the directory "Tor Browser\Browser\TorBrowser\Tor"
tor --hash-password *mypassword*
Unfortunately, this command runs but there is no response.
If anyone has any suggestions, much would be appreciated. Do you think this could be a firewall issue?
Apparently this is a known bug that when your run tor.exe from the command line it is running but opens in a hidden window. To get around this, run the following: tor --hash-password *your_password* | more. Hopefully this works. See more about the issue here.

Unable to get Docpad to run on Windows

I'm having problems getting Docpad to run on Windows.
I did the following.
Installed the latest version of Node
"NPM Install Docpad"
Then typed "docpad run" in an empty directory
I got an error message that said 'docpad' is not recognized as an internal or external command,
operable program or batch file.
Maybe I'm missing a step somewhere? I've also tried submitting the command to the node command prompt, and have also checked the troubleshooting guide and done a general google search.
Unless you installed an NPM module with the -g option (which is not indicated in the docpad web site so I suspect you didn't) the module won't be available on your PATH.
You can still run it by indicating the full path, for example run the following from the folder where you ran the npm install command:
node_modules\.bin\docpad.cmd
I had this same problem and a restart didn't help me.
What worked for me was installing via the 'nodejs command prompt' rather than the standard windows one.
I ran npm install -g docpad then navigated to my empty folder and ran docpad run and it worked straight away (after 1 hour messing around with the windows command prompt).

Resources