OpenFlexure Management Server
A server that run on an OpenFlexure Microscope to manage the microscope.
This server is just starting to be written so doesn't yet do much. Currently it is able to:
- Report the microscope server and service status
- Shut down or restart the microscope
- Shut down or restart the server
Eventually it will be able to:
- Configure the server for different hardware
- Install microscope extensions
- Update the microscope
Installation
This is experimental. When it moves out of the experiment phase it will automatically be installed on microscpe SD images. It only works on the new Trixie images.
For now to install a test version on a microscope for developing:
- Run
ofm activate - Clone the repository
- Navigate into the repo and run
npm install -e .[dev] - Create a systemd
servicefile that mirrors the one used by the microscope (/etc/systemd/system/openflexure-microscope-server.service) replacingopenflexure-microscope-servertoopenflexure-management-server. - Run
sudo systemctl enable openflexure-management-server
Developing on a Microscope
Developing the webapp
Use Node 24. If you donlt have node 24, consider using NVM to manage node versions on your computer.
To install, navigate to the webapp directory and run:
npm install
Running the dev server
To run the dev server run:
npm run serve
The server will update the API endpoints by default to http://localhost:5001. To Redirect to a microscope run:
npm run serve:microscope
This will update the API endpoints to point at http://microscope.local:5001. To use a different host name use an .env.local file with your hostname set to VITE_MICROSCPOPE_HOST:
# Save as .env.local
VITE_MICROSCPOPE_HOST=http://hostname.local:5001
This .env.local file is ignored by git.
Metadata
Release files for openflexure-management-server 0.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| openflexure_management_server-0.0.1.tar.gz | 4.1 MB | Without provenance | Details for openflexure_management_server-0.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| openflexure_management_server-0.0.1-py3-none-any.whl | Python 3 | none | any | Details for openflexure_management_server-0.0.1-py3-none-any.whl |
Total release size: 8.2 MB
Release files / openflexure_management_server-0.0.1.tar.gz
| Download URL | openflexure_management_server-0.0.1.tar.gz |
|---|---|
| Size | 4.1 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3e6835e9f96b592f575fc3041b0c0f4c311dc36f8a3fe771843ab84b0f3ee14f
|
|
BLAKE2b-256 checksum How to use checksums |
4d118aa3f393e2470d87b6f1f0e69c989301797ba4a2e80da5a7ad9d3d789af0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.2.0 CPython/3.13.13
|
Release files / openflexure_management_server-0.0.1-py3-none-any.whl
| Download URL | openflexure_management_server-0.0.1-py3-none-any.whl |
|---|---|
| Size | 4.1 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5ae99f3897069127a740fec94c787dd01f2955c76e79016daf83aa0852ced947
|
|
BLAKE2b-256 checksum How to use checksums |
42bf43b1a18973e8be6876385283055ac50b89053ba8389a4d9f88fdda89250b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.2.0 CPython/3.13.13
|
Security for openflexure-management-server 0.0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.