You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
⚠️ Keep in mind that due to Snap's strict confinement policy, installing Hugo with Snap will make it impossible to run the main Hugo commands (hugo mod, hugo new, hugo server) in directories located outside the user's home directory.
The text was updated successfully, but these errors were encountered:
I will add a note next to the Snap installation instructions, but this is inaccurate:
will make it impossible to run the main Hugo commands (hugo mod, hugo new, hugo server) in directories located outside the user's home directory.
The isolation provided by strict confinement does not prevent you from running the hugo commands in any directory. Instead, it prevents you from creating and building sites outside of your $HOME directory or outside of directories on removable media.
We have permission to offer classic confinement, but have taken the conservative approach to isolation--opening interfaces as needed is simple; closing them after release is not. There are currently around 13,000 snap installations in the wild, and the requests for classic confinement have been limited.
The Hugo snap package initially had a number of limitations related to dependencies (Git, Go, Dart Sass, etc.). @anthonyfok has done a remarkable job of removing these limitations, and I am grateful for his efforts.
Problem
Installing Hugo with Snap results in shortcomings, and these have already been abundantly discussed since 2016 (see issues gohugoio/hugo#10757 gohugoio/hugo#10337 gohugoio/hugo#5573 gohugoio/hugo#4336 gohugoio/hugo#3143 gohugoio/hugo#2532). Still, to this day there is no warning about that matter in the Snap section of the installation documentation.
Proposal
Add a warning saying something like
The text was updated successfully, but these errors were encountered: