#192 https setup docs

.github/workflows/deploy_staging.yml

@@ -4,7 +4,6 @@ on:
   workflow_dispatch:
   push:
     branches:
-      -	develop
-
+      - 'develop'
 jobs:
   uses: ./.github/workflows/deployment.yml

server/default.env

@@ -6,6 +6,15 @@
 # domain name where the server is hosted, including subdoman, without schema (http) and port
 # ATOMIC_DOMAIN=localhost
 
+# Port where it's running. Make sure you have the rights to run at this port.
+# Both an HTTPS and an HTTP port can be specified.
+
+# Set this to 80 if you're running this publicly
+# ATOMIC_PORT=9883
+
+# Set this to 443 if you're running this publicly
+# ATOMIC_PORT_HTTPS=9884
+
 # Whether you want to enable HTTPS. If set to true, the server will initialize Certification process on start using Let'sEncrypt. You'll need to set ATOMIC_EMAIL for this.
 # ATOMIC_HTTPS=false
 
@@ -24,12 +33,6 @@
 # Path to where your config will be stored.
 # ATOMIC_CONFIG_FILE_PATH="/Users/your_home_folder/.config/atomic/config.toml"
 
-# Port where it's running. Make sure you have the rights to run at this port.
-# Both an HTTPS and an HTTP port can be specified.
-# Both are necesssary during CERT_INIT
-# ATOMIC_PORT=9883
-# ATOMIC_PORT_HTTPS=9884
-
 # Local IP where it's running. Use :: if you want it to be public.
 # ATOMIC_IP=::
 

server/src/https.rs

@@ -151,7 +151,7 @@ pub async fn cert_init_server(config: &crate::config::Config) -> AtomicServerRes
     request_cert(config)
         .await
         .map_err(|e| format!("Certification init failed: {}", e))?;
-    tracing::warn!("HTTPS TLS Cert init sucesful! Stopping HTTP server, starting HTTPS...");
+    tracing::warn!("HTTPS TLS Cert init successful! Stopping HTTP server, starting HTTPS...");
     handle.stop(true).await;
     Ok(())
 }