The story of system.startup.startupScript
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Active
- Domain
- documentation
Research direction
Start with the system.startup.startupScript entry point and compare its source with the twelve startup stages listed in the issue. The issue names no target documentation file, test, or required output, so clarify where the explanation should live and what format marks the work as complete.
Written by the indexing model from the issue text.
Description
I asked Claude to summarize what system.startup.startupScript does. It's very good at understanding the whole of what a 309-line script written over many years by many people, does.
-
Bails if it already ran.
system.temp.Frontierexisting is the "already started" flag; otherwise it creates that table, stamps the startup time, and setsstartingUp = true. -
Records where the root file is --
Frontier.pathToRootandFrontier.pathstring. -
Starts the scheduler and fixes the clock --
scheduler.init,scheduler2.init, then makes sure the everyMinute, hourly, and overnight tasks are set in the future (overnight keeps its hour, e.g. 3AM). -
Opens the About window (if
user.prefs.openAboutWindowsays so) and starts the log (log.startup). -
Runs the external startup commands file --
opmlStartupCommands.txtnext to the app, if present -- then callsFrontier.enableAgents. -
Opens guest databases -- everything in
user.databaseswithopenOnStartuptrue, running each one's#startupscript if itsrunStartupScriptis true. -
The init parade --
html.init,webserver.init,betty.init,people.init,custody.init,soap.init,export.init, andmainResponder.startupon the OPML Editor. -
First-run business -- on
user.prefs.firstRootRun: license agreement, the user-info dialog, root updates. -
Builds the menubar, initializes proxy prefs, installs Tools (in a try, so a Tools failure can't kill the startup), and finds the default browser on Windows.
-
Calls
system.callbacks.startup-- the user's own startup scripts. -
Starts the daemons --
inetd.start, last on purpose so servers come up after everything else is ready. -
Clears
startingUp-- the script's own comment: "signal to all who care, let the hits begin!"
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from scripting/helloFrontier
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
scripting/helloFrontier#13 · 2 comments · 1 reaction ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
scripting/helloFrontier#12 ·
-
Difficulty 5/5 Over a week Newbie friendliness 10/100
scripting/helloFrontier#11 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
scripting/helloFrontier#10 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
scripting/helloFrontier#9 · 4 comments · 1 reaction ·
All issues in scripting/helloFrontier
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
bancolombia/sentinel#22 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 94/100
objectionary/hone-maven-plugin#1061 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
redhat-developer/rhdh-plugins#4887 · 2 comments ·