I get the same error as in this link:
“Error” when trying to access “scripts” in system administration & when trying to add a new script in a base. The only log information is:
django.request:228 log_response Internal Server Error: /api/v2.1/admin/scripts-tasks/
I have tried the suggested solution of deleting and reinstalling SeaTable + MariaDB containers and their configuration a few times, but the problem persists.
My version is 2.5.0 Developer Edition (self-hosted) on Windows 10 pc. It is a clean docker installation with one super user.
Hi, welcome to the SeaTable Forum.
I am sorry my previous statement was not correct. The Developer Edition can run Python scripts, but you have to configure the FaaS Scheduler and the Python runner.
See the manual here: Deploy - SeaTable Admin Manual
That bug you have quoted in the other post has been solved in 2.5.0 so you shouldn’t be seeing it if everything is correctly configured.
I am using these conf settings for local server:
For Python runner:
SCHEDULER_URL = ‘127.0.0.1/faas’
For FAAS Scheduler
- “444:444” # since 443 is already used by SeaTable container
FAAS_URL = ’ ’
RUNNER_URL = ‘http://host.docker.internal:8080’
DTABLE_WEB_SERVICE_URL = ‘127.0.0.1’
SEATABLE_FAAS_AUTH_TOKEN = ‘ea4df715d05144ff8a741654d79f4780’ # Token to copy to SeaTable’s configuration file
SEATABLE_FAAS_AUTH_TOKEN = ‘ea4df715d05144ff8a741654d79f4780’ # Token from seatable_faas_scheduler_settings.py
SEATABLE_FAAS_URL = ‘127.0.0.1/faas’ # URL of the SeaTable FAAS Scheduler
There were no errors and both FAAS scheduler and SeaTable containers are running. But, I still don’t see the Script’s page for Python in SeaTable (shows Error).
Any corrections required for above conf settings?
Quoting the manual: “It is strongly recommended to install SeaTable FAAS Scheduler and Python Runner on a separate host. Running these two components on the same machine as SeaTable is very likely to cause conflicts.”
Oh, I didn’t see that. (Sorry!)
Can you post a screenshot or animated gif (you cannot post videos, but agifs you can)?
Sure… attached here… I have completely removed Python runner and FAAS Scheduler.
Thanks… I have removed Python runner and FAAS Scheduler (
I would be curious how it looks in your base editor. Judging from your description above, I wonder if you have really found how to add a new script.
When you click on “Scripts” in your editor, what happens?
- Click on “Scripts” Symbol (that </> symbol)
- Click on “New script”
Oh, yes… you’re right about the “Scripts” in the editor. The small icon next to Plugins went unnoticed… Thanks for pointing this out. Now, I can see the screen exactly as you have shown in the screenshot. Does this mean that I can directly write the scripts from this screen and execute them by choosing ‘run script’ for buttons? Of course, from the above messages, I understand that Python scripts won’t work this way unless FAAS and Python Runner are configured on different machines.
PS: I got the impression that scripts have to appear under sys admin only because Plugins have to be added that way from under sys admin before choosing them for your bases.
Yes, just give it a try, you’ll find it is easy and a lot of fun to use! The scripts are saved in your base and you can use the button to call them in each table.
The “Scripts” in the admin menu is only for the system administrator to overview who created which regular execution tasks for the Python scripts. I don’t think this part is interesting for you at the moment, right? On the other hand, I think this menu will be removed soon (but I’m not sure), as the automation rule can run Python scripts regularly, too.
Of course, did I mention that we have a very detailed scripts programming manual? There you can find almost all the simple examples you need to understand, get used to and make good use of the SeaTable scripts:
SeaTable Programming Manual
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.