Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
blocks:server:publish-on-internet [2023-01-06 20:13]
admin [Publishing an in-house Blocks server on the Internet]
blocks:server:publish-on-internet [2023-02-09 10:04] (current)
admin Added link to CNAME setup
Line 10: Line 10:
   * A [[https://developers.cloudflare.com/cloudflare-one/connections/connect-apps/|VPN-like tunnel]], making your in-house Blocks server accessible from the internet.   * A [[https://developers.cloudflare.com/cloudflare-one/connections/connect-apps/|VPN-like tunnel]], making your in-house Blocks server accessible from the internet.
   * Certificate for secure server access (HTTPS).   * Certificate for secure server access (HTTPS).
-  * Caching of many resources, such as images, for improved performance and reducer load on your Blocks server.+  * Caching of many resources, such as images, for improved performance and reduce load on your Blocks server.
  
-These services are all currently provided for free by Cloudflare. +These services are all currently provided for free by Cloudflare. This guide assumes you can use Cloudflare also as your DNS provider. However, when that's not an option, you can use a slightly different method based on a [[https://developers.cloudflare.com/cloudflare-one/faq/cloudflare-tunnels-faq/#how-can-tunnel-be-used-with-partial-dns-cname-setup|partial DNS (CNAME Setup)]].
  
 ==== Prerequisites ==== ==== Prerequisites ====
Line 42: Line 42:
   - Specify a subdomain (if desired) and domain name for the connector.    - Specify a subdomain (if desired) and domain name for the connector. 
   - Wait for the tunnel to be created and show a "healthy" status.   - Wait for the tunnel to be created and show a "healthy" status.
-  - Open a browser using https://<subdomain>.<domain>/edit to access the editor. +  - Open a browser using <code>https://<subdomain>.<domain>/edit</code> to access the editor. 
-  - Connect spots using https://<subdomain>.<domain>/spot. +  - Connect spots using <code>https://<subdomain>.<domain>/spot </code>.
 Substitute <subdomain>.<domain> above with your subdomain (if any) and domain name. Substitute <subdomain>.<domain> above with your subdomain (if any) and domain name.
  
 You're stongly advised to enforce the use of https on all connections, following instructions found [[https://developers.cloudflare.com/ssl/edge-certificates/additional-options/always-use-https/|here]]. Using HTTPS avoids sending passwords and other potentially sensitive data as clear text. You're stongly advised to enforce the use of https on all connections, following instructions found [[https://developers.cloudflare.com/ssl/edge-certificates/additional-options/always-use-https/|here]]. Using HTTPS avoids sending passwords and other potentially sensitive data as clear text.
  
-:!: IMPORTANTMake sure you have set a secure password for all users of your Blocks server, so you're not using the default "pixi" password for the admin user.+:!: **IMPORTANT**: Make sure you have set a secure password for all users of your Blocks server, so you're not using the default "pixi" password for the admin user.
  
 ==== Recommended Enhancements ==== ==== Recommended Enhancements ====