Editing Config Files: Difference between revisions
Jump to navigation
Jump to search
imported>Wd6awp No edit summary |
imported>Wd6awp No edit summary |
||
Line 12: | Line 12: | ||
For Windows: | For Windows: | ||
* [https://winscp.net/ Winscp] is a popular file transfer and editor client. | * [https://winscp.net/ Winscp] is a popular file transfer and editor client. | ||
* [http://www.putty.org Putty] is '''the''' SSH and Telnet client. | * [http://www.putty.org Putty] is not an editor but you'll need it. It is '''the''' SSH and Telnet client. | ||
For Mac: | For Mac: |
Revision as of 17:43, 15 October 2017
To modify your node beyond the basic settings of what nodesetup.sh can do, you'll need to manually edit the config files. Of course, you'll need to know the user ID and password of your AllStarLink server. You also want to understand the Structure of Config Files before you start.
Linux CLI Editors
For quick and simple changes the built-in Linux editors are the way to go.
- vi is pretty much the default editor on most linux distros. Learn it, love it.
- Update vi to fix cursor movement (apt-get install vim).
- nano is easier to learn and preferred by many.
GUI Editors
Many folks prefer a GUI editor and file transfer client over the Linux vi and nano editors. If you need to do a lot of copy and paste these are much easier. Here are some of the many clients out there.
For Windows:
- Winscp is a popular file transfer and editor client.
- Putty is not an editor but you'll need it. It is the SSH and Telnet client.
For Mac:
Location of Config Files
Nearly all of the files you'll need to edit are in /etc/asterisk