FTP
Structr will listen to incoming FTP connections on the application.ftp.port
configured in structr.conf if the service “FTPService” is included in the list of configured services configured.services
.
You have been redirected from an outdated version of the article. Below is the content available on this topic. To view the old article click here.
Structr will listen to incoming FTP connections on the application.ftp.port
configured in structr.conf if the service “FTPService” is included in the list of configured services configured.services
.
The FtpService allows users to connect to the structr instance via the FTP protocol. The FTP port can be configured via the application.ftp.port
key in structr.conf.
Authentication is only possible via password. After successful authentication the FTP connection lists all the files a user has read rights to starting from the root directory.
Files which the user is allowed to read, but which reside in a directory which the user is not allowed to “see”, the file will not show up in the FTP listing.
Regular users will also not be able to see file owner if they do not have read rights on those nodes.
$ lftp -p 8021 -u admin localhost
Password: *****
lftp admin@localhost:~> DIR
drwx------ 1 admin 0 Jun 30 15:22 testFolder
-rw------- 1 user1 347 Jun 30 09:24 test1.txt
-rw------- 1 admin 25 Jun 30 09:24 test2.txt
-rw------- 1 user2 5 Jun 30 09:24 test3.txt
-rw------- 1 user1 5 Jun 30 09:24 test4.txt
lftp admin@localhost:/>
application.host | The listen address of the Structr HTTP server. If you set the listen address to 127.0.0.1 , Structr will only be accessible for applications that run on the local host. This value essentially binds the HTTP server to the local loopback interface. The other option is 0.0.0.0 which makes Structr accessible from all networks. |
application.http.port | The HTTP port that Structr listens on. If you want to be able to access Structr under a simple http:// URL, you need to set this value to 80 . |
application.https.port | The HTTPS port that Structr listens on. If you want to be able to access Structr under a simple https:// URL, you need to set this value to 443 . |
application.ssh.port | The port that the SSHService listens on. |
application.ftp.port | The port that the FTPService listens on. |
application.https.enabled | If enabled, the internal HTTP server will be configured to allow HTTPS connections to the application.https.port. |
application.keystore.path | The path to a JKS keystore file that contains the certificate chain and private key for the SSL configuration needed for HTTPS. The keystore must be in PCK12 format. |
application.keystore.password | The password for the JKS keystore used in application.keystore.path. |
application.baseurl.override | Overrides baseUrl value that is originally assembled dynamically from the protocol, hostname and port of the server instance Structr is running on. |
When the maintenance mode is started, the following services are shut down:
After a brief moment, the following services are restarted with another port:
maintenance.application.http.port | HTTP port the Structr server will listen on in maintenance mode. |
maintenance.application.https.port | HTTPS port the Structr server will listen on in maintenance mode. |
maintenance.application.ssh.port | SSH port the Structr server will listen on in maintenance mode. |
maintenance.application.ftp.port | FTP port the Structr server will listen on in maintenance mode. |
maintenance.resource.path | The local folder for static resources served in maintenance mode. If no path is provided, a default maintenance page with customizable text is shown in maintenance mode. |
maintenance.message | Text for default maintenance page. |
$ lftp -p 8021 -u user1 localhost
Password:
lftp user1@localhost:~> DIR
drwx------ 1 0 Jun 30 15:22 testFolder
-rw------- 1 user1 347 Jun 30 09:24 test1.txt
-rw------- 1 25 Jun 30 15:41 test2.txt
-rw------- 1 5 Jun 30 09:24 test3.txt
-rw------- 1 user1 5 Jun 30 09:24 test4.txt
Various interfaces are available for integrating a Structr application into a company’s IT landscape, ranging from data import tools for RDF, CSV, XML and SQL to interactive technologies such as SSH and FTP to automated processing of mass data via the REST interface. In addition, ActiveDirectory support exists, and it is also possible to connect e-mail mailboxes via SMTP.
The Services Settings tab allows you to (re)start and stop Structr services. The available services include a MailService, CronService, SchemaService, AgentService, NodeService, SSHService, FtpService, LDAPService, HttpService, as well as a DirectoryWatchService.