The story of system.startup.startupScript

Abierto
#5 1 comentario 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
45/100
Tipo de issue
Documentación
Claridad
Necesita aclaración
Estado de actividad
Activo
Área
documentation

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

  1. Bails if it already ran. system.temp.Frontier existing is the "already started" flag; otherwise it creates that table, stamps the startup time, and sets startingUp = true.

  2. Records where the root file is -- Frontier.pathToRoot and Frontier.pathstring.

  3. 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).

  4. Opens the About window (if user.prefs.openAboutWindow says so) and starts the log (log.startup).

  5. Runs the external startup commands file -- opmlStartupCommands.txt next to the app, if present -- then calls Frontier.enableAgents.

  6. Opens guest databases -- everything in user.databases with openOnStartup true, running each one's #startup script if its runStartupScript is true.

  7. The init parade -- html.init, webserver.init, betty.init, people.init, custody.init, soap.init, export.init, and mainResponder.startup on the OPML Editor.

  8. First-run business -- on user.prefs.firstRootRun: license agreement, the user-info dialog, root updates.

  9. 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.

  10. Calls system.callbacks.startup -- the user's own startup scripts.

  11. Starts the daemons -- inetd.start, last on purpose so servers come up after everything else is ready.

  12. Clears startingUp -- the script's own comment: "signal to all who care, let the hits begin!"

Lenguaje dominante
Sin datos de lenguaje
Estrellas
0
Forks
0
Sin PR fusionados en 30 d

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de scripting/helloFrontier

Todos los issues de scripting/helloFrontier

Issues similares

Más issues de Documentation

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.