📦➔🦋 Store and retrieve files on the Atmosphere
README: add missing envvars to Build instructions
+3
-1
+3
-1
README.md
+3
-1
README.md
···
102
102
103
103
Various environment variables can be exported to control various aspects of the development version. These are as follows:
104
104
105
+
* `ATFILE_DEVEL_DIST_USERNAME` <em><string></em><br />_(Todo)_. During runtime, this is set to `$did` in `atfile.sh` (see **🏗️ Building ➔ Meta**). Ideally, you should not set this variable as updates in the built version will not be fetched from the correct place
106
+
* `ATFILE_DEVEL_DIST_PASSWORD` <em><string></em><br />_(Todo)_
105
107
* `ATFILE_DEVEL_ENABLE_PIPING` <em><int> (default: `0`)</em><br />Allow piping (useful to test installation) _(e.g. `cat ./atfile.sh | bash`)_
106
108
* `ATFILE_DEVEL_ENABLE_PUBLISH` <em><int> (default: `0`)</em><br />Publish build to ATProto repository (to allow for updating) as the last step when running `release`. Several requirements must be fulfilled to succeed:
107
-
* `ATFILE_DEVEL_DIST_USERNAME` must be set<br />By default, this is set to `$did` in `atfile.sh` (see **🏗️ Building ➔ Meta**). Ideally, you should not set this variable as updates in the built version will not be fetched from the correct place
109
+
* `ATFILE_DEVEL_DIST_USERNAME` must be set
108
110
* `ATFILE_DEVEL_DIST_PASSWORD` must be set
109
111
* No tests should return an **Error** (**Warning** is acceptable)
110
112
* Git commit must be <a href="https://git-scm.com/docs/git-tag">tagged</a>