[Support] cmer - Seafile


cmer

Recommended Posts

Hi,

tested this docker now and I love it! Thanks cmer!!

 

I only had to add FILE_SERVER_ROOT to my server address so it works with down- and uploads.

 

So now Im running local http: and wants to go safe outside my LAN  -  Need some kind of guide here? O.o

Settin up Nginx, SSL etc, not obvius from this thread to a noob.

 

Another question is, how do I know what version Im running, I remember it was in the footer when I run Seafile standalone earlier?

 

BR,

/tompa

 

Link to comment
On 5/25/2017 at 11:07 PM, airbillion said:

That would be great!

 

Thanks for the container...it has been working really well for me!

 

I have updated the container. It should show up in a few minutes. Just update and you should be good to go!

Link to comment
On 2017-05-29 at 7:13 PM, tompa said:

Hi,

tested this docker now and I love it! Thanks cmer!!

 

I only had to add FILE_SERVER_ROOT to my server address so it works with down- and uploads.

 

So now Im running local http: and wants to go safe outside my LAN  -  Need some kind of guide here? O.o

Settin up Nginx, SSL etc, not obvius from this thread to a noob.

 

Another question is, how do I know what version Im running, I remember it was in the footer when I run Seafile standalone earlier?

 

BR,

/tompa

 

 

Answering my self here :)

I found this tutorial very helpful - https://cyanlabs.net/tutorials/the-complete-unraid-reverse-proxy-duck-dns-dynamic-dns-and-letsencrypt-guide/

Everything seems to be working perfect so far!

 

Still cant find version info though...

/tompa

 

edit: found version from bottom left "About"  -> running 6.1.0 now

 

Edited by tompa
Link to comment
  • 3 weeks later...
  • 3 weeks later...

Hello - 

 

I'm not sure if I'm nuts here, but it sure seems like I've done something wrong with the setup. Everyone else seems to be successful - so it must be me! 

 

Installing via CA, the setup appears to work fine. I browse to the instance and get the standard login page. Username & password specified at login do not work. I attempted to reset the password via reset-admin.sh but the script fails to execute (syntax error on line 9). Since the script only finds python and executes manage.py, I attempted to do that as well -- but it fails as well (no module named django.core.management). 

 

At this point, I'm stumped about how to log in. All logs (unRAID or application) appear clean or empty. 

 

My install process:

Running the current version of unRAID + CA. Added the docker, used the following settings (left default unless otherwise noted):

 

Instance URL: http://192.168.X.X (valid local IP of the server)

Email: [email protected]

Password: test (to verify no typos)

Web Interface Port: 8500 (8000 currently taken)

 

A user share called "seafile" exists.

 

Thanks for any assistance! 

Link to comment
  • 3 weeks later...
2 hours ago, ice pube said:

Stupid question probably but how do I add my /media share in the Seafile admin page? In my docker setup I have /media mapped to /mnt/user/media

 

You can't unless you also install the client on Unraid, which would definitely be an unconventional way of doing it. If you want to share /media, try using SMB.

Link to comment
  • 2 weeks later...

Awesome job with this dcoker!

 

Quick question though...is there anythign special that neeeds to be done to get the Pro version working?

 

I have tried with botha mysql docker and without...

 

I have the free version working perfectly...I set up a 2nd docker to test the Pro version and always have this error:

 


Installing Professional Edition...
Downloading & Extracting https://download.seafile.com/d/6e5297246c/files/?p=/pro/seafile-pro-server_6.1.4_x86-64.tar.gz&dl=1...
Using Professional Edition...
Installation path: /opt/haiwen/seafile-pro-server-6.1.4

Seahub is not running
Done.

Using Professional Edition...
Installation path: /opt/haiwen/seafile-pro-server-6.1.4

Seahub is not running
Done.


seafile server not running yet
Done.
Traceback (most recent call last):
File "/opt/haiwen/seafile-pro-server-6.1.4/pro/pro.py", line 837, in <module>
main()
File "/opt/haiwen/seafile-pro-server-6.1.4/pro/pro.py", line 834, in main
args.func(args)
File "/opt/haiwen/seafile-pro-server-6.1.4/pro/pro.py", line 705, in do_setup
env_mgr.read_seafile_conf_dir()
File "/opt/haiwen/seafile-pro-server-6.1.4/pro/pro.py", line 341, in read_seafile_conf_dir
with open(seafile_ini, 'r') as fp:
IOError: [Errno 2] No such file or directory: '/opt/haiwen/ccnet/seafile.ini'

 

Seafile Pro is free for up to 3 users so I don't think I would need a license file....

 

Any ideas?

 

Thanks!

Edited by airbillion
Link to comment

Hi Cmer,

 

Still no luck with getting the Pro version running...

 

According to the Seafile website no license file is needed for 3 or less users:

 

"You can get pro edition free for 3 users by register an account in our customer center. Note, you don't need a license file to run the pro edition for 3 users."

 

So I think that there may be a different issue that I am running into...

 

Re-pulled the docker again and still received this error:

 

Installing Professional Edition...
Downloading & Extracting https://download.seafile.com/d/6e5297246c/files/?p=/pro/seafile-pro-server_6.1.4_x86-64.tar.gz&dl=1...
Using Professional Edition...
Installation path: /opt/haiwen/seafile-pro-server-6.1.4

Seahub is not running
Done.


seafile server not running yet
Done.

seafile server not running yet
Done.
Traceback (most recent call last):
File "/opt/haiwen/seafile-pro-server-6.1.4/pro/pro.py", line 837, in <module>
main()
File "/opt/haiwen/seafile-pro-server-6.1.4/pro/pro.py", line 834, in main
args.func(args)
File "/opt/haiwen/seafile-pro-server-6.1.4/pro/pro.py", line 705, in do_setup
env_mgr.read_seafile_conf_dir()
File "/opt/haiwen/seafile-pro-server-6.1.4/pro/pro.py", line 341, in read_seafile_conf_dir
with open(seafile_ini, 'r') as fp:
IOError: [Errno 2] No such file or directory: '/opt/haiwen/ccnet/seafile.ini'

 

Any other ideas about what I should try to resolve this?

 

Thank you for your help!

 

 

Link to comment
1 hour ago, cmer said:

Try going "pro" with the non-pro docker. I think you need to initialize the database with the community edition (non-pro) and then upgrade, but I might be wrong. Regardless, you can go back to non-pro without an issue after.

Thanks!  That worked...pulled regular version...got it running...then pulled pro version and it upgraded and started up perfectly!

 

Thanks again!!

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.