-
Notifications
You must be signed in to change notification settings - Fork 241
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How do I connect this to my website? #376
Comments
This is a very old project, so I am not sure if you will still be able to get everything properly setup. You need to put the modules/ui/dist directory (after a successful
as mentioned in modules/ui/README.md). To change the superadmin (admin/admin), make sure that you should change the migration files in
I haven't tested this, but that should roughly be what you need to do. Maybe you need to look up the deletion syntax for CQL. Also I don't remember where/how to set the password... maybe it's admin by default as well, you can try it out. Apart from that, everything else is pretty much server configurations: getting the URLs to point to wasabi and the UI, etc. Once you done that, you can create experiments and use them as shown inside the contrib/client-demo example project. Good luck! |
I want to use Wasabi to have an admin test things such as captions, pictures, etc. to a small news-like site I run. I have Wasabi running on my virtual box, and can access the Wasabi UI from localhost. However, I need the admin I'm gonna have use it be able to go to wasabi(or something).mywebsite.com, and only the admin to be able to change portions of mywebsite.com using Wasabi as the testing framework.
How would I go about doing this? Which files would I start at?
The text was updated successfully, but these errors were encountered: