Security News
New Python Packaging Proposal Aims to Solve Phantom Dependency Problem with SBOMs
PEP 770 proposes adding SBOM support to Python packages to improve transparency and catch hidden non-Python dependencies that security tools often miss.
@flowfuse/file-server
Advanced tools
All requests should include a Authorization
header with a Bearer token assigned by the FlowFuse platform to identify
Create/Replace
POST /v1/files/:teamId/:projectId/[path and filename]
Content-Type: application/octet-stream
Append
POST /v1/files/:teamId/:projectId/[path and filename]
With Header FF_MODE: append
Content-Type: application/octet-stream
Read File
GET /v1/files/:teamId/:projectId/[path and filename]
Content-Type: application/octet-stream
Delete File
DELETE /v1/files/:teamId/:projectId/[path and filename]
Check team quota usage
GET /v1/quota/:teamId
Content-Type: application/json
Set stored values
POST /v1/context/:projectId/:scope
Content-Type: application/json
Body:
[
{ "key": "x", "value": { "foo": "bar" } },
{ "key": "y.y", "value": 100 },
]
Get stored values
GET /v1/context/:projectId/:scope?key=x[&key=y.y]
Content-Type: application/json
Response:
[
{ "key": "x", "value": { "foo": "bar" } },
{ "key": "y.y", "value": 100 }
]
Get keys for a scope
GET /v1/context/:projectId/:scope/keys
Content-Type: application/json
Response:
[
"x",
"y"
]
Delete scope
DELETE /v1/context/:projectId/:scope
Clean unused scopes from the store
POST /v1/context/:projectId/clean
Content-Type: application/json
Body:
[
"nodeId", "flowId"
]
Configuration is read from etc/flowforge-storage.yml
host: 0.0.0.0
port: 3001
base_url: http://flowforge:3000
driver:
type: localfs
options:
root: var/root
telemetry:
backend:
prometheus:
enabled: true
s3
, localfs
or memory
(for testing)/metrics
endpoint to track resource usageThe following can be any of the options for the S3Client Contructor, see here
host: '0.0.0.0'
port: 3001
base_url: http://forge.default
driver:
type: s3
options:
bucket: flowforge-files
credentials:
accessKeyId: XXXXXXXXXXXXXXXXXXX
secretAccessKey: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
forcePathStyle: true
region: us-east-1
This driver is purely to make testing easier, it has no configuration options.
This driver can use either PostgreSQL or SQLite to hold context values.
To use with PostgreSQL configure as follows:
context:
type: sequelize
options:
type: postgres
host: 127.0.0.1
port: 5432
database: ff-context
username: user
password: password
To use with SQLite configure as follows:
context:
type: sequelize
options:
type: sqlite
storage: ff-context.db
Where context.options.storage
is the filename of the SQLite database, by default it will be written to
the var
directory if a fully qualified path is not provided.
/opt/flowforge-file-storage
npm run test
NOTE: This will run all tests for all backends and requires a running postgres database
To prepare postgres for the tests, use the following procedure (tested on Linux and WSL2 ubuntu + docker)...
docker run --rm --name postgres -e POSTGRES_PASSWORD=secret -e POSTGRES_USER=postgres -p 5432:5432 postgres:14
npm run test:nopg
Alternatively, you can set env variable TEST_POSTGRES=false
export TEST_POSTGRES=false
npm run test
FAQs
A basic Object Storage backend
We found that @flowfuse/file-server demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
PEP 770 proposes adding SBOM support to Python packages to improve transparency and catch hidden non-Python dependencies that security tools often miss.
Security News
Socket CEO Feross Aboukhadijeh discusses open source security challenges, including zero-day attacks and supply chain risks, on the Cyber Security Council podcast.
Security News
Research
Socket researchers uncover how threat actors weaponize Out-of-Band Application Security Testing (OAST) techniques across the npm, PyPI, and RubyGems ecosystems to exfiltrate sensitive data.