I have finally gotten an install of Campcaster to run. I was unable to
compile LS version due to limited knowledge of the process. I used
Ubuntu 7.04
"Feisty:". I also had to change an instruction given in the cheatsheet
to Feisty from Dapper to get things to work. All works as intended. I
tried Ubuntu Studio but was less successful, I do not believe it is
exactly the same as the official Ubuntu.
The problem is not with Campcaster, but with my network. Some net
sluething revealed port 80 and port 3344 blocked. I can run the web
interface inside my small LAN, but not from outside. I am thinking of
two solutions: find the block or use different ports. I found two ports
that are not blocked, but changing the ports from the Campcaster studio
interface causes Campcaster to "lose" all three servers Campcaster is
well behaved here and simply asked if I wanted to fix the port setting
to log on, well done..
I note that I can access Station thru LAN even if Studio is not running
and assume a configuration file is somewhere and it could be changed.
Is this true? If so can the ports be changed there?
My interest is somewhat casual as the Cheif engineer for a large non
commercial station and several smaller non commercial stations. These
stations are using very expensive software for automation and the
investment is high in time to use it. Campcaster seems ideal for the
target of unserved audiences, however and it will remain of interest to
me for use at small stations in the future. My interest is in the web
administration of a station running automation and I am using this
fascinating software as a learning environment. My knowledge of Linux,
the web and networks has been increased, thanks.
I would also like to thank the people who are creating this software for
the world, a fine gift indeed for a world in need of truth.
The Campcaster storage server and web interface are web services which
are run by Apache. I think the easiest way to make them accessible
from outside on a different port is not to change anything in
Campcaster, but make Apache listen on a second port as well (say
10080), and redirect all requests to port 10080 to the same document
root as the default.
Caveat: nobody has tried this yet, so it may not work. Please tell us
if it did. Thanks,
Ferenc
On 10/1/07, Scott Henning wrote:
> Hello,
>
> I have finally gotten an install of Campcaster to run. I was unable to
> compile LS version due to limited knowledge of the process. I used
> Ubuntu 7.04
> "Feisty:". I also had to change an instruction given in the cheatsheet
> to Feisty from Dapper to get things to work. All works as intended. I
> tried Ubuntu Studio but was less successful, I do not believe it is
> exactly the same as the official Ubuntu.
>
> The problem is not with Campcaster, but with my network. Some net
> sluething revealed port 80 and port 3344 blocked. I can run the web
> interface inside my small LAN, but not from outside. I am thinking of
> two solutions: find the block or use different ports. I found two ports
> that are not blocked, but changing the ports from the Campcaster studio
> interface causes Campcaster to "lose" all three servers Campcaster is
> well behaved here and simply asked if I wanted to fix the port setting
> to log on, well done..
>
> I note that I can access Station thru LAN even if Studio is not running
> and assume a configuration file is somewhere and it could be changed.
> Is this true? If so can the ports be changed there?
>
> My interest is somewhat casual as the Cheif engineer for a large non
> commercial station and several smaller non commercial stations. These
> stations are using very expensive software for automation and the
> investment is high in time to use it. Campcaster seems ideal for the
> target of unserved audiences, however and it will remain of interest to
> me for use at small stations in the future. My interest is in the web
> administration of a station running automation and I am using this
> fascinating software as a learning environment. My knowledge of Linux,
> the web and networks has been increased, thanks.
>
> I would also like to thank the people who are creating this software for
> the world, a fine gift indeed for a world in need of truth.
>
> Scott Henning
>