Finish

Nearly there - a few things to know before you sign in.

There are steps still to do before setup can finish.
Carry on where setup is
Signing in needs HTTPS
This page came over http://, and ITFlow only lets you sign in over https:// - so the sign-in page will turn you away until the site has a certificate (Let's Encrypt is free). Only for a test install that never leaves your network, change this line in config.php instead:
  • Your backup key Backups are locked with it. Keep a copy somewhere safe, away from this server - a backup can't be restored without it. It is in Maintenance > Backup too. config.php couldn't be written to, so there isn't one yet - Maintenance > Backup says how to add it.
  • Its address Links in emails and the client portal go to https://.$config_base_url in config.php before you invite clients.' ?> Put the address people reach ITFlow at in $config_base_url in config.php - links in emails go to it.

Once you are signed in

  1. Cron - ITFlow needs one crontab entry, for the user that owns its files. The install script adds it for you; by hand, it is: /dev/null", 'Crontab entry') ?> Then turn it on in Maintenance > Cron - it ships off.
  2. Mail - the mailboxes ITFlow sends from and turns emails into tickets from, in Admin > Settings > Mail.
  3. Backups - when they run, in Maintenance > Backup.
  4. Starter content - templates, categories and checklists to start from, in Maintenance > Starter Content.
  5. Your team - invite them from Admin > Users.
Once, now - so the project can see who uses ITFlow. Nothing else is ever sent. More
What is sent
'Company', 'website' => 'Website', 'city' => 'City', 'state' => 'State', 'country' => 'Country', 'currency' => 'Currency'] as $key => $label) { ?>
-' ?>
Install
a random id made for it