Pending configuration warning and reload

templates/base.html

@@ -168,6 +168,19 @@
     <!-- Main content -->
     <section class="content">
         <div class="container-fluid">
+          {% if pending_changes_warning %}
+            <div class="alert alert-warning" role="alert">
+                <h4 class="alert-heading">Update Required</h4>
+                <p>Your WireGuard settings have been modified. To apply these changes, please update the configuration and reload the WireGuard service.
+                </p>
+                <p>
+                  <a href="/tools/export_wireguard_config/?action=update_and_restart" class="btn btn-secondary">Update and restart service</a>
+              </p>
+              
+            </div>
+          {% endif %}
+        
+        
           
 
             {% block content %}{% endblock %}
@@ -179,7 +192,7 @@
   <footer class="main-footer">
     wireguard-webadmin 
     <div class="float-right d-none d-sm-inline-block">
-      <b>Version</b> 0.8 beta
+      <b>Version</b> 0.8.1 beta
     </div>
   </footer>
 

templates/wireguard/welcome.html

@@ -5,17 +5,15 @@
     <p>I've been working hard on it over the past week and plan to continue making corrections and finishing it in the coming days.</p>
     <p>Currently, it's quite functional, but there's still a need to polish various aspects of the interface to enhance usability.</p>
     <p>If you encounter any issues or have suggestions, please open an issue on GitHub so I can review it.</p>
-    <h2>Important Points to Note:</h2>
+    <h2>TODO list</h2>
     <ul>
         <li>The peers page does not yet display data from WireGuard such as the last handshake and data transfer.</li>
         <li>The verification of allowed IPs against the output of wg show has not yet been implemented. This will help detect configuration errors for crypto routing.</li>
-        <li>After editing a peer or server settings, go to the status page and click to update the WireGuard configurations, then restart the service. I still need to make this process more intuitive.</li>
         <li>The DNS server provided to the peer is still hardcoded.</li>
+        <li>AllowedIPs on client configuration side.</li>
     </ul>
-    <p>Your involvement and feedback are crucial to the development of wireguard_webadmin. Together, we can refine and enhance its functionality. Thank you for being part of this journey!</p>
+    
 
-    <h2>Don't Forget</h2>
-    <p>Remember to save your configuration changes and restart the service for them to take effect.</p>
     <p>Keep checking the GitHub page, I will be updating this project very soon.</p>
 
 {% endblock %}