how to install? #8

Closed
opened 2018-05-15 10:20:40 +02:00 by dirsigler · 20 comments
dirsigler commented 2018-05-15 10:20:40 +02:00 (Migrated from github.com)

Hey Lachs0r, thanks for this tool!

Could you provide more information how to set up the requirments and install the uwsgi config?

Thanks

Hey Lachs0r, thanks for this tool! Could you provide more information how to set up the requirments and install the uwsgi config? Thanks
T0MuX commented 2018-11-08 11:49:51 +01:00 (Migrated from github.com)

Hi, same question here ^^

I would like to install this service on my own VPS, but the way to install it is not enough clear for me. What we have to do to install it ?

Thank you by advance

Hi, same question here ^^ I would like to install this service on my own VPS, but the way to install it is not enough clear for me. What we have to do to install it ? Thank you by advance
akash-joshi commented 2018-12-31 04:58:43 +01:00 (Migrated from github.com)

Do this after cloning this repo on your server :

pip install requirements.txt
python fhost.py

Lemme know if this works 👍

Do this after cloning this repo on your server : ``` pip install requirements.txt python fhost.py ``` Lemme know if this works :+1:

On Monday, December 31, 2018 4:58:43 AM CET Akash Joshi wrote:

Do this after cloning this repo on your server :

pip install requirements.txt
python fhost.py

Lemme know if this works 👍

Ugh, the requirements.txt has horribly outdated versions in it. I never
thought of updating this because I’m just using openSUSE’s Python packages.

Also, never EVER use pip to install modules system-wide. You WILL regret it.

On Monday, December 31, 2018 4:58:43 AM CET Akash Joshi wrote: > Do this after cloning this repo on your server : > ``` > pip install requirements.txt > python fhost.py > ``` > Lemme know if this works :+1: Ugh, the requirements.txt has horribly outdated versions in it. I never thought of updating this because I’m just using openSUSE’s Python packages. Also, never EVER use pip to install modules system-wide. You WILL regret it.
akash-joshi commented 2018-12-31 06:36:45 +01:00 (Migrated from github.com)

The better pip install seems to be

pip install --upgrade -r requirements.txt

Also, I use virtualenv

The better pip install seems to be ``` pip install --upgrade -r requirements.txt ``` Also, I use virtualenv
akash-joshi commented 2018-12-31 06:59:28 +01:00 (Migrated from github.com)
Traceback (most recent call last):
  File "fhost.py", line 10, in <module>
    from magic import Magic
  File "C:\nodeapps\ENV\lib\site-packages\magic.py", line 173, in <module>
    raise ImportError('failed to find libmagic.  Check your installation')
ImportError: failed to find libmagic.  Check your installation

libmagic isn't being detected, even after being installed via pip

``` Traceback (most recent call last): File "fhost.py", line 10, in <module> from magic import Magic File "C:\nodeapps\ENV\lib\site-packages\magic.py", line 173, in <module> raise ImportError('failed to find libmagic. Check your installation') ImportError: failed to find libmagic. Check your installation ``` libmagic isn't being detected, even after being installed via pip
dijit commented 2018-12-31 13:33:03 +01:00 (Migrated from github.com)

Libmagic needs to be installed from your OS packages. The python module for libmagic just wraps the shared object file that is provided from the apt/rpm package called “libmagic”

Sent from iFruit 9x

On 31 Dec 2018, at 05:59, Akash Joshi notifications@github.com wrote:

Traceback (most recent call last):
File "fhost.py", line 10, in
from magic import Magic
File "C:\nodeapps\ENV\lib\site-packages\magic.py", line 173, in
raise ImportError('failed to find libmagic. Check your installation')
ImportError: failed to find libmagic. Check your installation
libmagic isn't being detected, even after being installed via pip


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Libmagic needs to be installed from your OS packages. The python module for libmagic just wraps the shared object file that is provided from the apt/rpm package called “libmagic” Sent from iFruit 9x > On 31 Dec 2018, at 05:59, Akash Joshi <notifications@github.com> wrote: > > Traceback (most recent call last): > File "fhost.py", line 10, in <module> > from magic import Magic > File "C:\nodeapps\ENV\lib\site-packages\magic.py", line 173, in <module> > raise ImportError('failed to find libmagic. Check your installation') > ImportError: failed to find libmagic. Check your installation > libmagic isn't being detected, even after being installed via pip > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub, or mute the thread.
akash-joshi commented 2019-01-01 05:37:18 +01:00 (Migrated from github.com)

Ahh shite, libmagic is not available on Windows. Maybe update the README with compatible OSs ?

Ahh shite, libmagic is not available on Windows. Maybe update the README with compatible OSs ?

On Tuesday, January 1, 2019 5:37:18 AM CET Akash Joshi wrote:

Ahh shite, libmagic is not available on Windows. Maybe update the README
with compatible OSs ?

