You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a few Cloudgene instances and quite often the confirmation emails end up in junk mail or are even not delivered by big webmail providers at all. Edu accounts seem to be especially aggressive in not delivering at all, which is a problem since most of the userbase makes their accounts with .edu mails. There are potentially things we can do about delivery rates going forward, but in the meantime I want to manually confirm user accounts (we don't want to give up the confirmation email as we have been hit with spam attacks on other services in the past where they get an account and the plaster text everywhere for SEO, even in jobnames...). The number of unconfirmed accounts is probably something like 30-40% now and often when an account isn't confirmed they tried with 2-3 different emails... it's been becoming more and more of a problem over time.
Maybe I'm missing something obvious... but I can't seem to figure out how to do this. I don't see a way in the interface, though the check on the left side of the users list seems to indicate whether or not they have confirmed. I might be missing something in the UI... I almost feel like I asked this before but I can't find it now, just that feeling of deja vu.
I'm using the docker container and still on the H2 database, I thought it wasn't a big deal because there isn't a ton of user info, the dataset is small... but H2 seems incredibly obnoxious now that I'm looking at this. I thought, ok, I'll manually mark them in the database. I'm not totally unfamiliar with databases... MariaDB, MySQL, Oracle... but the H2 setup has me scratching my head on how to even start their console for this... also because it is running in embedded mode... I'm not sure, is it even exposed outside of the cloudgene app?
Alternatively is there a way I can migrate the database from H2 to MySQL? After that I should be fine to make the appropriate modifications in there.
The text was updated successfully, but these errors were encountered:
We have a few Cloudgene instances and quite often the confirmation emails end up in junk mail or are even not delivered by big webmail providers at all. Edu accounts seem to be especially aggressive in not delivering at all, which is a problem since most of the userbase makes their accounts with .edu mails. There are potentially things we can do about delivery rates going forward, but in the meantime I want to manually confirm user accounts (we don't want to give up the confirmation email as we have been hit with spam attacks on other services in the past where they get an account and the plaster text everywhere for SEO, even in jobnames...). The number of unconfirmed accounts is probably something like 30-40% now and often when an account isn't confirmed they tried with 2-3 different emails... it's been becoming more and more of a problem over time.
Maybe I'm missing something obvious... but I can't seem to figure out how to do this. I don't see a way in the interface, though the check on the left side of the users list seems to indicate whether or not they have confirmed. I might be missing something in the UI... I almost feel like I asked this before but I can't find it now, just that feeling of deja vu.
I'm using the docker container and still on the H2 database, I thought it wasn't a big deal because there isn't a ton of user info, the dataset is small... but H2 seems incredibly obnoxious now that I'm looking at this. I thought, ok, I'll manually mark them in the database. I'm not totally unfamiliar with databases... MariaDB, MySQL, Oracle... but the H2 setup has me scratching my head on how to even start their console for this... also because it is running in embedded mode... I'm not sure, is it even exposed outside of the cloudgene app?
Alternatively is there a way I can migrate the database from H2 to MySQL? After that I should be fine to make the appropriate modifications in there.
The text was updated successfully, but these errors were encountered: