Re: [Freeswitch-users] How to upgrade ?
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 <mike@jerris.com> Sent: September 20, 2008 3:24 PM To: freeswitch-users@lists.freeswitch.org <freeswitch-users@lists.freeswitch.org> Cc: freeswitch-users@lists.freeswitch.org <freeswitch-users@lists.freeswitch.org> 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 <msc@freeswitch.org> wrote:
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 <pabx_freeswitch@telenet.be> wrote:
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: http://www.nabble.com/How-to-upgrade---tp19589317p19589317.html Sent from the Freeswitch-users mailing list archive at Nabble.com.
_______________________________________________ Freeswitch-users mailing list Freeswitch-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_______________________________________________ Freeswitch-users mailing list Freeswitch-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_______________________________________________ Freeswitch-users mailing list Freeswitch-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
I don't understand the proposal. Could you explain a bit more please. Mike On Sep 20, 2008, at 6:39 PM, Christian Jensen <christian@jensenbox.com> wrote:
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 <mike@jerris.com> Sent: September 20, 2008 3:24 PM To: freeswitch-users@lists.freeswitch.org <freeswitch-users@lists.freeswitch.org
Cc: freeswitch-users@lists.freeswitch.org <freeswitch-users@lists.freeswitch.org
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 <msc@freeswitch.org> wrote:
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 <pabx_freeswitch@telenet.be> wrote:
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: http://www.nabble.com/How-to-upgrade---tp19589317p19589317.html Sent from the Freeswitch-users mailing list archive at Nabble.com.
_______________________________________________ Freeswitch-users mailing list Freeswitch-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_______________________________________________ Freeswitch-users mailing list Freeswitch-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_______________________________________________ Freeswitch-users mailing list Freeswitch-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_______________________________________________ Freeswitch-users mailing list Freeswitch-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
It might be premature as well as half baked - I am just testing out the thought, however here is my thinking... 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 Currently, it is being called from the Default dialplan. 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. My patch is only going to work with dialplans, but I propose making it a pattern to follow. 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 Make sense? Michael Jerris wrote:
I don't understand the proposal. Could you explain a bit more please.
Mike
On Sep 20, 2008, at 6:39 PM, Christian Jensen <christian@jensenbox.com> wrote:
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 <mike@jerris.com> Sent: September 20, 2008 3:24 PM To: freeswitch-users@lists.freeswitch.org <freeswitch-users@lists.freeswitch.org
Cc: freeswitch-users@lists.freeswitch.org <freeswitch-users@lists.freeswitch.org
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 <msc@freeswitch.org> wrote:
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 <pabx_freeswitch@telenet.be> wrote:
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: http://www.nabble.com/How-to-upgrade---tp19589317p19589317.html Sent from the Freeswitch-users mailing list archive at Nabble.com.
_______________________________________________ Freeswitch-users mailing list Freeswitch-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_______________________________________________ Freeswitch-users mailing list Freeswitch-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_______________________________________________ Freeswitch-users mailing list Freeswitch-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_______________________________________________ Freeswitch-users mailing list Freeswitch-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_______________________________________________ Freeswitch-users mailing list Freeswitch-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
This was what we talked about on IRC a few days ago right? /b On Sep 21, 2008, at 2:45 AM, Christian Jensen wrote:
It might be premature as well as half baked - I am just testing out the thought, however here is my thinking...
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
Currently, it is being called from the Default dialplan.
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.
My patch is only going to work with dialplans, but I propose making it a pattern to follow.
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
Make sense?
Yeppers. On Sep 21, 2008, at 12:52 AM, Brian West <brian@freeswitch.org> wrote:
This was what we talked about on IRC a few days ago right?
/b
On Sep 21, 2008, at 2:45 AM, Christian Jensen wrote:
It might be premature as well as half baked - I am just testing out the thought, however here is my thinking...
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
Currently, it is being called from the Default dialplan.
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.
My patch is only going to work with dialplans, but I propose making it a pattern to follow.
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
Make sense?
_______________________________________________ Freeswitch-users mailing list Freeswitch-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
participants (3)
-
Brian West
-
Christian Jensen
-
Michael Jerris