Login broken

[jonnylink]

• BitBucket sign in isn't working (clicking it just brings the user back to the login page)
• Password reset doesn't work ("The CSRF token is invalid. Please try to resubmit the form.")

[jorisvaesen]

Sounds like this issue again: https://github.com/repman-io/repman/issues/629

[jyrkidn]

And also related to https://github.com/repman-io/repman/issues/635.

@akondas can this be fixed? Seems like an issue that pops up every 3-4 months.

[nicholas019]

I'm using it as my email login, but it doesn't work normally

[thibodelanghe]

@akondas is there any possibility that the storage get's migrated to S3 or something else of that nature?

[intheweb]

I know the service is free, but I cannot deploy anything for more then 13 hours now because repman.io has issues with logins.

Can you please supply a status update @akondas?

[nicholas019]

I'm also unable to distribute it. I'm waiting for it to normalize.

[aascericec]

Github login doesn't work also

[jonnylink]

Seems like maybe we're just SOL on this one. Regardless seems like it was not safe to rely on this (free) service.

[xvilo]

Self hosted is easy to run, I can possibly publish a repman kubernetes chart if there is interest in this

[lammensj-ds]

I believe we can close this. I'm able to login and fetch the package.json-file for the organisation I created. However, there's outdated data on the packages (like a branch that was removed in the last 24 hours), but I guess the platform is trying to update all the items it contains... Which might take some time, right?

[xvilo]

You can most likely press the “scan” button on the package overview for those packages to have them scanned again manually. I believe this also happens when the package webhook is called

[lammensj-ds]

You can most likely press the “scan” button on the package overview for those packages to have them scanned again manually. I believe this also happens when the package webhook is called

Yeah, already did that. The overview remains the same: "synced: 1 day ago".

[xvilo]

It depends on the following factors:

• How long was it broken for,
• how many messages are in the queue currently and,
• how many consumers there are running

If there are a lot and not too many consumers it might take some time to catch up.

but it could well not be fixed yet, and that the consumer isn’t running. Then we still have to wait. I would suggest keeping this open until we have the greenlight from @akondas

[jonnylink]

Agreed. I'm seeing last synced 6 days ago and we definitely have more since then. Manual scanning hasn't resolved it either.

[Jelle-S]

Same issue here, login works now, but packages don't seem to sync. As said before, we realize the service is free, but getting package updates can be pretty critical when there is (for example) a security update in one of those packages.

[xvilo]

Hi all, small update, I've gotten approval to publish the internally used helm chart for Repman, its located here: https://github.com/teamdotblue/helm

Couple of notes

• It was made to just work for us, so not everything is optimal yet.
• The current master version won't fully run yet, this is to be fixed.
• It will spawn Postgres, Redis and Minio (S3) as depending services.

I intend to fix the last remaining issues (nginx deployments), then it should be fine for a v0 tag. However, today is a public holiday over here, so I have to see how far I can come today.

[xvilo]

Small update, the helm chart is in a more generic and working state from v0.2.0 onwards. It can be deployed by first adding the repo uri helm repo add teamdotblue https://teamdotblue.github.io/helm. Then helm install it: helm upgrade --install -n repman-two --create-namespace repman teamdotblue/repman. -f values-repman.yaml --debug

Make sure to provide the values-repman.yaml file with updated values (https://github.com/teamdotblue/helm/blob/main/charts/repman/values.yaml) for your domain and change the app_secret config