Reply to thread

Yes, I too found that the pyLoad package would not work (just a bit after I posted the link), so began trying to work out how to adapt varkey's instructions right at the start of this thread to the new systemd service method of daemon startup.


These were the instructions I followed from varkey's original post (#2 on this thread):


1. pacman -Sy python2 python-pycurl


2. Create a symbolic link for python to python2

 

ln -s /usr/bin/python2 /usr/bin/python


3. Download and extract the pyLoad source package change the package version 0.4.9 to whatever is the latest and greatest pyLoad version:

 

wget http://download.pyload.org/pyload-src-v0.4.9.zip 


unzip pyload-src-v0.4.8.zip

 

4. Go to the folder in which pyLoad was extracted and run:

  

python pyLoadCore.py -s


5. Set the download path and login data etc. When it asks for type of webserver, choose 'threaded'


6. If you extracted the pyload files in step 3 to /home/pyload then run the following command (adjust the path depending on where the extract was done):

 

  

ln -s /home/pyload/pyLoadCore.py /usr/bin/pyLoadCore


Since the rest of the instructions were for the old method of daemon configuration (i.e.) initscript versus systemd service.  I just executed  /usr/bin/pyLoadCore --daemon and I now see the pyLoad login page at http:<IP>:8000


 Now to try and figure out how to create a systemd service file since  arch no longer uses the initscripts that were in varkey's instructions from a while ago.    This can be done through webmin or the cli, I guess. If you figure this out or someone else has this info, please post.