User Tools

Site Tools


the_metaarray

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
the_metaarray [2022/02/07 20:14] – [Executables and Packages] jquahthe_metaarray [2022/02/25 05:25] – old revision restored (2022/02/07 20:26) hc9
Line 61: Line 61:
 * https through a self signed certificate is only available to personal URLs under *.sdf.org * https through a self signed certificate is only available to personal URLs under *.sdf.org
  
 +* Migrating your CGI scripts from the cluster to the MetaArray? You'll need to pay attention to the filename (only '.cgi' seems to work) and the path to the interpreter. For example, the following script will generate an actual webpage when served from the cluster, but when served from the MetaArray will prompt your browser for a location to save the script itself (first because the path to the interpreter is wrong, and second because the file extension is not recognized by nginx as needing the fastcgi module for its processing).
 +
 +  #!/usr/pkg/bin/python3.9
 +  # saved as $HOME/html/my_powerful.py
 +  import cgi
 +  
 +  print('Content-Type:text/html')
 +  print()
 +  print('<!DOCTYPE html>')
 +  print('<html lang="en">')
 +  print('<head>')
 +  print('<title>My powerful script</title>')
 +  print('</head>')
 +  print('<body>')
 +  print('Hello, World!')
 +  print('</body>')
 +  print('</html>')
 +
 +To get this script to behave properly on the MetaArray, change the first line to ''#!/usr/bin/env python3.9'', and rename the file as ''my_powerful.cgi'' .
 ===== SDF Nextcloud ===== ===== SDF Nextcloud =====
  
the_metaarray.txt · Last modified: 2023/07/01 00:15 by hc9