assuming you installed everything correctly, navigate to the 'adapt_authoring' directory and run:
node serveryou should see some green highlighted messages in the output and it will tell you what port the local server is listening on, by default 5000.
so then go to localhost:5000 in your browser and you should see the dashboard login page.
2 replies
you'll also need to ensure mongod is running in the background (on GNU/Linux systems this would be
sudo systemctl start mongod.service or sudo service mongod start. Probably different for Mac though it's Unix based
@5am_gitlab 16.4.2 isn't LTS yet is it?
my mistake, I thought 16 was the LTS but can now see it's still 14
my mistake for not reading
my mistake, I thought 16 was the LTS but can now see it's still 14
Hello, I recently upgraded to V5 of the framework and 0.10.5 of the Authoring Tool. I typically work in the framework to develop the theme and then import to the Authoring Tool. I'm guessing that the Authoring Tool is grabbing the values from the schema files but I only edit the LESS files. I won't ever need to edit the colors in the Authoring Tool. Is there a way I can disable editing colors in the Authoring Tool or will I have to update the LESS files and the schema files for every change?
@simondate, the tagged pre-releases are exactly the same as the latest release, just with an additional schema folder for the new authoring tool. it doesn't have any effect in the current authoring tool. for example, bookmarking comparison
@marissa-champions, if you mean disabling the colour picker functionality then it should just be a case of removing the
variables object from the theme's schema
Will the existing version 0.10.5 development continue or it will be stopped?
so once you've exported, if you add
"strictMode": true into the course.json in the build object and rebuild using grunt dev or grunt build you should get strict mode enabled
@simondate I thought that, unfortunately our provider uses templating across Adapt framework/AT upgrades, so our forked versions may interfere with this, and we also can't disable any plugins they've enabled by default, meaning the course author would probably see two of every component in the list and this could be confusing.
Was this intentional to do so?
As for example when we export course all custom styles will be wiped out when re-importing the exported-course.
As for example when we export course all custom styles will be wiped out when re-importing the exported-course.
What would be the most practical/sensible way to host multiple older and newer versions of the AAT from the same server? Maybe containerisation? For example, I'd like to spin up a testing VPS and have a few subdomains pointing to different versions to make it quick and easy to test and compare versions of plugins etc.
I could easily do this with VMs locally, but then presumably there'd be no way to do quick mobile previewing
yeah, have some experience with Apache proxies. My personal site uses proxies for services like Plausible analytics, Netdata, Nextcloud etc. I'd quite like to try out Docker for some stuff eventually. My Plausible instance runs in Docker but was installed via a script, so I don't have much experience with setting containers up yet.
the containers, defined in a text file, usually inherit from a standard nodejs container by directive, then you put in a config for the application installation bits, it's very straight forward. automating the startup and redirecting apache to it might provide a challenge
Is there any reason why endpoints are not protected within authoring tool?
For example with postman without auth we can execute endpoints?
For example with postman without auth we can execute endpoints?