"Try it out" does not appear to be working

[Jandev]

I've been trying to get the solution to work on my local machine, but failing at this.

The docker-compose command mentioned in the "Try it out" section starts all the containers & the services appear to be working.

Use the Libre Simulator to test out Libre. The quickest way to run Libre and the Libre Simulator it is with the docker-compose command docker-compose -f docker-compose.yml -f docker-compose.sim.yml up -d. This will start up Libre and the simulator together. After running the command, browse to http://localhost:3000 to access Grafana and http://localhost:1880/ui to control the simulation.

The PostgreSQL instance is being populated with the initial seed data.

The simulator is also started & 'doing stuff'. The numbers change from time to time, so I guess that's a good simulator.

However, there's no data in the InfluxDB, or so it seems

When opening up Grafana, I can see multiple type of dashboards, but all graphs return an Unauthorized.

Any suggestions on what I can/should try next, or is there a missing step? Some friends of me tried to do the same and were facing the same issue.

What I've done so far to resolve the issue

• I've tried changing all of the passwords in the configurations to a single hardcoded password
• Turned off my Windows Firewall

Software used

I'm using:

• Windows 11 22H2 - 22621.674
• Docker version 20.10.17, build 100c701

[Sulomus]

+1

Did you resolve this issue or the project is abandoned? 😞

[tomhollingworth]

Libre v3 is under heavy development in private repositories. Codebase is changing to /libremfg/ instead of /spruik/ and migrating to GitLab, ISO certification and lots of other exciting stuff.

I wouldn't expect too much support from these repositories going forward. I'll seek to archive some of our v1/v2 repos and provide some breadcrumbs on where to go.

[Sulomus]

Libre v3 is under heavy development in private repositories. Codebase is changing to /libremfg/ instead of /spruik/ and migrating to GitLab, ISO certification and lots of other exciting stuff.

I wouldn't expect too much support from these repositories going forward. I'll seek to archive some of our v1/v2 repos and provide some breadcrumbs on where to go.

Great to hear this! v3 will be OSS too or private?

[tomhollingworth]

Private for the foreseeable future