Does anyone really see the need for Mystic to allow all of the paths to
be configured upon initial installation? I was thinking of simplifying
it so that the installation only asks for the root Mystic directory.
As I continue to build on Mystic more and more paths will be
configurable, so its going to become overwhelming if I keep adding paths to the installation utility.
I am doing a small update to the installation, nothing special of note really >but I have a question:
Does anyone really see the need for Mystic to allow all of the paths to be >configured upon initial installation? I was thinking of simplifying it so that
the installation only asks for the root Mystic directory.
As I continue to build on Mystic more and more paths will be configurable, so >its going to become overwhelming if I keep adding paths to the installation >utility.
--- Mystic BBS v1.12 A38 2018/01/01 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)
On 01/04/18, g00r00 pondered and said...
Does anyone really see the need for Mystic to allow all of the paths to be configured upon initial installation? I was thinking of simplifying it so that the installation only asks for the root Mystic directory.
As I continue to build on Mystic more and more paths will be configurable, so its going to become overwhelming if I keep adding paths to the installation utility.
I think on first thought it seems fine to do as you suggest. Another idea is >that you might want to offer a separate menu option on the initial installer >page that users could access to change any default paths so it separates >things out a bit... and make the 'Install Mystic BBS' more as you say, the >user can just set the root Mystic directory from that screen then press F2 to >install.
I also suggest you change the default Outbound Echomail path to use %system >path%\echomail\out only and drop \fidonet as this may confuse some if they are >not actually running fidonet from first install.
Best, Paul
`I'm not expendable, I'm not stupid, and I'm not going' - Kerr Avon, Blake's 7
--- Mystic BBS v1.12 A38 2018/01/01 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)
Does anyone really see the need for Mystic to allow all of the paths
to be configured upon initial installation? I was thinking of
simplifying it so that the installation only asks for the root Mystic directory.
Does anyone really see the need for Mystic to allow all of the paths to
be configured upon initial installation? I was thinking of simplifying
it so that the installation only asks for the root Mystic directory.
I am doing a small update to the installation, nothing special of note really but I have a question:
Does anyone really see the need for Mystic to allow all of the paths to
be configured upon initial installation? I was thinking of simplifying
it so that the installation only asks for the root Mystic directory.
As I continue to build on Mystic more and more paths will be
configurable, so its going to become overwhelming if I keep adding paths to the installation utility.
I am doing a small update to the installation, nothing special of note really but I have a question:
Does anyone really see the need for Mystic to allow all of the paths to
be configured upon initial installation? I was thinking of simplifying
it so that the installation only asks for the root Mystic directory.
As I continue to build on Mystic more and more paths will be
configurable, so its going to become overwhelming if I keep adding paths to the installation utility.
Does anyone really see the need for Mystic to allow all of the paths to
be configured upon initial installation? I was thinking of simplifying
it so that the installation only asks for the root Mystic directory.
Does anyone really see the need for Mystic to allow all of the paths to
be configured upon initial installation? I was thinking of simplifying
it so that the installation only asks for the root Mystic directory.
I also suggest you change the default Outbound Echomail path to use %system path%\echomail\out only and drop \fidonet as this may confuse
some if they are not actually running fidonet from first install.
I would like to see a small confirmation appear when changing the main directory (like to \mystic\install\) so I know the inserted data (\install) propagated everywhere else, otherwise no need that I can see. :-)
I am doing a small update to the installation, nothing special of note really but I have a question:
Does anyone really see the need for Mystic to allow all of the paths to
be configured upon initial installation? I was thinking of simplifying
it so that the installation only asks for the root Mystic directory.
As I continue to build on Mystic more and more paths will be
configurable, so its going to become overwhelming if I keep adding paths to the installation utility.
I would like to see a small confirmation appear when changing the
main directory (like to \mystic\install\) so I know the inserted
data (\install) propagated everywhere else, otherwise no need
that I can see.
:-)
I'm sorry, I'm not quite sure I am following you here so instead I'll paint a picture of what I had in mind: The new installation would probably look something like this:
Root Path | c:\mystic\
BBS Name | New Mystic BBS
BBS Location | Somewhere, USA
Sysop Handle | Sysop
Real Name | Sysop
E-mail |
[F2] Begin Installation [ESC] Abort
It would then create your Sysop account as well, and configure the BBS name, location, and Sysop name.
Funny you mention that because I just changed the default last night in A39 to:
\root\echomail\out\primary\
It would then create your Sysop account as well, and configure the BBS name, location, and Sysop name.
Does anyone really see the need for Mystic to allow all of the paths to
be configured upon initial installation? I was thinking of simplifying
it so that the installation only asks for the root Mystic directory.
Does anyone really see the need for Mystic to allow all of the paths to
be configured upon initial installation? I was thinking of simplifying
it so that the installation only asks for the root Mystic directory.
g00r00 wrote to All <=-
I am doing a small update to the installation, nothing special of note really but I have a question:
Does anyone really see the need for Mystic to allow all of the paths to
be configured upon initial installation? I was thinking of simplifying
it so that the installation only asks for the root Mystic directory.
Avon wrote to g00r00 <=-
I also suggest you change the default Outbound Echomail path to use %system path%\echomail\out only and drop \fidonet as this may confuse
some if they are not actually running fidonet from first install.
g00r00 wrote to Avon <=-
I also suggest you change the default Outbound Echomail path to use %system path%\echomail\out only and drop \fidonet as this may confuse
some if they are not actually running fidonet from first install.
Funny you mention that because I just changed the default last night in A39 to:
\root\echomail\out\primary\
g00r00 wrote to Cmech <=-
It would then create your Sysop account as well, and configure the BBS name, location, and Sysop name.
It would then create your Sysop account as well, and configure the BB name, location, and Sysop name.
That will be a pain for those of us upgrading. All I need to specify is the root path. The other information should be separate, since only new sysops need it. Remember that installing a new copy of Mystic is also
the first step to upgrading.
That will be a pain for those of us upgrading. All I need to specify is the root path. The other information should be separate, since only new sysops need it. Remember that installing a new copy of Mystic is also
the first step to upgrading.
Avon wrote to vk3jed <=-
Perhaps there could be some switches added to the installer that allow
you to pass the key fields via command line? That could speed things up
if you're trying to automate a fresh install and copying files across from it. Just a thought?
That will be a pain for those of us upgrading. All I need to specify is the root path.
Funny you mention that because I just changed the default last night in A39 to:
\root\echomail\out\primary\
\root\echomail\outbound (primary)
Then obviously all the other directories would be in ..\echomail as well, rather than another subdirectory. May lead to less confusion. *shrug*
^^ Whats the point of having an OUT directory if the directories used aren't within the out directory! I hate that BSO works that way, and I can't imagine why they did it the way they did.
Anyway having primary isn't the best solution but it keeps it all under the same bucket which I like (and is much better than fidonet lol)
c:\mystic\out\primary
c:\mystic\out\fsxnet.021
c:\mystic\out\agoranet.046
Of course its completely configurable so if someone doesn't like my defaults they can change it. For now I am going to try out primary in
the next alpha as a default.
g00r00 wrote to vk3jed <=-
It will be the identical number of keypresses as it is now, you change
the path and press F2.
Static wrote to vk3jed <=-
On 01/05/18, Tony Langdon said the following...
That will be a pain for those of us upgrading. All I need to specify is the root path.
I'd imagine everything would have defaults and you wouldn't have to
change anything beyond the root path for an upgrade install like you already do.
g00r00 wrote to Accession <=-
\root\echomail\outbound (primary)
Then obviously all the other directories would be in ..\echomail as well, rather than another subdirectory. May lead to less confusion. *shrug*
I don't like that as a default. I tried it in the very beginning but
it leaves us cluttered by the stupid way BSO works:
Anyway having primary isn't the best solution but it keeps it all
under the same bucket which I like (and is much better than fidonet
lol)
c:\mystic\out\primary
c:\mystic\out\fsxnet.021
c:\mystic\out\agoranet.046
So in that case, the default starting directory would be \mystic\echomail\out (is 'out' even needed?) and nothing further until
you setup your primary network. That would not have an extension, and
the rest would.
Unfortunately I don't think I can make that change in Mystic 1 because
it will confuse the shit out of people lol
You haven't "officially" made any changes yet, including the "primary" thing you had discussed the past couple days. ;)
Most people don't understand 5D BSO anyways, since most tossers from yesteryear never supported it.
Yeah I've been sitting on the first A39 pre-alpha for a bit in case I think of some more changes I want to do with the record formats, so no
one has seen it but the default is primary in A39.
I agree. This is part of the reason I want to make a outbound packet viewer so people have a view into what is going on without having to understand that stuff.
I am doing a small update to the installation, nothing special of note really but I have a question:
Does anyone really see the need for Mystic to allow all of the paths to
be configured upon initial installation? I was thinking of simplifying
it so that the installation only asks for the root Mystic directory.
Sysop: | sneaky |
---|---|
Location: | Ashburton,NZ |
Users: | 2 |
Nodes: | 8 (0 / 8) |
Uptime: | 120:19:20 |
Calls: | 2,127 |
Calls today: | 3 |
Files: | 11,149 |
D/L today: |
41 files (21,471K bytes) |
Messages: | 950,890 |