2018-11-14 09:44:04 +00:00
|
|
|
// Copyright 2018 The Hugo Authors. All rights reserved.
|
|
|
|
//
|
|
|
|
// Licensed under the Apache License, Version 2.0 (the "License");
|
|
|
|
// you may not use this file except in compliance with the License.
|
|
|
|
// You may obtain a copy of the License at
|
|
|
|
// http://www.apache.org/licenses/LICENSE-2.0
|
|
|
|
//
|
|
|
|
// Unless required by applicable law or agreed to in writing, software
|
|
|
|
// distributed under the License is distributed on an "AS IS" BASIS,
|
|
|
|
// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
|
|
// See the License for the specific language governing permissions and
|
|
|
|
// limitations under the License.
|
|
|
|
|
|
|
|
package filecache
|
|
|
|
|
|
|
|
import (
|
|
|
|
"path"
|
|
|
|
"path/filepath"
|
|
|
|
"strings"
|
2018-11-14 09:51:41 +00:00
|
|
|
"time"
|
2018-11-14 09:44:04 +00:00
|
|
|
|
Add Hugo Modules
This commit implements Hugo Modules.
This is a broad subject, but some keywords include:
* A new `module` configuration section where you can import almost anything. You can configure both your own file mounts nd the file mounts of the modules you import. This is the new recommended way of configuring what you earlier put in `configDir`, `staticDir` etc. And it also allows you to mount folders in non-Hugo-projects, e.g. the `SCSS` folder in the Bootstrap GitHub project.
* A module consists of a set of mounts to the standard 7 component types in Hugo: `static`, `content`, `layouts`, `data`, `assets`, `i18n`, and `archetypes`. Yes, Theme Components can now include content, which should be very useful, especially in bigger multilingual projects.
* Modules not in your local file cache will be downloaded automatically and even "hot replaced" while the server is running.
* Hugo Modules supports and encourages semver versioned modules, and uses the minimal version selection algorithm to resolve versions.
* A new set of CLI commands are provided to manage all of this: `hugo mod init`, `hugo mod get`, `hugo mod graph`, `hugo mod tidy`, and `hugo mod vendor`.
All of the above is backed by Go Modules.
Fixes #5973
Fixes #5996
Fixes #6010
Fixes #5911
Fixes #5940
Fixes #6074
Fixes #6082
Fixes #6092
2019-05-03 07:16:58 +00:00
|
|
|
"github.com/gohugoio/hugo/config"
|
|
|
|
|
2018-11-14 09:44:04 +00:00
|
|
|
"github.com/gohugoio/hugo/helpers"
|
|
|
|
|
2018-11-27 23:17:43 +00:00
|
|
|
"github.com/mitchellh/mapstructure"
|
2018-11-14 09:44:04 +00:00
|
|
|
"github.com/pkg/errors"
|
|
|
|
"github.com/spf13/afero"
|
|
|
|
)
|
|
|
|
|
|
|
|
const (
|
|
|
|
cachesConfigKey = "caches"
|
|
|
|
|
|
|
|
resourcesGenDir = ":resourceDir/_gen"
|
|
|
|
)
|
|
|
|
|
Add Hugo Modules
This commit implements Hugo Modules.
This is a broad subject, but some keywords include:
* A new `module` configuration section where you can import almost anything. You can configure both your own file mounts nd the file mounts of the modules you import. This is the new recommended way of configuring what you earlier put in `configDir`, `staticDir` etc. And it also allows you to mount folders in non-Hugo-projects, e.g. the `SCSS` folder in the Bootstrap GitHub project.
* A module consists of a set of mounts to the standard 7 component types in Hugo: `static`, `content`, `layouts`, `data`, `assets`, `i18n`, and `archetypes`. Yes, Theme Components can now include content, which should be very useful, especially in bigger multilingual projects.
* Modules not in your local file cache will be downloaded automatically and even "hot replaced" while the server is running.
* Hugo Modules supports and encourages semver versioned modules, and uses the minimal version selection algorithm to resolve versions.
* A new set of CLI commands are provided to manage all of this: `hugo mod init`, `hugo mod get`, `hugo mod graph`, `hugo mod tidy`, and `hugo mod vendor`.
All of the above is backed by Go Modules.
Fixes #5973
Fixes #5996
Fixes #6010
Fixes #5911
Fixes #5940
Fixes #6074
Fixes #6082
Fixes #6092
2019-05-03 07:16:58 +00:00
|
|
|
var defaultCacheConfig = Config{
|
2018-11-14 09:44:04 +00:00
|
|
|
MaxAge: -1, // Never expire
|
2018-11-14 16:18:32 +00:00
|
|
|
Dir: ":cacheDir/:project",
|
2018-11-14 09:44:04 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
const (
|
|
|
|
cacheKeyGetJSON = "getjson"
|
|
|
|
cacheKeyGetCSV = "getcsv"
|
|
|
|
cacheKeyImages = "images"
|
|
|
|
cacheKeyAssets = "assets"
|
Add Hugo Modules
This commit implements Hugo Modules.
This is a broad subject, but some keywords include:
* A new `module` configuration section where you can import almost anything. You can configure both your own file mounts nd the file mounts of the modules you import. This is the new recommended way of configuring what you earlier put in `configDir`, `staticDir` etc. And it also allows you to mount folders in non-Hugo-projects, e.g. the `SCSS` folder in the Bootstrap GitHub project.
* A module consists of a set of mounts to the standard 7 component types in Hugo: `static`, `content`, `layouts`, `data`, `assets`, `i18n`, and `archetypes`. Yes, Theme Components can now include content, which should be very useful, especially in bigger multilingual projects.
* Modules not in your local file cache will be downloaded automatically and even "hot replaced" while the server is running.
* Hugo Modules supports and encourages semver versioned modules, and uses the minimal version selection algorithm to resolve versions.
* A new set of CLI commands are provided to manage all of this: `hugo mod init`, `hugo mod get`, `hugo mod graph`, `hugo mod tidy`, and `hugo mod vendor`.
All of the above is backed by Go Modules.
Fixes #5973
Fixes #5996
Fixes #6010
Fixes #5911
Fixes #5940
Fixes #6074
Fixes #6082
Fixes #6092
2019-05-03 07:16:58 +00:00
|
|
|
cacheKeyModules = "modules"
|
2018-11-14 09:44:04 +00:00
|
|
|
)
|
|
|
|
|
Add Hugo Modules
This commit implements Hugo Modules.
This is a broad subject, but some keywords include:
* A new `module` configuration section where you can import almost anything. You can configure both your own file mounts nd the file mounts of the modules you import. This is the new recommended way of configuring what you earlier put in `configDir`, `staticDir` etc. And it also allows you to mount folders in non-Hugo-projects, e.g. the `SCSS` folder in the Bootstrap GitHub project.
* A module consists of a set of mounts to the standard 7 component types in Hugo: `static`, `content`, `layouts`, `data`, `assets`, `i18n`, and `archetypes`. Yes, Theme Components can now include content, which should be very useful, especially in bigger multilingual projects.
* Modules not in your local file cache will be downloaded automatically and even "hot replaced" while the server is running.
* Hugo Modules supports and encourages semver versioned modules, and uses the minimal version selection algorithm to resolve versions.
* A new set of CLI commands are provided to manage all of this: `hugo mod init`, `hugo mod get`, `hugo mod graph`, `hugo mod tidy`, and `hugo mod vendor`.
All of the above is backed by Go Modules.
Fixes #5973
Fixes #5996
Fixes #6010
Fixes #5911
Fixes #5940
Fixes #6074
Fixes #6082
Fixes #6092
2019-05-03 07:16:58 +00:00
|
|
|
type Configs map[string]Config
|
|
|
|
|
|
|
|
func (c Configs) CacheDirModules() string {
|
|
|
|
return c[cacheKeyModules].Dir
|
|
|
|
}
|
|
|
|
|
|
|
|
var defaultCacheConfigs = Configs{
|
|
|
|
cacheKeyModules: {
|
|
|
|
MaxAge: -1,
|
|
|
|
Dir: ":cacheDir/modules",
|
|
|
|
},
|
2018-11-14 09:44:04 +00:00
|
|
|
cacheKeyGetJSON: defaultCacheConfig,
|
|
|
|
cacheKeyGetCSV: defaultCacheConfig,
|
2019-03-23 19:15:06 +00:00
|
|
|
cacheKeyImages: {
|
2018-11-14 09:44:04 +00:00
|
|
|
MaxAge: -1,
|
|
|
|
Dir: resourcesGenDir,
|
|
|
|
},
|
2019-03-23 19:15:06 +00:00
|
|
|
cacheKeyAssets: {
|
2018-11-14 09:44:04 +00:00
|
|
|
MaxAge: -1,
|
|
|
|
Dir: resourcesGenDir,
|
|
|
|
},
|
|
|
|
}
|
|
|
|
|
Add Hugo Modules
This commit implements Hugo Modules.
This is a broad subject, but some keywords include:
* A new `module` configuration section where you can import almost anything. You can configure both your own file mounts nd the file mounts of the modules you import. This is the new recommended way of configuring what you earlier put in `configDir`, `staticDir` etc. And it also allows you to mount folders in non-Hugo-projects, e.g. the `SCSS` folder in the Bootstrap GitHub project.
* A module consists of a set of mounts to the standard 7 component types in Hugo: `static`, `content`, `layouts`, `data`, `assets`, `i18n`, and `archetypes`. Yes, Theme Components can now include content, which should be very useful, especially in bigger multilingual projects.
* Modules not in your local file cache will be downloaded automatically and even "hot replaced" while the server is running.
* Hugo Modules supports and encourages semver versioned modules, and uses the minimal version selection algorithm to resolve versions.
* A new set of CLI commands are provided to manage all of this: `hugo mod init`, `hugo mod get`, `hugo mod graph`, `hugo mod tidy`, and `hugo mod vendor`.
All of the above is backed by Go Modules.
Fixes #5973
Fixes #5996
Fixes #6010
Fixes #5911
Fixes #5940
Fixes #6074
Fixes #6082
Fixes #6092
2019-05-03 07:16:58 +00:00
|
|
|
type Config struct {
|
2018-11-14 09:44:04 +00:00
|
|
|
// Max age of cache entries in this cache. Any items older than this will
|
|
|
|
// be removed and not returned from the cache.
|
2018-11-14 09:51:41 +00:00
|
|
|
// a negative value means forever, 0 means cache is disabled.
|
|
|
|
MaxAge time.Duration
|
2018-11-14 09:44:04 +00:00
|
|
|
|
|
|
|
// The directory where files are stored.
|
|
|
|
Dir string
|
2018-11-23 08:16:42 +00:00
|
|
|
|
|
|
|
// Will resources/_gen will get its own composite filesystem that
|
|
|
|
// also checks any theme.
|
|
|
|
isResourceDir bool
|
2018-11-14 09:44:04 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
// GetJSONCache gets the file cache for getJSON.
|
|
|
|
func (f Caches) GetJSONCache() *Cache {
|
|
|
|
return f[cacheKeyGetJSON]
|
|
|
|
}
|
|
|
|
|
|
|
|
// GetCSVCache gets the file cache for getCSV.
|
|
|
|
func (f Caches) GetCSVCache() *Cache {
|
|
|
|
return f[cacheKeyGetCSV]
|
|
|
|
}
|
|
|
|
|
|
|
|
// ImageCache gets the file cache for processed images.
|
|
|
|
func (f Caches) ImageCache() *Cache {
|
|
|
|
return f[cacheKeyImages]
|
|
|
|
}
|
|
|
|
|
Add Hugo Modules
This commit implements Hugo Modules.
This is a broad subject, but some keywords include:
* A new `module` configuration section where you can import almost anything. You can configure both your own file mounts nd the file mounts of the modules you import. This is the new recommended way of configuring what you earlier put in `configDir`, `staticDir` etc. And it also allows you to mount folders in non-Hugo-projects, e.g. the `SCSS` folder in the Bootstrap GitHub project.
* A module consists of a set of mounts to the standard 7 component types in Hugo: `static`, `content`, `layouts`, `data`, `assets`, `i18n`, and `archetypes`. Yes, Theme Components can now include content, which should be very useful, especially in bigger multilingual projects.
* Modules not in your local file cache will be downloaded automatically and even "hot replaced" while the server is running.
* Hugo Modules supports and encourages semver versioned modules, and uses the minimal version selection algorithm to resolve versions.
* A new set of CLI commands are provided to manage all of this: `hugo mod init`, `hugo mod get`, `hugo mod graph`, `hugo mod tidy`, and `hugo mod vendor`.
All of the above is backed by Go Modules.
Fixes #5973
Fixes #5996
Fixes #6010
Fixes #5911
Fixes #5940
Fixes #6074
Fixes #6082
Fixes #6092
2019-05-03 07:16:58 +00:00
|
|
|
// ModulesCache gets the file cache for Hugo Modules.
|
|
|
|
func (f Caches) ModulesCache() *Cache {
|
|
|
|
return f[cacheKeyModules]
|
|
|
|
}
|
|
|
|
|
2018-11-14 09:44:04 +00:00
|
|
|
// AssetsCache gets the file cache for assets (processed resources, SCSS etc.).
|
|
|
|
func (f Caches) AssetsCache() *Cache {
|
|
|
|
return f[cacheKeyAssets]
|
|
|
|
}
|
|
|
|
|
Add Hugo Modules
This commit implements Hugo Modules.
This is a broad subject, but some keywords include:
* A new `module` configuration section where you can import almost anything. You can configure both your own file mounts nd the file mounts of the modules you import. This is the new recommended way of configuring what you earlier put in `configDir`, `staticDir` etc. And it also allows you to mount folders in non-Hugo-projects, e.g. the `SCSS` folder in the Bootstrap GitHub project.
* A module consists of a set of mounts to the standard 7 component types in Hugo: `static`, `content`, `layouts`, `data`, `assets`, `i18n`, and `archetypes`. Yes, Theme Components can now include content, which should be very useful, especially in bigger multilingual projects.
* Modules not in your local file cache will be downloaded automatically and even "hot replaced" while the server is running.
* Hugo Modules supports and encourages semver versioned modules, and uses the minimal version selection algorithm to resolve versions.
* A new set of CLI commands are provided to manage all of this: `hugo mod init`, `hugo mod get`, `hugo mod graph`, `hugo mod tidy`, and `hugo mod vendor`.
All of the above is backed by Go Modules.
Fixes #5973
Fixes #5996
Fixes #6010
Fixes #5911
Fixes #5940
Fixes #6074
Fixes #6082
Fixes #6092
2019-05-03 07:16:58 +00:00
|
|
|
func DecodeConfig(fs afero.Fs, cfg config.Provider) (Configs, error) {
|
|
|
|
c := make(Configs)
|
2018-11-14 09:44:04 +00:00
|
|
|
valid := make(map[string]bool)
|
|
|
|
// Add defaults
|
|
|
|
for k, v := range defaultCacheConfigs {
|
|
|
|
c[k] = v
|
|
|
|
valid[k] = true
|
|
|
|
}
|
|
|
|
|
|
|
|
m := cfg.GetStringMap(cachesConfigKey)
|
|
|
|
|
Add Hugo Modules
This commit implements Hugo Modules.
This is a broad subject, but some keywords include:
* A new `module` configuration section where you can import almost anything. You can configure both your own file mounts nd the file mounts of the modules you import. This is the new recommended way of configuring what you earlier put in `configDir`, `staticDir` etc. And it also allows you to mount folders in non-Hugo-projects, e.g. the `SCSS` folder in the Bootstrap GitHub project.
* A module consists of a set of mounts to the standard 7 component types in Hugo: `static`, `content`, `layouts`, `data`, `assets`, `i18n`, and `archetypes`. Yes, Theme Components can now include content, which should be very useful, especially in bigger multilingual projects.
* Modules not in your local file cache will be downloaded automatically and even "hot replaced" while the server is running.
* Hugo Modules supports and encourages semver versioned modules, and uses the minimal version selection algorithm to resolve versions.
* A new set of CLI commands are provided to manage all of this: `hugo mod init`, `hugo mod get`, `hugo mod graph`, `hugo mod tidy`, and `hugo mod vendor`.
All of the above is backed by Go Modules.
Fixes #5973
Fixes #5996
Fixes #6010
Fixes #5911
Fixes #5940
Fixes #6074
Fixes #6082
Fixes #6092
2019-05-03 07:16:58 +00:00
|
|
|
_, isOsFs := fs.(*afero.OsFs)
|
2018-11-14 09:44:04 +00:00
|
|
|
|
|
|
|
for k, v := range m {
|
|
|
|
cc := defaultCacheConfig
|
|
|
|
|
2018-11-14 09:51:41 +00:00
|
|
|
dc := &mapstructure.DecoderConfig{
|
|
|
|
Result: &cc,
|
|
|
|
DecodeHook: mapstructure.StringToTimeDurationHookFunc(),
|
|
|
|
WeaklyTypedInput: true,
|
|
|
|
}
|
|
|
|
|
|
|
|
decoder, err := mapstructure.NewDecoder(dc)
|
|
|
|
if err != nil {
|
|
|
|
return c, err
|
|
|
|
}
|
|
|
|
|
|
|
|
if err := decoder.Decode(v); err != nil {
|
2018-11-14 09:44:04 +00:00
|
|
|
return nil, err
|
|
|
|
}
|
|
|
|
|
|
|
|
if cc.Dir == "" {
|
|
|
|
return c, errors.New("must provide cache Dir")
|
|
|
|
}
|
|
|
|
|
|
|
|
name := strings.ToLower(k)
|
|
|
|
if !valid[name] {
|
|
|
|
return nil, errors.Errorf("%q is not a valid cache name", name)
|
|
|
|
}
|
|
|
|
|
|
|
|
c[name] = cc
|
|
|
|
}
|
|
|
|
|
|
|
|
// This is a very old flag in Hugo, but we need to respect it.
|
|
|
|
disabled := cfg.GetBool("ignoreCache")
|
|
|
|
|
|
|
|
for k, v := range c {
|
2018-11-14 16:18:32 +00:00
|
|
|
dir := filepath.ToSlash(filepath.Clean(v.Dir))
|
|
|
|
hadSlash := strings.HasPrefix(dir, "/")
|
2018-11-14 09:44:04 +00:00
|
|
|
parts := strings.Split(dir, "/")
|
|
|
|
|
2018-11-14 16:18:32 +00:00
|
|
|
for i, part := range parts {
|
|
|
|
if strings.HasPrefix(part, ":") {
|
Add Hugo Modules
This commit implements Hugo Modules.
This is a broad subject, but some keywords include:
* A new `module` configuration section where you can import almost anything. You can configure both your own file mounts nd the file mounts of the modules you import. This is the new recommended way of configuring what you earlier put in `configDir`, `staticDir` etc. And it also allows you to mount folders in non-Hugo-projects, e.g. the `SCSS` folder in the Bootstrap GitHub project.
* A module consists of a set of mounts to the standard 7 component types in Hugo: `static`, `content`, `layouts`, `data`, `assets`, `i18n`, and `archetypes`. Yes, Theme Components can now include content, which should be very useful, especially in bigger multilingual projects.
* Modules not in your local file cache will be downloaded automatically and even "hot replaced" while the server is running.
* Hugo Modules supports and encourages semver versioned modules, and uses the minimal version selection algorithm to resolve versions.
* A new set of CLI commands are provided to manage all of this: `hugo mod init`, `hugo mod get`, `hugo mod graph`, `hugo mod tidy`, and `hugo mod vendor`.
All of the above is backed by Go Modules.
Fixes #5973
Fixes #5996
Fixes #6010
Fixes #5911
Fixes #5940
Fixes #6074
Fixes #6082
Fixes #6092
2019-05-03 07:16:58 +00:00
|
|
|
resolved, isResource, err := resolveDirPlaceholder(fs, cfg, part)
|
2018-11-14 16:18:32 +00:00
|
|
|
if err != nil {
|
|
|
|
return c, err
|
|
|
|
}
|
2018-11-23 08:16:42 +00:00
|
|
|
if isResource {
|
|
|
|
v.isResourceDir = true
|
|
|
|
}
|
2018-11-14 16:18:32 +00:00
|
|
|
parts[i] = resolved
|
2018-11-14 09:44:04 +00:00
|
|
|
}
|
2018-11-14 16:18:32 +00:00
|
|
|
}
|
2018-11-14 09:44:04 +00:00
|
|
|
|
2018-11-14 16:18:32 +00:00
|
|
|
dir = path.Join(parts...)
|
|
|
|
if hadSlash {
|
|
|
|
dir = "/" + dir
|
|
|
|
}
|
|
|
|
v.Dir = filepath.Clean(filepath.FromSlash(dir))
|
2018-11-14 09:44:04 +00:00
|
|
|
|
2018-11-23 08:16:42 +00:00
|
|
|
if !v.isResourceDir {
|
|
|
|
if isOsFs && !filepath.IsAbs(v.Dir) {
|
|
|
|
return c, errors.Errorf("%q must resolve to an absolute directory", v.Dir)
|
|
|
|
}
|
2018-11-14 09:44:04 +00:00
|
|
|
|
2018-11-23 08:16:42 +00:00
|
|
|
// Avoid cache in root, e.g. / (Unix) or c:\ (Windows)
|
|
|
|
if len(strings.TrimPrefix(v.Dir, filepath.VolumeName(v.Dir))) == 1 {
|
|
|
|
return c, errors.Errorf("%q is a root folder and not allowed as cache dir", v.Dir)
|
|
|
|
}
|
2018-11-14 10:53:45 +00:00
|
|
|
}
|
|
|
|
|
Add Hugo Modules
This commit implements Hugo Modules.
This is a broad subject, but some keywords include:
* A new `module` configuration section where you can import almost anything. You can configure both your own file mounts nd the file mounts of the modules you import. This is the new recommended way of configuring what you earlier put in `configDir`, `staticDir` etc. And it also allows you to mount folders in non-Hugo-projects, e.g. the `SCSS` folder in the Bootstrap GitHub project.
* A module consists of a set of mounts to the standard 7 component types in Hugo: `static`, `content`, `layouts`, `data`, `assets`, `i18n`, and `archetypes`. Yes, Theme Components can now include content, which should be very useful, especially in bigger multilingual projects.
* Modules not in your local file cache will be downloaded automatically and even "hot replaced" while the server is running.
* Hugo Modules supports and encourages semver versioned modules, and uses the minimal version selection algorithm to resolve versions.
* A new set of CLI commands are provided to manage all of this: `hugo mod init`, `hugo mod get`, `hugo mod graph`, `hugo mod tidy`, and `hugo mod vendor`.
All of the above is backed by Go Modules.
Fixes #5973
Fixes #5996
Fixes #6010
Fixes #5911
Fixes #5940
Fixes #6074
Fixes #6082
Fixes #6092
2019-05-03 07:16:58 +00:00
|
|
|
if !strings.HasPrefix(v.Dir, "_gen") {
|
|
|
|
// We do cache eviction (file removes) and since the user can set
|
|
|
|
// his/hers own cache directory, we really want to make sure
|
|
|
|
// we do not delete any files that do not belong to this cache.
|
|
|
|
// We do add the cache name as the root, but this is an extra safe
|
|
|
|
// guard. We skip the files inside /resources/_gen/ because
|
|
|
|
// that would be breaking.
|
|
|
|
v.Dir = filepath.Join(v.Dir, filecacheRootDirname, k)
|
|
|
|
} else {
|
|
|
|
v.Dir = filepath.Join(v.Dir, k)
|
|
|
|
}
|
|
|
|
|
2018-11-14 09:44:04 +00:00
|
|
|
if disabled {
|
|
|
|
v.MaxAge = 0
|
|
|
|
}
|
|
|
|
|
|
|
|
c[k] = v
|
|
|
|
}
|
|
|
|
|
|
|
|
return c, nil
|
|
|
|
}
|
|
|
|
|
|
|
|
// Resolves :resourceDir => /myproject/resources etc., :cacheDir => ...
|
Add Hugo Modules
This commit implements Hugo Modules.
This is a broad subject, but some keywords include:
* A new `module` configuration section where you can import almost anything. You can configure both your own file mounts nd the file mounts of the modules you import. This is the new recommended way of configuring what you earlier put in `configDir`, `staticDir` etc. And it also allows you to mount folders in non-Hugo-projects, e.g. the `SCSS` folder in the Bootstrap GitHub project.
* A module consists of a set of mounts to the standard 7 component types in Hugo: `static`, `content`, `layouts`, `data`, `assets`, `i18n`, and `archetypes`. Yes, Theme Components can now include content, which should be very useful, especially in bigger multilingual projects.
* Modules not in your local file cache will be downloaded automatically and even "hot replaced" while the server is running.
* Hugo Modules supports and encourages semver versioned modules, and uses the minimal version selection algorithm to resolve versions.
* A new set of CLI commands are provided to manage all of this: `hugo mod init`, `hugo mod get`, `hugo mod graph`, `hugo mod tidy`, and `hugo mod vendor`.
All of the above is backed by Go Modules.
Fixes #5973
Fixes #5996
Fixes #6010
Fixes #5911
Fixes #5940
Fixes #6074
Fixes #6082
Fixes #6092
2019-05-03 07:16:58 +00:00
|
|
|
func resolveDirPlaceholder(fs afero.Fs, cfg config.Provider, placeholder string) (cacheDir string, isResource bool, err error) {
|
|
|
|
workingDir := cfg.GetString("workingDir")
|
|
|
|
|
2018-11-14 09:44:04 +00:00
|
|
|
switch strings.ToLower(placeholder) {
|
|
|
|
case ":resourcedir":
|
2018-11-23 08:16:42 +00:00
|
|
|
return "", true, nil
|
2018-11-14 09:44:04 +00:00
|
|
|
case ":cachedir":
|
Add Hugo Modules
This commit implements Hugo Modules.
This is a broad subject, but some keywords include:
* A new `module` configuration section where you can import almost anything. You can configure both your own file mounts nd the file mounts of the modules you import. This is the new recommended way of configuring what you earlier put in `configDir`, `staticDir` etc. And it also allows you to mount folders in non-Hugo-projects, e.g. the `SCSS` folder in the Bootstrap GitHub project.
* A module consists of a set of mounts to the standard 7 component types in Hugo: `static`, `content`, `layouts`, `data`, `assets`, `i18n`, and `archetypes`. Yes, Theme Components can now include content, which should be very useful, especially in bigger multilingual projects.
* Modules not in your local file cache will be downloaded automatically and even "hot replaced" while the server is running.
* Hugo Modules supports and encourages semver versioned modules, and uses the minimal version selection algorithm to resolve versions.
* A new set of CLI commands are provided to manage all of this: `hugo mod init`, `hugo mod get`, `hugo mod graph`, `hugo mod tidy`, and `hugo mod vendor`.
All of the above is backed by Go Modules.
Fixes #5973
Fixes #5996
Fixes #6010
Fixes #5911
Fixes #5940
Fixes #6074
Fixes #6082
Fixes #6092
2019-05-03 07:16:58 +00:00
|
|
|
d, err := helpers.GetCacheDir(fs, cfg)
|
2018-11-23 08:16:42 +00:00
|
|
|
return d, false, err
|
2018-11-14 16:18:32 +00:00
|
|
|
case ":project":
|
Add Hugo Modules
This commit implements Hugo Modules.
This is a broad subject, but some keywords include:
* A new `module` configuration section where you can import almost anything. You can configure both your own file mounts nd the file mounts of the modules you import. This is the new recommended way of configuring what you earlier put in `configDir`, `staticDir` etc. And it also allows you to mount folders in non-Hugo-projects, e.g. the `SCSS` folder in the Bootstrap GitHub project.
* A module consists of a set of mounts to the standard 7 component types in Hugo: `static`, `content`, `layouts`, `data`, `assets`, `i18n`, and `archetypes`. Yes, Theme Components can now include content, which should be very useful, especially in bigger multilingual projects.
* Modules not in your local file cache will be downloaded automatically and even "hot replaced" while the server is running.
* Hugo Modules supports and encourages semver versioned modules, and uses the minimal version selection algorithm to resolve versions.
* A new set of CLI commands are provided to manage all of this: `hugo mod init`, `hugo mod get`, `hugo mod graph`, `hugo mod tidy`, and `hugo mod vendor`.
All of the above is backed by Go Modules.
Fixes #5973
Fixes #5996
Fixes #6010
Fixes #5911
Fixes #5940
Fixes #6074
Fixes #6082
Fixes #6092
2019-05-03 07:16:58 +00:00
|
|
|
return filepath.Base(workingDir), false, nil
|
2018-11-14 09:44:04 +00:00
|
|
|
}
|
|
|
|
|
2018-11-23 08:16:42 +00:00
|
|
|
return "", false, errors.Errorf("%q is not a valid placeholder (valid values are :cacheDir or :resourceDir)", placeholder)
|
2018-11-14 09:44:04 +00:00
|
|
|
}
|