| | 56 | |
|---|
| | 57 | <dt>I'm trying to access cherokee-admin from a remote machine but it doesn't seem to work. Is it broken?</dt> |
|---|
| | 58 | <dd>No it is not. cherokee-admin binds only to local loopback by default. There are some workarounds: |
|---|
| | 59 | <ul> |
|---|
| | 60 | <li>Create an SSH tunnel. This is the recommended way. In order to do so you must issue the following command: |
|---|
| | 61 | <blockquote><pre class="shell">ssh -L 9090:localhost:9090 remote_IP</pre></blockquote> |
|---|
| | 62 | After that you can access the remote interface through http://localhost:9090 and every request will be forwarded to the remote IP running cherokee-admin. |
|---|
| | 63 | </li> |
|---|
| | 64 | <li>Launch cherokee-admin with the -a parameter in order to force it to listen to all the network interfaces.</li> |
|---|
| | 65 | <li>Finally you could always install cherokee on your local host, configure it there and then copy the generated cherokee.conf file to the device running the cherokee instance you wanted to set up.</li> |
|---|
| | 66 | </ul> |
|---|
| | 67 | </dd> |
|---|
| | 68 | |
|---|
| | 69 | <dt>I'm old-style and don't want to use your gorgeous configuration UI. Is there a way to replicate cherokee-admin's work by hand?</dt> |
|---|
| | 70 | <dd> |
|---|
| | 71 | Yes there is. The configuration file is a plain text file and its syntax is well documented. Check the documentation of your package, or its <a href="http://www.cherokee-project.com/doc/internal_configuration.html">online version</a>.<br/> |
|---|
| | 72 | Notice that it is not the recommended method, but the format will always be kept updated to facilitate scripting tasks, working with embedded devices and other similar situations. |
|---|
| | 73 | </dd> |
|---|
| | 74 | |
|---|