I want to add bulk usernames (to create initial dummy users to create posts). So I was trying with creating a rake file, and loading it and then running it. But had no success. The rake file doesn’t even gets loaded sometimes, and when I use another method it gets loaded and then error thrown “I don’t know how to create …” error thrown by rails c (can’t even remember the error message as I tried thousand different methods over hours to make it work with no success) What I did Created users.rake file cd /var/www/discourse mkdir -p lib/tasks touch lib/tasks/users.rake Editing it with nano cd /var/www/discourse/lib/tasks sudo nano users.rake And then pasted the following code into editor and saved namespace :users do desc "Create users from a list" task :create, [:usernames, :password, :domain] => :environment do |task, args| usernames = args[:usernames].split(',') password = args[:password] domain = args[:domain] User.transaction do usernames.each do |username| next if User.exists?(username: username) email = "#{username}@#{domain}" user = User.new(username: username, email: email, password: password) unless user.save puts "Failed to save user #{username}: #{user.errors.full_messages.join(", ")}" raise ActiveRecord::Rollback end end end end end Loaded into rails c and loaded it into tasks rails console load 'lib/tasks/users.rake' exit Then tried to create the users ./launcher enter app rake users:create["username1,username2", "password", "domain.com"] Is there any other method that I can try through the terminal without using third party things.

Use rake dev:populate to seed with the out of the box test data - easy! [image] Set up a staging server Sysadmins There are several tricks that can help when you are setting up a staging server. What is a staging server? A staging server is essentially a clone of a production site. It also resides on a server, and functions identically. It runs inside a Docker container, just as a normal Discourse site does. It exists to give you a place to try risky things out, or to trial things that you cannot easily hide from your users. It is very useful for trialling adverts using the Discourse Advertising Plugin (A…

Thank you for your comment. Your method will just fill the site with some random users and data, which I do not want. And I do not want a staged online site, I can just host it locally if I want. This is for a production environment. Dummy users will actually have some meaningful topics. The purpose of this is not to present an empty site to the public. So, kindly let me know of a solution related to the question I mentioned. I just need to insert users (I have the name list for the users), into the main DB of discourse. Thank you.

[image] PrettyGirl: I can just host it locally if I want. You can use this technique for local development installs too (that’s its primary purpose). [image] PrettyGirl: So, kindly let me know of a solution related to the question I mentioned. I just need to insert users (I have the name list for the users), into the main DB of discourse. Why not read the code for that rake task and modify it how you see fit? lib/tasks/dev.rake main # frozen_string_literal: true def check_environment! raise "Database commands are only supported in development environment" if !Rails.env.development? ENV["SKIP_TEST_DATABASE"] = "1" ENV["SKIP_MULTISITE"] = "1" end desc "Run db:migrate:reset task and populate sample content for development environment" task "dev:reset" => ["db:load_config"] do |_, args| check_environment! Rake::Task["db:migrate:reset"].invoke Rake::Task["dev:config"].invoke Rake::Task["dev:populate"].invoke end desc "Initialize development environment" task "dev:config" => ["db:load_config"] do |_, args| This file has been truncated. show original

I recommend that you look at the import scripts in script/import_scripts and look for one that reads csv files. I’ve been planning a script or plugin that will let your create stuff from a spreadsheet, but I’ve had other work in the way.

I amended the code, but the production discourse in the docker container, I created rake file with touch and edited in nano, then entered the app with ./launcher enter app, then entered rails and checked rake -T and the rake file does not gets loaded. This is my primary concern. I can’t even test out the file in production. However, in localhost, theres no issue, I just copy and pasted the file into the lib/tasks and it works fine. This docker and docker container is pain when you need to access things directly. And I can’t even find out why it doesn’t automatically gets loaded into the rake tasks list. So, I’m still stuck in the production as the rake file does not automatically gets loaded, so I can’t run the command. Your site won’t support me if I didn’t use the docker, or else I would have been more than happy to remove the docker and host the site directly. That would make life much more easier.

Normally rake tasks are tested in development and can be deployed as part of a plugin.

Of you have it working locally you can backup there and restore to production. Did you put your file in /var/www/discourse/lib/rake inside the container?

The issue is that when local backup is uploaded to the live site, it will replace all the contents I made in live site. I have a local instance, but someone in this forum suggested me to have the live site to do the development. So, I’m now developing in the live site (it’s not officially public yet though). And I put the file in lib/tasks, local instance works, not the live instance. I’ll try the lib/rake as well.

You shouldn’t develop on a live site. You develop locally, package the changes in a Theme Component or plug-in and then deploy to the live site. Here’s an example of a rake task in a plugin: discourse-chatbot/lib/tasks at main · merefield/discourse-chatbot main/lib/tasks An AI bot with RAG capability for Topics, Chat & Customer Support in Discourse, currently powered by OpenAI - merefield/discourse-chatbot

[image] Robert: You shouldn’t develop on a live site. I think you shouldn’t develop rails or ember on a standard install, but I regularly to imports in a production container. Since it’s just a rake task you don’t even need to restart the server for changes to take effect. Since it’s not public it should be safe to revert too a backup of something goes wrong. That’s probably where I would do it. You could backup the live site and restore it to the dev site, do the work and then backup/restore back to the live site.

Bulk creating users with rails etc

Development

merefield (Robert) October 13, 2023, 7:03am 10

You shouldn’t develop on a live site.

You develop locally, package the changes in a Theme Component or plug-in and then deploy to the live site.

Here’s an example of a rake task in a plugin:

Topic		Replies	Views
Seed or API calls to create test users Development	6	1088	August 19, 2019
What is the Rails command to create an admin user in Discourse? Product Support	9	2400	April 10, 2020
Import users from csv Development	4	4009	January 29, 2018
How to create a new user in pure sql Migration	26	2968	October 18, 2023
How to manually add users and email in console mode? Product Support	11	9555	March 17, 2017

Bulk creating users with rails etc

Related topics