* Added another check and better error handling to Template->get() to print a more useful message if a template is found but fails to parse.
* Moved some strings into the words file.
Signed-off-by: Digimer <digimer@alteeve.ca>
When you sync with a peer, this machine's data will be copied to and recorded on the peer's database. Data gathered by ScanCore will also be kept in sync on both dashboards, and any general purpose data collected by other dashboards while this one is offline will be copied back when this machine comes online. Should this machine ever be rebuilt, data recorded from before the rebuild will be automatically restored as well.
This will update this system using any available software repositories. You can also use this to create or load update packs to allow for the update of offline or air-gapped Anvil! systems.
Update the network configuration for this Striker.
#!string!striker_0059!#
</td>
</td>
</tr>
</tr>
</table>
</table>
<!-- end striker-setup -->
<!-- end striker-setup -->
<!-- start striker-sync -->
<!-- start striker-sync -->
<tablealign="center">
<tr>
<td>
Add or remove Striker peers.
</td>
</tr>
<tr>
<td>
Peer dashboards are Striker machines whose databases this Striker will use to record data. If this machine ever needs to be replaced, or goes offline for a period of time, it will automatically pull the data back from any peers that it is missing.
@ -57,13 +57,13 @@ NOTE: You must update the password of any other system using this host's
</key>
</key>
<keyname="message_0030">Failed to write the new password to the temporary file: [#!variable!file!#]. Please check the logs for details.</key>
<keyname="message_0030">Failed to write the new password to the temporary file: [#!variable!file!#]. Please check the logs for details.</key>
<keyname="message_0031">Beginning configuration of local system.</key>
<keyname="message_0031">Beginning configuration of local system.</key>
<keyname="message_0032"><![CDATA[Forgot your password?<br />Use '<span class="code">anvil-change-password</span>' from the console to reset it.]]></key>
<keyname="message_0032"></key>
<keyname="message_0033">Log out</key>
<keyname="message_0033"></key>
<keyname="message_0034"><![CDATA[Logged in as: [<span class="fixed_width">#!data!sys::users::user_name!#</span>]]]></key>
<keyname="message_0034"><![CDATA[Logged in as: [<span class="fixed_width">#!data!sys::users::user_name!#</span>]]]></key>
<keyname="message_0035">Welcome!</key>
<keyname="message_0035"></key>
<keyname="message_0036">Create or manage Anvil! systems</key>
<keyname="message_0036"></key>
<keyname="message_0037">Manage this Striker system and sync with others</key>
<keyname="striker_0055">When you sync with a peer, this machine's data will be copied to and recorded on the peer's database. Data gathered by ScanCore will also be kept in sync on both dashboards, and any general purpose data collected by other dashboards while this one is offline will be copied back when this machine comes online. Should this machine ever be rebuilt, data recorded from before the rebuild will be automatically restored as well.</key>
<keyname="striker_0056">Update this Striker</key>
<keyname="striker_0057">This will update this system using any available software repositories. You can also use this to create or load update packs to allow for the update of offline or air-gapped Anvil! systems.</key>
<keyname="striker_0058">Configure this Striker</key>
<keyname="striker_0059">Update the network configuration for this Striker.</key>
<keyname="striker_0060">Welcome!</key>
<keyname="striker_0061">Create or manage Anvil! systems</key>
<keyname="striker_0062">Manage this Striker system and sync with others</key>
<keyname="striker_0063">Log out</key>
<keyname="striker_0064">Help and support</key>
<keyname="striker_0065"><![CDATA[Forgot your password?<br />Use '<span class="code">anvil-change-password</span>' from the console to reset it.]]></key>
<keyname="striker_0066">Access to this machine via: [#!variable!network!#].</key>
<keyname="striker_0067"></key>
<keyname="striker_0068"></key>
<keyname="striker_0069"></key>
<keyname="striker_0070"></key>
<!-- Strings used by jobs -->
<!-- Strings used by jobs -->
<keyname="job_0001">Configure Network</key>
<keyname="job_0001">Configure Network</key>
@ -408,6 +427,7 @@ Here we will inject 't_0006', which injects 't_0001' which has a variable: [#!st
<keyname="error_0028"><![CDATA[There appears to be a problem with Striker. The login failed, please check: [<span class="code">#!data!sys::log_file!#</span>] for details.]]></key>
<keyname="error_0028"><![CDATA[There appears to be a problem with Striker. The login failed, please check: [<span class="code">#!data!sys::log_file!#</span>] for details.]]></key>
<keyname="error_0029"><![CDATA[Failed to find the template: [<span class="code">#!variable!template!#</span>] in the template file: [<span class="code">#!variable!file!#</span>].]]></key>
<keyname="error_0029"><![CDATA[Failed to find the template: [<span class="code">#!variable!template!#</span>] in the template file: [<span class="code">#!variable!file!#</span>].]]></key>
<keyname="error_0030"><![CDATA[Failed to process the template: [<span class="code">#!variable!template!#</span>] in the template file: [<span class="code">#!variable!file!#</span>]. Details of the problem should be in: [<span class="code">#!data!sys::log_file!#</span>].]]></key>
<!-- These are works and strings used by javascript/jqery -->
<!-- These are works and strings used by javascript/jqery -->