ipfs/kubo

changes in the default configuration do not propagate to the upgrades of earlier go-ipfs versions

Open

#3707 opened on Feb 19, 2017

View on GitHub
 (7 comments) (0 reactions) (0 assignees)Go (13,906 stars) (2,725 forks)batch import
help wantedkind/bug

Description

Version information

go-ipfs version: 0.4.5-
Repo version: 5
System version: amd64/windows
Golang version: go1.7.4

Type: bug (misconfiguration)

Priority: ?

Description

The chat log from fedwiki/wiki-client#173 says that changes in the default configuration of go-ipfs do not automatically apply to users of earlier versions when they upgrade. Click to enlarge:

(the chat log)

It means that earlier adopters do not automatically get config-related features (such as CORS from #2778) and it makes those features less reliable.

For example, I cannot reliably host a 360°×180° photo for a Pannellum-based panorama on IPFS (unless I decide to achieve “same origin” by putting the whole engine of Panellum on IPFS as well, but that would be quite a 無駄) because:

  • Panellum would use that photo as a WebGL texture,

  • WebGL textures are CORS-controlled,

  • some of IPFS users install Firefox addons or Chrome extensions to redirect IPFS requests to their local gateways,

  • their local gateways won't automatically have CORS unless they're v0.4.3-rc4 (or later) and a clean installation (not an upgrade) or users edited their configurations manually to enable CORS (the latter's not likely because why would they know to do that).

Something should be done about it. Consider, for example, two separate configuration files (one for the default config and the other for the overrides of the defaults).

Contributor guide

Tech stack
go
Domain
backendinfrastructure
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Go programmingIPFS architectureconfiguration upgrade process
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
Investigate how go ipfs handles default configuration changes between versions. Look at the code that initializes the config on first run and the upgrade path (likely `config/migration` or similar). The issue suggests a two file approach: one for defaults and one for user overrides. Consider implementing a migration mechanism that applies new defaults without overriding user changes. Check existing discussions in issue #3707 and linked PRs.