<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
It might be premature as well as half baked - I am just testing out the
thought, however here is my thinking...<br>
<br>
There is a folder called extensions in the dialplan folder. The nice
thing about this folder is that it is read in by a simple xml
preprocessing command that says go get *.xml<br>
<br>
Currently, it is being called from the Default dialplan.<br>
<br>
Borrowing from the Apache HTTPD style configuration, everything to
customize the install is done with additional files as opposed to
editing anything that ships with the software. So This works, however,
we should be able to specify the name of a root configuration folder -
this way all config can sit way outside of the app tree - for example,
to place the FS app in one folder and have all external config in a
different folder not under the same path - thereby ensuring upgrade
safety.<br>
<br>
My patch is only going to work with dialplans, but I propose making it
a pattern to follow.<br>
<br>
In the dialplan, I am making a folder for each context that will be
loaded externally and postfixing a ".d" on the end, so for example
default.d and public.d<br>
<br>
Make sense?<br>
<br>
Michael Jerris wrote:
<blockquote cite="mid:5BD402E7-D487-42C7-9289-9928D5E37FF2@jerris.com"
type="cite">
<pre wrap="">I don't understand the proposal. Could you explain a bit more please.
Mike
On Sep 20, 2008, at 6:39 PM, Christian Jensen
<a class="moz-txt-link-rfc2396E" href="mailto:christian@jensenbox.com"><christian@jensenbox.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">I am working on a patch that would externalize the install configs,
much the same way as the extensions folder (which i propose to be
called "default")
The new folders will be the same name as the context they are called
from, for example the one i am most interested in is "public.d"
Any objections?
-----Original Message-----
From: Michael Jerris <a class="moz-txt-link-rfc2396E" href="mailto:mike@jerris.com"><mike@jerris.com></a>
Sent: September 20, 2008 3:24 PM
To: <a class="moz-txt-link-abbreviated" href="mailto:freeswitch-users@lists.freeswitch.org">freeswitch-users@lists.freeswitch.org</a> <<a class="moz-txt-link-abbreviated" href="mailto:freeswitch-users@lists.freeswitch.org">freeswitch-users@lists.freeswitch.org</a>
</pre>
<pre wrap="">Cc: <a class="moz-txt-link-abbreviated" href="mailto:freeswitch-users@lists.freeswitch.org">freeswitch-users@lists.freeswitch.org</a> <<a class="moz-txt-link-abbreviated" href="mailto:freeswitch-users@lists.freeswitch.org">freeswitch-users@lists.freeswitch.org</a>
</pre>
<pre wrap="">Subject: Re: [Freeswitch-users] How to upgrade ?
Make current will not work from release tarballs but if you grab the
new version it should install without wiping out your config.
Mike
On Sep 20, 2008, at 6:10 PM, Michael S Collins <a class="moz-txt-link-rfc2396E" href="mailto:msc@freeswitch.org"><msc@freeswitch.org></a>
wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Yes "make current" will update you without breaking your existing
configs. Even if you do "make samples" it won't overwrite your
configs bit it will replace any missing conf files with default ones.
-MC
Sent from my iPhone
On Sep 20, 2008, at 2:46 PM, henkoegema <a class="moz-txt-link-rfc2396E" href="mailto:pabx_freeswitch@telenet.be"><pabx_freeswitch@telenet.be></a>
wrote:
</pre>
<blockquote type="cite">
<pre wrap="">At the moment I'm using FS version 1.0.0.
I want to upgrade to the latest version.
Can I just type
#make current (?) :working:
without loosing my own (or edited standard) conf files ?
--
View this message in context: <a class="moz-txt-link-freetext" href="http://www.nabble.com/How-to-upgrade---tp19589317p19589317.html">http://www.nabble.com/How-to-upgrade---tp19589317p19589317.html</a>
Sent from the Freeswitch-users mailing list archive at Nabble.com.
_______________________________________________
Freeswitch-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Freeswitch-users@lists.freeswitch.org">Freeswitch-users@lists.freeswitch.org</a>
<a class="moz-txt-link-freetext" href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a>
UNSUBSCRIBE:<a class="moz-txt-link-freetext" href="http://lists.freeswitch.org/mailman/options/freeswitch-users">http://lists.freeswitch.org/mailman/options/freeswitch-users</a>
<a class="moz-txt-link-freetext" href="http://www.freeswitch.org">http://www.freeswitch.org</a>
</pre>
</blockquote>
<pre wrap="">_______________________________________________
Freeswitch-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Freeswitch-users@lists.freeswitch.org">Freeswitch-users@lists.freeswitch.org</a>
<a class="moz-txt-link-freetext" href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a>
UNSUBSCRIBE:<a class="moz-txt-link-freetext" href="http://lists.freeswitch.org/mailman/options/freeswitch-users">http://lists.freeswitch.org/mailman/options/freeswitch-users</a>
<a class="moz-txt-link-freetext" href="http://www.freeswitch.org">http://www.freeswitch.org</a>
</pre>
</blockquote>
<pre wrap="">_______________________________________________
Freeswitch-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Freeswitch-users@lists.freeswitch.org">Freeswitch-users@lists.freeswitch.org</a>
<a class="moz-txt-link-freetext" href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a>
UNSUBSCRIBE:<a class="moz-txt-link-freetext" href="http://lists.freeswitch.org/mailman/options/freeswitch-users">http://lists.freeswitch.org/mailman/options/freeswitch-users</a>
<a class="moz-txt-link-freetext" href="http://www.freeswitch.org">http://www.freeswitch.org</a>
_______________________________________________
Freeswitch-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Freeswitch-users@lists.freeswitch.org">Freeswitch-users@lists.freeswitch.org</a>
<a class="moz-txt-link-freetext" href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a>
UNSUBSCRIBE:<a class="moz-txt-link-freetext" href="http://lists.freeswitch.org/mailman/options/freeswitch-users">http://lists.freeswitch.org/mailman/options/freeswitch-users</a>
<a class="moz-txt-link-freetext" href="http://www.freeswitch.org">http://www.freeswitch.org</a>
</pre>
</blockquote>
<pre wrap=""><!---->
_______________________________________________
Freeswitch-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Freeswitch-users@lists.freeswitch.org">Freeswitch-users@lists.freeswitch.org</a>
<a class="moz-txt-link-freetext" href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a>
UNSUBSCRIBE:<a class="moz-txt-link-freetext" href="http://lists.freeswitch.org/mailman/options/freeswitch-users">http://lists.freeswitch.org/mailman/options/freeswitch-users</a>
<a class="moz-txt-link-freetext" href="http://www.freeswitch.org">http://www.freeswitch.org</a>
</pre>
</blockquote>
<br>
</body>
</html>