Hi Jochen,

On Fri, Sep 2, 2016 at 8:32 PM, Jochen Bick <jochen.b...@usys.ethz.ch> wrote:
> yes exactly. So my problem is that I have no idea where to copy those
> settings. I have tutorial how it works on Centos but the file structure is
> different on Ubuntu.

Slightly different, but not too different.  If it's Apache then the
general format of its configuration files is probably the same.  Just
the path and how to restart the web server will differ.

I tried setting it up before but that was a long time ago.  But if not
me, perhaps someone else can help you if you post (a) what you have so
far in the configuration files and (b) what kind of errors you're
getting in your error logs.

> So I have my galaxy instance running on localhost:8080 (can also be moved to
> something else). If I run localhost or my local ip in a browser I see the
> apache also from a different PC in my network. So my idea is to redirect the
> apache or galaxy to my IP so that everyone in the network can see and use it
> (ssl encrypted if possible)

I would ignore SSL for the moment.  You should probably break up your
problem into smaller problems.

Try editing 000-default.conf.  Then throw the RewriteRules in the
aforementioned web page into that.  I think that page is actually
quite self-explanatory.  For example, this rule:

RewriteRule ^(.*) http://localhost:8080$1 [P]

would rewrite the URLs so that anyone accessing your site on port 80
would then get sent to port 8080.  If it's another server, then it
would then be something like this:

RewriteRule ^(.*) http://www.example.com:8080$1 [P]

Of course, you can change that to https, etc. but, again, move step by
step and see if you can get port 80 on localhost redirected to port
8080 on localhost first.

Please keep all replies on the list by using "reply all"
in your mail client.  To manage your subscriptions to this
and other Galaxy lists, please use the interface at:

To search Galaxy mailing lists use the unified search at:

Reply via email to