See its user documentation for more information on configuring and managing your Rocket.Chat instance. You can then log in (by default, you will have to wait for an email with a TOTP code to log in) you will be able to change the multitude of settings, behaviours, and integrations that Rocket.Chat supports. After filling in your content and content related to your instance, you should receive an email from both your Rocket.Chat instance and from the Rocket.Chat developers showing your instance is registered. If you then go name] in your browser, you should get the 'initial user' start up page as shown in the attached screenshot. You can also stop Rocket.Chat by issuing:Īnd verify it status (running or not) via You can issue a CTRL-C to cancel out of the logs view - it won't affect the running Rocket.Chat instance. After it's done with the launching, Docker Compose will display the logging data being put out by both the MongoDB and Rocket.Chat containers. This command will 'pull' any missing reference containers from (the default central place where many Docker containers are stored by their developers) and launch them in "daemon mode" (the '-d' flag achieves that) on your server, so that they'll keep running until you stop them. You can then start the Docker containers by invoking Docker Composeĭocker-compose up -d
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |