Repository navigation
Opifer 1.0.0
Install
npm install -g @opifer/cli
o4r init --company "My company" && o4r up # http://127.0.0.1:4700Node.js 22. PostgreSQL is embedded, Docker is optional. Website and guides: https://opifer.dev
The repository is public, the website is up at opifer.dev, and everything the README says has been verified on a second machine. No breaking change from 0.1.0: the version says the product is ready to be tried.
Added
- Website
site/(home, the guides rendered fromdocs/), built withnode site/build.mjs. CONTRIBUTING.md,CLA.md(contributor licence agreement, sign-off on every commit checked by a workflow),SECURITY.mdwith private vulnerability reporting, issue forms and a pull request template.- The task form creates a project inline.
DockerEnvironmentoptionuser: on Linux the sandbox runs as the server's user, so files written under the task folder belong to it on the host.
Fixed
- The container image did not build (
pnpm prune --prodwithout a TTY) and then did not start (commander, then@opifer/dbmissing from a production install); verified on Linux with Docker 29: start, demo, restart, recovery after a kill. docker-compose.ymlpublished the port on every interface; it binds127.0.0.1now.o4r uprefused to start after a container restart because the stale pid file pointed at pid 1, its own pid.- After a server restart every wake-up left running went back to the queue without comparing the database clock with the process clock (a random CI failure).
GET /v1/sessions/:idwith a malformed id answered 500; it answers 400.- The CLI printed
0.0.0.0in URLs when listening on every interface.
Changed
- The demo company is called Proclive.
Full changelog: https://github.com/NextEpochs/opifer/blob/main/CHANGELOG.md · Website: https://opifer.dev