CNAME flattening was popularized in part by Cloudflare.
We have used CNAME flattening successfully for years with multiple web-hosting providers.
DNS A records are a pre-WWW artifact necessary to resolve the apex domain example.invalid from www.example.invalid or radar.example.invalid.
To enable CNAME flattening on DNS records, first screenshot or otherwise backup DNS settings.
Don’t do this experiment during busy times, better to use on a little-used or test website first to ensure it works correctly with the proposed setup.
Determine the web address the web hosting provider puts the website at. E.g. for GitHub Pages it would be username.github.io or at Netlify username.netlify.app
Remove DNS A record for example.invalid that points to a specific IP address
Add a CNAME record pointing example.invalid to the server address from step #1
For GitHub username joe with GitHub Pages site at joe.github.io, with desired web address example.invalid: make a CNAME DNS record with example.invalid as an alias to joe.github.io.
Fortran
submodule
is supported by all popular Fortran compilers.
While designed as a way to better manage public/private exposure of variables in large Fortran modules, submodules can also be used to seamlessly switch in/out advanced functionality.
For example, the GEMINI 3-D ionospheric model was created with raw binary file I/O.
Since we had already written an object-oriented HDF5 interface, we integrated HDF5 file I/O into GEMINI.
To help ensure a smooth transition with seamless fallback to raw binary if HDF5 wasn’t available, we used Fortran submodule with CMake.
The user would call file_read and file_write subroutines with the same name, regardless of whether HDF5 was enabled.
CMake would switch in submodule files depending on whether HDF5 was working or not.
Rather than maintain a compiler feature table, in general we create simple test programs and verify that they compile–all automatically handled within CMake.
Insert into CMakeLists.txt
include(CheckSourceCompiles)set(CMAKE_TRY_COMPILE_TARGET_TYPESTATIC_LIBRARY)# save link time, only compile is needed
check_source_compiles(Fortran"module b
interface
module subroutine d
end subroutine d
end interface
end
submodule (b) c
contains
module procedure d
end
end
program a
end"f08submod)if(NOTf08submod)return() # or make FATAL_ERROR here
endif()
Selectively enable program functionality using submodule in CMakeLists.txt. This example is for HDF5:
While both
GitHub Pages
and
GitLab Pages
are adequate for most personal, group and project pages, when website size and / or traffic have grown beyond what is feasible for these solutions, a more comprehensive hosting provider like Netlify may be considered.
Netlify provides its own CDN, so those that had been using Cloudflare for DNS and CDN can configure Cloudflare to provide only DNS, if they so choose.
Netlify is free
for single users, allowing a private GitLab, GitHub or Bitbucket repo (or other suitable source) to deploy to a public custom domain HTTPS website.
SSL certificates can be user-provided or can be created through Netlify for your custom domain.
Netlify provides a
comparison
of GitHub Pages and Netlify.
GitLab Pages allows user choice of static site generator (Hugo, Jekyll, etc.).
GitHub Pages can using
GitHub Actions for Hugo.
GitLab Pages private repos have a monthly runtime quota.
Netlify has a
monthly traffic quota
on the free tier, and
monthly build quota.
For sites that are becoming very popular, GitHub Pages will simply want you to move elsewhere, while Netlify will have a paid plan to offer.
This process may be too burdensome for those with limited IT or bandwidth resources, or simply the lack to time to learn how to do this.
Netlify uses webhooks to detect a git push to the website GitLab repo, and then builds the site.
Netlify has a CDN and DDoS protection built-in.
Even if the other features aren’t needed, a key feature is the ability to have the website code in a private repo with unlimited public website deployments and traffic.
Build minute limits (such as on GitLab and Netlify) can legimately be worked around by building the site locally on your laptop and pushing the publish-ready HTML.
Note: This process may take down your site for a day or two if things go wrong.
Even under normal conditions, all site visitors may need to allow an HTTPS exception due to SSL certificate error since Netlify requires all DNS servers to update before generating the domain certificate.
if not already on GitLab, copy your website repo to GitLab (any name repo is fine).
disable Auto DevOps and ensure no file named .gitlab-ci.yml exists.
Login to Netlify using Gitlab, which will ask for your website repo.
pick a custom Netlify subdomain like mycompany.netlify.app. Ensure this site is totally working before proceeding.
Set Cloudflare or whatever your DNS provider is to point CNAME or A to mycompany.netlify.app (THIS IS THE PART THAT CAN TAKE YOUR MAIN WEBSITE DOWN!)
Under Netlify Domain Management → HTTPS → Verify DNS config, ensure the verification completes. Until the DNS change propagates worldwide, your main HTTPS domain visitors are getting SSL verification errors. They can use https://mycompany.invalid instead of https://mycompany.invalid temporarily. Do this at a low traffic time range!
If using Cloudflare CDN, the old records may point to DigitalOcean while the new records point to *.netlify.app
If the Git commits have already been pushed to remote, this process will require other users of the repo to reset, rebase or reclone, as for any Git operation that edits history.
If the Git commits have not already been pushed, then this process will not require extra steps from other repo users.
If one has installed
CMake for native Windows
AND has not installed CMake in Cygwin, Cygwin will try to use the Windows CMake, which will not work properly.
A solution is to install CMake in Cygwin to properly use CMake from Cygwin.
Assuming a Python package named “myprogram”, have a directory structure like
pyproject.toml
myprogram/
__init__.py
A minimal
pyproject.toml
is all that’s required for a PyPI Python package.
The package “version” number must be distinct for each release, or PyPI will prevent upload.
Intel oneAPI on Windows provides an easy way to use Fortran MPI on Windows.
The Intel oneAPI compile and link commands on Windows are distinct from those on Linux, perhaps reflecting the internal use of Visual Studio on Windows.
The HDF5 1.10.6 release changed the naming convention for the HDF5 Fortran library files on all operating systems.
old: hdf5hl_fortran.
new: hdf5_hl_fortran.
If experiencing trouble finding HDF5 with CMake, try
FindHDF5.cmake.
FindHDF5 specifically works with Intel compilers and HDF5 across operating systems including Windows.
The free open source SSH app
ConnectBot
allows connecting to SSH servers with port forwarding using public key authentication, including ED25519.
Sometimes it’s necessary to share SSH keypairs on multiple clients.
Perhaps the server owner isn’t willing to bother with more than one SSH client key. ConnectBot has an
open issue
since it cannot import OpenSSH keys created on a PC.
Generally users should create unique SSH public/private keypairs for each device.
Sharing keys between devices means if a device is compromised, deleting its key from ~/.ssh/authorized_keys on the SSH server disables all other devices sharing that key.
Workaround by creating an SSH keypair in ConnectBot.
Copy the ConnectBot-created public/private keypair to the PC ~/.ssh directory.
The stem (filename without extension) of the public and private keys must match.
The public key should have a .pub suffix, while the private key has no suffix.
Thereby the same SSH keypair is used on the phone with ConnectBot and the PC with OpenSSH client.