Shouldn’t it be obvious that Windows is the worst possible OS to use for a
server?

On Tuesday, January 1, 2019 5:37:18 AM CET Akash Joshi wrote: > Ahh shite, libmagic is not available on Windows. Maybe update the README > with compatible OSs ? Shouldn’t it be obvious that Windows is the worst possible OS to use for a server?

You are right about that. As would a thorough refactoring to get rid of some cruft and unmaintained/obsolete dependencies.

You are right about that. As would a thorough refactoring to get rid of some cruft and unmaintained/obsolete dependencies.
T0MuX commented 2019-01-03 23:40:17 +01:00 (Migrated from github.com)

Do this after cloning this repo on your server :

pip install requirements.txt
python fhost.py

Lemme know if this works

Hi ! thank you to answer me :)

First, the install worked this way :

pip install --user `cat requirements.txt`

Second, yes : it worked. this way :

python fhost.py runserver

Tested with curl 127.0.0.1:5000 from the server, but unable to connect remotly. I have to deal with my vhosts and cname lol.

> Do this after cloning this repo on your server : > > ``` > pip install requirements.txt > python fhost.py > ``` > Lemme know if this works Hi ! thank you to answer me :) First, the install worked this way : ``` pip install --user `cat requirements.txt` ``` Second, yes : it worked. this way : ``` python fhost.py runserver ``` Tested with `curl 127.0.0.1:5000` from the server, but unable to connect remotly. I have to deal with my vhosts and cname lol.

On Thursday, January 3, 2019 11:40:18 PM CET T0MuX wrote:

Tested with curl 127.0.0.1:5000 from the server, but unable to connect
remotly. I have to deal with my vhosts and cname lol.

Yes, this is because that’s just the development server. You should NOT expose
that to the public. Use an application server like uwsgi behind nginx.

On Thursday, January 3, 2019 11:40:18 PM CET T0MuX wrote: > Tested with `curl 127.0.0.1:5000` from the server, but unable to connect > remotly. I have to deal with my vhosts and cname lol. Yes, this is because that’s just the development server. You should NOT expose that to the public. Use an application server like uwsgi behind nginx.
mngad commented 2019-02-08 17:20:55 +01:00 (Migrated from github.com)

On Thursday, January 3, 2019 11:40:18 PM CET T0MuX wrote: Tested with curl 127.0.0.1:5000 from the server, but unable to connect remotly. I have to deal with my vhosts and cname lol.
Yes, this is because that’s just the development server. You should NOT expose that to the public. Use an application server like uwsgi behind nginx.

Any chance you could point me in the direction of how to do this (uwsgi)?

> On Thursday, January 3, 2019 11:40:18 PM CET T0MuX wrote: Tested with `curl 127.0.0.1:5000` from the server, but unable to connect remotly. I have to deal with my vhosts and cname lol. > Yes, this is because that’s just the development server. You should NOT expose that to the public. Use an application server like uwsgi behind nginx. Any chance you could point me in the direction of how to do this (uwsgi)?
jusdepatate commented 2019-12-07 21:36:39 +01:00 (Migrated from github.com)

On Thursday, January 3, 2019 11:40:18 PM CET T0MuX wrote: Tested with curl 127.0.0.1:5000 from the server, but unable to connect remotly. I have to deal with my vhosts and cname lol.
Yes, this is because that’s just the development server. You should NOT expose that to the public. Use an application server like uwsgi behind nginx.

So there's no way to install 0x0 without nginx ? As i've read on uwsgi's doc using it on Apache2 is a bad idea

> On Thursday, January 3, 2019 11:40:18 PM CET T0MuX wrote: Tested with `curl 127.0.0.1:5000` from the server, but unable to connect remotly. I have to deal with my vhosts and cname lol. > Yes, this is because that’s just the development server. You should NOT expose that to the public. Use an application server like uwsgi behind nginx. So there's no way to install 0x0 without nginx ? As i've read on uwsgi's doc using it on Apache2 is a bad idea
T0MuX commented 2019-12-27 11:37:43 +01:00 (Migrated from github.com)

I can't make this to work correctly, even with nginx correctly configured anyway.

  1. When I upload a file, it returns the wrong adress : http://0.mux.re/a.ext instead of https://0.mux.re/a.ext, never understood why.
  2. None of the two adresses is working. The http one because there is nothing on http://0.mux.re, so normal, and the https one no idea what is going wrong.
    On the server side I have 127.0.0.1 - - [27/Dec/2019 11:32:12] "POST / HTTP/1.0" 400 - and on the client side I have Segmentation fault. And again, don't understand why because earlier it was returning an url in http and this url wasnt the good one, and not working even renaming in https.
I can't make this to work correctly, even with nginx correctly configured anyway. 1) When I upload a file, it returns the wrong adress : http://0.mux.re/a.ext instead of https://0.mux.re/a.ext, never understood why. 2) None of the two adresses is working. The http one because there is nothing on http://0.mux.re, so normal, and the https one no idea what is going wrong. On the server side I have `127.0.0.1 - - [27/Dec/2019 11:32:12] "POST / HTTP/1.0" 400 -` and on the client side I have `Segmentation fault`. And again, don't understand why because earlier it was returning an url in http and this url wasnt the good one, and not working even renaming in https.
toloveru commented 2020-05-19 20:04:17 +02:00 (Migrated from github.com)

After a ton of screwing around with uWSGI I finally managed to get it running. First off, the uWSGI application in Debian packages apparently does not take the --wsgi-file option. You'd have to install the application with pip. Then use this uwsgi command to launch the application: uwsgi --socket 0.0.0.0:8080 --protocol=http --wsgi-file fhost.py --callable app. I can't believe that this hasn't been documented anywhere yet. Hopefully it saves someone the hours of trouble I had with this.

After a ton of screwing around with uWSGI I finally managed to get it running. First off, the uWSGI application in Debian packages apparently does not take the `--wsgi-file` option. You'd have to install the application with pip. Then use this uwsgi command to launch the application: `uwsgi --socket 0.0.0.0:8080 --protocol=http --wsgi-file fhost.py --callable app`. I can't believe that this hasn't been documented anywhere yet. Hopefully it saves someone the hours of trouble I had with this.
orhun commented 2021-02-13 22:50:47 +01:00 (Migrated from github.com)

In case anyone's still having problems with installing it, I wrote a blog post about it: https://orhun.dev/blog/no-bullshit-file-hosting/

In case anyone's still having problems with installing it, I wrote a blog post about it: https://orhun.dev/blog/no-bullshit-file-hosting/
UmutAlihan commented 2021-02-16 13:20:23 +01:00 (Migrated from github.com)

In case anyone's still having problems with installing it, I wrote a blog post about it: https://orhun.dev/blog/no-bullshit-file-hosting/

I would love to see a Dockerfile wrapping the commands and set up services in your great blog post :)

> In case anyone's still having problems with installing it, I wrote a blog post about it: https://orhun.dev/blog/no-bullshit-file-hosting/ I would love to see a Dockerfile wrapping the commands and set up services in your great blog post :)
TrevCan commented 2021-08-08 00:02:35 +02:00 (Migrated from github.com)

In case anyone's still having problems with installing it, I wrote a blog post about it: https://orhun.dev/blog/no-bullshit-file-hosting/

Hello @orhun, thanks for making the guide.
Just have a few suggestions:

  • Add python-pip to requirements (for the below reason)
  • Add install requirements uwsgi through pip (through the Arch repos I was not able to get the --with-file option).

Edit: Also add

  • create file instance/config.py (with your instructions I tried initializing the database but I got an error FileNotFoundError)
> In case anyone's still having problems with installing it, I wrote a blog post about it: https://orhun.dev/blog/no-bullshit-file-hosting/ Hello @orhun, thanks for making the guide. Just have a few suggestions: - Add `python-pip` to requirements (for the below reason) - Add install requirements `uwsgi` through pip (through the Arch repos I was not able to get the `--with-file` option). Edit: Also add - create file `instance/config.py` (with your instructions I tried initializing the database but I got an error `FileNotFoundError`)
orhun commented 2021-08-11 23:24:11 +02:00 (Migrated from github.com)
  • Add python-pip to requirements (for the below reason)

requirements.txt is installed via pip so it might be unnecessary to mention it separately. But I added it anyways.

  • Add install requirements uwsgi through pip (through the Arch repos I was not able to get the --with-file option).

It's because python plugin is either not installed or loaded. (in Arch: uwsgi-plugin-python)
I updated the blog post to mention this.

  • create file instance/config.py (with your instructions I tried initializing the database but I got an error FileNotFoundError)

Done. I should start watching the repository get notified about these changes.

Thanks for the suggestions! 🐻

> * Add `python-pip` to requirements (for the below reason) `requirements.txt` is installed via `pip` so it might be unnecessary to mention it separately. But I added it anyways. > * Add install requirements `uwsgi` through pip (through the Arch repos I was not able to get the `--with-file` option). It's because python plugin is either not installed or loaded. (in Arch: `uwsgi-plugin-python`) I updated the blog post to mention this. > * create file `instance/config.py` (with your instructions I tried initializing the database but I got an error `FileNotFoundError`) Done. I should start watching the repository get notified about these changes. Thanks for the suggestions! 🐻
dirsigler commented 2021-11-17 11:58:29 +01:00 (Migrated from github.com)

grave-digging here.
My initial request got solved ages ago therefore I close this issue.

Thanks everyone!

grave-digging here. My initial request got solved ages ago therefore I close this issue. Thanks everyone!
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: mia/0x0#8
No description provided.