dsuckau

For me the same now suddenly. I updated two weeks ago to `1.0.0-beta2` and restarted sinopia, everything was fine. My packages were still listed in the web UI. But today,...

1.) I already did provide a path to the config file: ``` command=sinopia -c /opt/sinopia/config.yaml ``` (from my supervisord config) 2.) I have two storage folders: `/opt/sinopia/storage` and `/opt/sinopia/local_storage`. In...

I'am a little wondered about that a `1.0.0` can be released without this bug being fixed.. :/ Still no packages listing in `1.0.0`...

I did put some `console.log`'s in my `index-web.js` ``` storage.get_local(function(err, packages) { console.log('get packages') console.log('packages count', packages.length) console.log('allowed packages count', packages.filter(allow).length) console.log(req.remote_user) console.log(config.packages) if (err) throw err // that function...

Yes, but could you say something more about why the web interface expects the username of the packages configuration and where it should get it from?

Yes, you did unterstand it correctly. But in my case the web interface is public, there is no auth plugin. The cat user is only for the npm client.

This is not a feature request, it is a bug report.....

@frvge Yes, of course, would be a nice feature. But I think there should be a new issue for it, phrased as feature request. Because this issue was originally opened...

I really hope this project will be maintained again. We use sinopia in our company for private packages. We are kind of dependent on it now, but don't trust this...

+1 Want to use it with async/await