Setting up Galaxy without e-mail
Dear all, I just started setting up a galaxy instance and I'm a bit stuck with user account activation without e-mail. Is it possible to run Galaxy without an SMTP server set? For example, for the administrator user, I set: admin_users = <my e-mail> in galaxy.ini . I'd also like to require login (i.e., require_login = True) but it seems that I can't do that from the outset. That has to be False and allow_user_creation has to be True. Then I can create a user with the same account as above, who will then become an administrator. But, the account has to be validated some how and I can't seem to figure out how to do that without enabling an SMTP server. Am I doing something that wasn't intended? Perhaps I must have an SMTP server set? Or are there other steps I should do to activate the administrator? The web page https://wiki.galaxyproject.org/Admin/GetGalaxy makes it look easy...so I am concerned I'm doing it all wrong... Also, if this instance will be a production system some day, should I start using a database (Postgres or MySQL) right away and not bother with the default SQLite? Otherwise, I will have to port the data over, which the documentation implies is not an easy thing to do... Thank you! Ray
Hi Raymond, Regarding activation, you mean you set user_activation_on = True, right? You can just leave 'user_activation_on = False', which is the default (and the value if left commented), which will disable any requirement of having a local SMTP server for user creation and won't validate the account. If this instance is going to be a production server, I'd *strongly* recommend just starting it right now with a Postgresql database. Porting data over is not something you'll want to have to deal with. -Dannon On Wed, Jul 29, 2015 at 5:40 AM, Raymond Wan <rwan.work@gmail.com> wrote:
Dear all,
I just started setting up a galaxy instance and I'm a bit stuck with user account activation without e-mail. Is it possible to run Galaxy without an SMTP server set?
For example, for the administrator user, I set:
admin_users = <my e-mail>
in galaxy.ini . I'd also like to require login (i.e., require_login = True) but it seems that I can't do that from the outset. That has to be False and allow_user_creation has to be True.
Then I can create a user with the same account as above, who will then become an administrator. But, the account has to be validated some how and I can't seem to figure out how to do that without enabling an SMTP server.
Am I doing something that wasn't intended? Perhaps I must have an SMTP server set? Or are there other steps I should do to activate the administrator? The web page https://wiki.galaxyproject.org/Admin/GetGalaxy makes it look easy...so I am concerned I'm doing it all wrong...
Also, if this instance will be a production system some day, should I start using a database (Postgres or MySQL) right away and not bother with the default SQLite? Otherwise, I will have to port the data over, which the documentation implies is not an easy thing to do...
Thank you!
Ray ___________________________________________________________ Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: https://lists.galaxyproject.org/
To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/mailinglists/
Hi Dannon, On Thu, Jul 30, 2015 at 4:28 AM, Dannon Baker <dannon.baker@gmail.com> wrote:
Regarding activation, you mean you set user_activation_on = True, right? You can just leave 'user_activation_on = False', which is the default (and the value if left commented), which will disable any requirement of having a local SMTP server for user creation and won't validate the account.
Thanks for this! I must have set it to True without keeping a record of it and was being locked out of the system. I was going about it all wrong...I thought I'm supposed to execute some SQL statement on the back-end to set a flag to 'on' or something to activate users!
If this instance is going to be a production server, I'd *strongly* recommend just starting it right now with a Postgresql database. Porting data over is not something you'll want to have to deal with.
Got it! Thank you for the advice! I'll restart now before I get too far into it... Thanks for your help! Ray
participants (2)
-
Dannon Baker -
Raymond Wan