Skip to content

http://host:8000 after seafile-admin start #743

Closed
big-grizzly opened this Issue Jul 22, 2014 · 24 comments

4 participants

@big-grizzly

I am porting the 3.0.4 to FreeBSD 9.2 Release. I understand that you have no support. Although some ports dependencies are not fully written, the build, installation, and init runs for major components seem fine. I have a question, without setting apache or Ngix, what I should expect to http://host:8000 just after

seafile-admin start

I hit 500 Internal Server Error, does it mean httpserver has problem? Which log file I can triage what happens.

Thank you.

@Chilledheart

Hi freebsd guy,

It is quite interesting for me to find out that someone installed seafile sucessfully under freebsd.
I believe you forgot execute ./manage.py syncdb in seahub directory before you start seafile. Or you can reference our manual

@Chilledheart

Hi @big-grizzly ,

You might want to turn on django's debug mode to get more information by adding a line to seahub_setting.py :

DEBUG=True

PS: I spent some hours compiling seafile under FreeBSD, and only found out I got stuck with libevent2. I referenced some old issues with BSDs support (e.g. haiwen/ccnet#4 ) . I thought it is non-trivial work and I will look into the BSDs support of seafile once I get some free time. And it would be very awesome if you can contribute back to seafile.

Cheers,
Chilledheart

@stephenhoos

I would contribute to a bounty on this... big-grizzly will your work help us get the server running on FreeNAS?

@big-grizzly

Somehow the above issue is resolved because I know there is something missing for FreeBSD code. Now the important problem in front of me is all the servers are running. But the downloading file size is always 0 byte, although the file size show in main web interface is 200+K bytes. When uploading, connection is always failed.

Yes, if possible, I would like to help FreeBSD, and FreeNAS community to port this project.

@stephenhoos

big-grizzly, you might want to comment here --> http://forums.pcbsd.org/showthread.php?t=22607

you might get some support, if others know you are working on the project already. I put in a ticket with ixsystems asking them what it would take to get this into FreeNAS.

@Chilledheart

Hi @big-grizzly @stephenhoos
It sounds coooooooool to get seafile into FreeNAS.
If there is anything I can help with, please don't hesitate to cc me, or email me rwindz0 AT gmail DOT c0m.

Thanks!

@stephenhoos

I am not a programmer just a sysadmin, so I can help with testing, but not programming. I run a few FreeNAS boxes, and I can spin up VMs too, so let me know if you need help with testing or anything like that.

@big-grizzly
@stephenhoos
@Chilledheart

some patches for FreeBSD(or FreeNAS, untested though)

sadly, seafile (seaf-daemon) requires additional support for fs change watch via kqueue, so building seafile-client (gui) would be quite tough.

@big-grizzly
@big-grizzly
@big-grizzly
@Chilledheart

@big-grizzly I am not sure, but you might want to reference the python's requirements.txt for thirdpart stuff, notably django
and djblets. Perhaps port www/py-django15 and www/py-djblets would fit this gap.

Thanks!

@big-grizzly
@big-grizzly
@Chilledheart

Hi @big-grizzly

Thanks for your work of bringing seafile to freebsd ports.

Here are some suggestions:

  • py-selenium and unittest are required only for tests, and remain part of optional dependencies for seahub. Ignore them please, if you want.
  • The python djblets problem. Sorry, but I don't have a better solution currently.
  • I have installed freebsd 9.3-rel vm box in my pc, and if possible, I can volunteer to test these ports.

Cheers,
Chilledheart

@big-grizzly
@Chilledheart

Hi @big-grizzly

It is grad to see website part works without problems.
And you are using seafile client from FreeBSD, aren't you? Try a different platform that seafile officially supports, and run client on it to see whether server part on FreeBSD is okay or not. I must tell that client part for FreeBSD is left incomplete (notably wt-monitor part, 200 loc or so left).

Cheers,
Chilledheart

@big-grizzly
@Chilledheart

Hi @big-grizzly
I meant there is a 200 lines of code (or so-called loc) of wt-monitor part to fill the gap from linux to FreeBSD.
And I will check that issue(ccnet clide-side connection) later.

Cheers,
Chilledheart

@big-grizzly
@big-grizzly
@shoeper shoeper closed this Feb 9, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.