Forum OpenACS Q&A: where can i change the default url for oacs-9.5?

during the configuration i type in a domain that did not work. i should have left it to the default, localhost:8000. i used the ip address fine until i installed the dotlrn and then the non resolving domain came into play.

i have gone through the administration and expected to find something in the parameter settings but didn't. Hopefully, there's a file I can edit.

thanks.

psql to the db. Something like:

su - postgres
psql oacs-5-9

Then you can get the parameter_id:

oacs-5-9=# select * from apm_parameter_values where parameter_id in (select parameter_id from apm_parameters where parameter_name = 'SystemURL');

 value_id | package_id | parameter_id |             attr_value             
----------+------------+--------------+------------------------------------
       74 |         69 |           64 | http://localhost:8000
(1 row)

You are referring to the kernel parameter "SystemURL". It can be altered via the Web interface via /acs-admin/ . On this page see the link "Parameters" in the line "ACS Kernel". When you click this "Parameters" link, you find the "SystemUR" as last entry on the resulting page.

Having problems with the links still pointing to localhost:8000 after making sure it has the domain name in the default url. I have rebooted the computer, restarted postgresql several times. is there a cache or another location where the localhost needs to be changed?

the SystemURL is used sometimes on internal redirects, it is setup on the initial install via install-ns, which also writes the default config file. When you change the host configuration (using different ip-address etc.) you have typically to change both, the config file and the SystemURL, and as well the "service" file. In general, the NaviServer config file allows to configure the listen on e.g. all IP addresses of your machine (see the first section of the naviserver config file).

Concerning running as a service: Depending on the version of linux, install-ns creates either a UpStart file (usage: status|start|stop oacs-5.9) and/or a systemd file (usage: systemctl status|start|stop oacs-5.9). running on older Ubuntus, you get upstart, some ubuntu versions support upstart and systemd (where the script generates both), redhat/fedora/centus use sytemd. When you change e.g. IP-addresses and/or ports, you have to update the service files in use as well (see the comments in the service files).

as it turns out the systemctl does not recognize the oacs-9-5 as a service.
I ran the StartUp command, and it was not there when i went to install it. what should i do.

On Debian I had to tweak a little install-oacs.sh so it created systemd script. I did that by setting brutally the systemd flag toward the end of the script.

Reason why it was not working is that probably Debian is a special case with respect to Ubuntu, as it doesn't ship upstart out of the box. Dind't take time to think about a proper fix, but it should just be some "if" revision.

Anyway, for what concerns Kenneth, give a look toward the end of the script and you'll see that systemd service creation is decided upon the value of a couple of flags. Check if your installation passes through the service creation part and if doesn't you can try hardcoding the flags.

on ubuntu 16.04.4 server and downloaded the latest install-ns.sh and install-oacs.sh files.
your instructions were exactly what I needed.

kmw@fremont:/lib/systemd/system$ sudo nano oacs-5-9.service
kmw@fremont:/lib/systemd/system$ sudo systemctl daemon-reload
kmw@fremont:/lib/systemd/system$ sudo systemctl enable oacs-5-9.service
kmw@fremont:/lib/systemd/system$ sudo systemctl is-enable oacs-5-9.service
Unknown operation is-enable.
kmw@fremont:/lib/systemd/system$ sudo systemctl is-enabled oacs-5-9.service
static
kmw@fremont:/lib/systemd/system$

thank you very very much.