old.kete.net.nz :Documentation

Can you please give me some more detailed instructions on how to run this after installation

hello ,

i do not use the port 80 in apache to run kete

i use the port 85  like ( http://kware:85)

and kete run successfully , but when i add an item , the item link do not open , because the link appears with out the port

like ( http://kware/site/topics/show/20-test-2  ) without port

how i can fix this

thank you

Tags: apache2 conf, another port

Have you tried changing the "Site Name" system setting via Administrator's Toolbox > reconfigure site > Advanced Options > Server?

Try adding the host name + colon + port and see if that works for you, i.e. kware:85 in your case.

Let me know how that goes.

yes i tried this ,

i set the site name  with the port and the site url also

but the problem is still, not solved

Hi,

Yes, it was a bit of an experiment and would only work in in theory with the latest Kete (i.e. from master about a week ago). I guess my work was incomplete though.

I must admit I have a bias against using ports this way (because there are better alternatives in my opinion) and the Kete codebase reflects this. To work around this, I suggest use use Apache vhosts all on port 80 and then use either /etc/hosts or the "ghost" ruby gem.

Here's an example of what I mean from how I develop:

<VirtualHost *:80>
  ServerName kete
  ...
</VirtualHost>

<VirtualHost *:80>
  ServerName kete_review
  ...
</VirtualHost>

Note that I have "kete" and "kete_review" as vhosts. Not hugely different from normal configuration of vhosts that we recommend. The difference is that these are domains that aren't in any DNS, so I add them locally to my machine so that it knows to request localhost like so:

$ sudo gem install ghost
...
$ ghost add kete
...
$ ghost add kete_review

After that I can simply request http://kete/ and http://kete_review/ from my local machine and it will hit the right vhosts.

This, of course, is limited only being browsable from my local machine. When we want to show our work to others on our team, etc. we use a similar technique, but with a wildcard DNS record that points at the machines IP address (this is within the context of katipo.co.nz domain)

*.a_machine               IN      A       1.2.3.4 # ip address for my machine

Then we add apache vhosts with ServerName directives that point at "kete.a_machine.katipo.co.nz" and "kete_review.a_machine.katipo.co.nz", etc.

I personally hate having to remember to specify ports and prefer this "shortcuts" approach when doing development.  That's why we have never gotten around to making Kete's records properly handle ports. We would be happy to accept a code contribution to set it right though.

One last thing before we declare the experiment a failure...

Did you do a site and backgroundrb restart and a Administrator's Toolbox > Rebuild search databases? If not, please do those and see if that does the trick.

thanks ,

but , i want more details

i cant understand this process

and i cant apply it

Hi,

From the command line, in your app directory:

$ touch tmp/restart # restarts web server
$ script/console backgroundrb stop # restarting backgroundrb which we needs to have its environment reloaded to take advantage of Site Name
...
$ script/console backgroundrb start

Now, click the Administrator's Toolbox "Rebuild search databases" and use the default options and click "Rebuild Search Databases".

After the search records have been rebuilt, click "Browse search records" and see if the links from results now work.

Isn't this last command missing a #?

rake kete:tools:tiny_mce:configure_imageselector the RAILS_ENV part if necessary, this is needed by new imageselector functionality

> Isn't this last command missing a #?

Yep, good catch. Edited to have the #. Thanks.